I rooted my ace plus phone and trying to put CyanogenMod 10.1 and I m stuck with this error 7.
I tryed to change cwm and delete few lines from rom that are related with checking compatibility but with no success.
ddfacto said:
I rooted my ace plus phone and trying to put CyanogenMod 10.1 and I m stuck with this error 7.
I tryed to change cwm and delete few lines from rom that are related with checking compatibility but with no success.
Click to expand...
Click to collapse
[GUIDE] status 7 error while flashing rom cwm xda (noob friendly)
or
you can re-download the rom and after downloading match the check sum
or
you can try twrp recovery
link is in my signature
vickyg.coolest said:
[GUIDE] status 7 error while flashing rom cwm xda (noob friendly)
or
you can re-download the rom and after downloading match the check sum
or
you can try twrp recovery
link is in my signature
Click to expand...
Click to collapse
I tryed to re-download the rom few times...I ll try with twrp now...btw...do u thing its smart to update my phone to JB?
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> twrp-build-3-06052013-trebon.tar.md5 is invalid.
<OSM> End...
ddfacto said:
I tryed to re-download the rom few times...I ll try with twrp now...btw...do u thing its smart to update my phone to JB?
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> twrp-build-3-06052013-trebon.tar.md5 is invalid.
<OSM> End...
Click to expand...
Click to collapse
again you have a corrupted file of twrp
you should use idm to download twrp
because twrp is working for everyone
and of course it is smart to update to jb if you dont use camera much
vickyg.coolest said:
again you have a corrupted file of twrp
you should use idm to download twrp
because twrp is working for everyone
and of course it is smart to update to jb if you dont use camera much
Click to expand...
Click to collapse
try cwm 5.5
vickyg.coolest said:
again you have a corrupted file of twrp
you should use idm to download twrp
because twrp is working for everyone
and of course it is smart to update to jb if you dont use camera much
Click to expand...
Click to collapse
that part is working but now I m stack on boot loop :/
wipe data in cmw after flash cm10.1
good luck
ddfacto said:
that part is working but now I m stack on boot loop :/
Click to expand...
Click to collapse
for bootloop you should wipe data wipe system and wipe evrythng except sd card
then flash cm 10.1 or whatever rom you want:thumbup:
Sent from my GT-S7500 using Tapatalk 2
Related
Hi Guys
I Want to install the XWLA4 Stock Rom on my Indian XWKI5 Firmware.
I heard that Flashing through ODIN will Increase Custom Counter and this voids Warranty?
I want to do these things:
Install XWLA4 - I Would also want to Retain my INDIAN CSC.. Help me how.?
Install CWM
Install the Ultimate Kernel with Voodoo Sound
How can I do this without Voiding Warranty and Incrementing Custom Counter..
Read the FAQ,but it didn't give much info..
BTW I am not new to Android. Just that I am new to ODIN
My Previous phones had direct Procedure to install CWM and flash ROM through it.. Thats why I am getting Confused and Stuck.
1. Installing an Stock ROM will not increase the Custom Count.
2. Don't worry about Warranty when ever you have problem flash Indian stock ROM before taking it to Service center.
3. once you install the XWLA4 ROM via ODIN then you need to install the CWM using ODIN and then flash the Ultimate kernel using CWM and enjoy the Voodoo sounds....
Great.. How to retain my CSC man? Indian One..
BTW XWLA4/ZSKK5, Which one to download?
I9103ZSKK5 ## 2011 November I9103OZSKK5 Hong Kong
I9103ZSKK5 ## 2.3.6 2011 November I9103OZSKK5 Taiwan
I9103XWLA4 2012 January I9103DRELA1 Austria (3 Hutchison)
For retaining the CSC use this method mentioned in the below link...
http://forum.xda-developers.com/showpost.php?p=20692726&postcount=16
You can download the XWLA from below link..
http://forum.xda-developers.com/showthread.php?t=1467088
Thanks.. SO Flashing CWM Via ODIN also doesn't increase Counter, Does it?
tejagamer said:
Thanks.. SO Flashing CWM Via ODIN also doesn't increase Counter, Does it?
Click to expand...
Click to collapse
no it wont .....
Great.. TY man..
Downloading Indian and XWLA4.. Will update and Install CWM and Ultimate Kernel.
BTW If I want to change Kernel to Ardatdat's Can I flash over Ultimate Kernel?
tejagamer said:
Great.. TY man..
Downloading Indian and XWLA4.. Will update and Install CWM and Ultimate Kernel.
BTW If I want to change Kernel to Ardatdat's Can I flash over Ultimate Kernel?
Click to expand...
Click to collapse
you can do it...
Thanks for confirming.. Will do so asap
I am getting an MD5 error
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> I9103XWLA4_I9103DRELA1_I9103NELA1_HOME.tar.md5 is invalid.
<OSM> End...
All I Did was Change the Cache.img with my Indian Firmware one..
How To overcome this?
No idea ..... But y u want to change CSC ......
Sent from my GT-I9103 using XDA
So that It Remains Indian.. And it will be Debranded na..
Else we will have all those 3 Apps
EDIT: Never Mind..
All i Had to do was Change extension from .tar.md5 to .tar..
Flashing now
tejagamer said:
So that It Remains Indian.. And it will be Debranded na..
Else we will have all those 3 Apps
Click to expand...
Click to collapse
I don't know much about CSC, but i am using ZCLA its chines firmware but i am not having any problem..
tejagamer said:
I am getting an MD5 error
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> I9103XWLA4_I9103DRELA1_I9103NELA1_HOME.tar.md5 is invalid.
<OSM> End...
All I Did was Change the Cache.img with my Indian Firmware one..
How To overcome this?
Click to expand...
Click to collapse
if you changed the cache.img you must to delete the .md5 from the ROM file, the file must be I9103XWLA4_I9103DRELA1_I9103NELA1_HOME.tar
Sorry for my bad English i'm Spanish.
Salu2,
SiWy ;-)
Yeah Did that.
Now its all fine..
Boot up is faast too..
EDIT: Flashed via ODIN
EDIT 2: Voodoo sound is awesome.. Too good.. Loving my R now..
tejagamer said:
Yeah Did that.
Now its all fine..
Boot up is faast too..
EDIT: Flashed via ODIN
EDIT 2: Voodoo sound is awesome.. Too good.. Loving my R now..
Click to expand...
Click to collapse
Oh well you have done it now enjoy !
But I'll have to wait for my PC to fire up.
'cooleagle' said:
Oh well you have done it now enjoy !
But I'll have to wait for my PC to fire up.
Click to expand...
Click to collapse
it have CWM flashable package also, give it a try u will love the audio output
http://forum.xda-developers.com/showthread.php?t=1632868
'cooleagle' said:
Oh well you have done it now enjoy !
But I'll have to wait for my PC to fire up.
Click to expand...
Click to collapse
Yeah man
Do update to XWLA4 and Install Ultimate Kernel Dude..
Speed Gain is awesome..
Also, Voodoo Sound Rocks!! Too good
xlm13x said:
it have CWM flashable package also, give it a try u will love the audio output
http://forum.xda-developers.com/showthread.php?t=1632868
Click to expand...
Click to collapse
No man currently my R's on stock Indian ROM as in case something happens I won't have to go around my friend's house to put it back on stock before taking it to the service center.
'cooleagle' said:
No man currently my R's on stock Indian ROM as in case something happens I won't have to go around my friend's house to put it back on stock before taking it to the service center.
Click to expand...
Click to collapse
what happened to ur pc? u gave in warranty?
I have a big problem with Rooting my Samsung via ODIN. I'm using difirent version of odin -started v.1.85 up to 3.07 and in all i have the same problem. The information when I started to root ma samsung is like this below:
<ID:0/027> File analysis..
<ID:0/027> SetupConnection..
<ID:0/027> Initialzation..
<ID:0/027> Get PIT for mapping..
<ID:0/027> Firmware update start..
<ID:0/027> recovery.img
<ID:0/027> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and the status in left upper window is of course FAILED
I'm using the 4.04 android version I9103XXLQ3.
I'm using Windows 7 64 bit in my computer.
If I understand correctly, when I want to upload new version of ROM like avatar rom, at first i must root my phone using Odin, and then it possible to upload the new Avatar 4.2.2 rom by the recovery mode from the sdcard.
There is a streng situation after I try to root my phone via odin and have the information like few lines above, when i tray to start my phone then I have the information in ma screen like this below whith the yellow triangle "exclamation".
Firmware upgrade encountered an issue.
Please select recovery mode in Kies and try again.
Can anybody could give me some advices how to fix this problem. I will be very appreciate
Thanks and sorry for my english at all
I9103-junior said:
I have a big problem with Rooting my Samsung via ODIN. I'm using difirent version of odin -started v.1.85 up to 3.07 and in all i have the same problem. The information when I started to root ma samsung is like this below:
<ID:0/027> File analysis..
<ID:0/027> SetupConnection..
<ID:0/027> Initialzation..
<ID:0/027> Get PIT for mapping..
<ID:0/027> Firmware update start..
<ID:0/027> recovery.img
<ID:0/027> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and the status in left upper window is of course FAILED
I'm using the 4.04 android version I9103XXLQ3.
I'm using Windows 7 64 bit in my computer.
If I understand correctly, when I want to upload new version of ROM like avatar rom, at first i must root my phone using Odin, and then it possible to upload the new Avatar 4.2.2 rom by the recovery mode from the sdcard.
There is a streng situation after I try to root my phone via odin and have the information like few lines above, when i tray to start my phone then I have the information in ma screen like this below whith the yellow triangle "exclamation".
Firmware upgrade encountered an issue.
Please select recovery mode in Kies and try again.
Can anybody could give me some advices how to fix this problem. I will be very appreciate
Thanks and sorry for my english at all
Click to expand...
Click to collapse
check whether Kies is running in background?
close it. also u must follow soft brick tutorial.
Thanks,
Disturbed™
Sent from my Disturbed™ Galaxy S4 using Tapatalk (VIP)
______________________________________________________
Wait for my time, U gonna pay for what U have done. - Disturbed™
Could you post Odin screen shot with all details how you are flashing...
Sent from my Nexus 4 using Tapatalk 2
screen shot from Odin
Hi
I attach an image from Odin. Any other suggestions welcomed.
Thanks
Peter
Disturbed™ said:
check whether Kies is running in background?
close it. also u must follow soft brick tutorial.
Thanks,
Disturbed™
Sent from my Disturbed™ Galaxy S4 using Tapatalk (VIP)
______________________________________________________
Wait for my time, U gonna pay for what U have done. - Disturbed™
Click to expand...
Click to collapse
Hi
I removed the Kies from Windows, because it seemed to me that it can cause conflict when I''m starting flash my phone.But unfortunately, problem is the same.
Where I can find "follow soft brick tutorial". and what is it used for.
Thanks at all
If you are facing problems with v6.0.3.2, download tar file of CWM v4.0.0.2 from here and try flashing it.
by flashing CWM you are flashing custom recovery and doing so will not root your phone!
you need to flash superuser.zip or flash ardatdat's kernel to root.
Nikhil said:
If you are facing problems with v6.0.3.2, download tar file of CWM v4.0.0.2 from here and try flashing it.
by flashing CWM you are flashing custom recovery and doing so will not root your phone!
you need to flash superuser.zip or flash ardatdat's kernel to root.
Click to expand...
Click to collapse
what a catch. we must have reading habits.
Thanks,
Disturbed™
Sent from my Disturbed™ Galaxy S4 using XDA Premium 4
______________________________________________________
Wait for my time, U gonna pay for what U have done. - Disturbed™
Nikhil said:
If you are facing problems with v6.0.3.2, download tar file of CWM v4.0.0.2 from here and try flashing it.
by flashing CWM you are flashing custom recovery and doing so will not root your phone!
you need to flash superuser.zip or flash ardatdat's kernel to root.
Click to expand...
Click to collapse
Hi, thanks a lot - solution with cwm ver.4.0.0.2 turned out to be the right way.I managed to upload to my phone this version of cwm but I wondering if this is only ver. that will by works on my i9103r?. Anyway now I am trying to upload new unofficial ROM and one question about that. Where can I find a instruction how to deal with this operation I now only that this is doing from the download mode using cwm. But that's all. Thanks in advance:good:
I9103-junior said:
Hi, thanks a lot - solution with cwm ver.4.0.0.2 turned out to be the right way.I managed to upload to my phone this version of cwm but I wondering if this is only ver. that will by works on my i9103r?.
Click to expand...
Click to collapse
No you can flash different versions also. Since you installed CWM v4.0.0.2, now onwards download flashable zip file of other recoveries and flash them.
Anyway now I am trying to upload new unofficial ROM and one question about that. Where can I find a instruction how to deal with this operation I now only that this is doing from the download mode using cwm. But that's all. Thanks in advance:good:
Click to expand...
Click to collapse
Visit [INDEX] Custom ROM/Kernel/MOD/Guide/Tool
links to various Roms are given there and instructions are given in respective Rom's OP.
Happy Flashing..
I wanted to install the stock firmware on my galaxy j7 but when I try to flash it with odin I get this error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplag the cable..
<OSM> Please wait..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialization..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> cm.bim
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can you please help me?
The model is j710fn (2016)
@r4d0n7 have you verified hash of md5 to be sure it didn't get corrupted during download.. you could try removing the ".md5" so it's just a ".tar" an extract with winrar or 7zip to see if any errors occur you can try flashing without the ".md5" also just flash the tar file otherwise it could be corrupted make sure you download from a reliable source.. use a download manager also. Maybe your partitions got jacked up over time and there not matching when verifying may have to flash a .pit file also
Sent from my LGLS676 using Tapatalk
rick.wardenburg said:
@r4d0n7 have you verified hash of md5 to be sure it didn't get corrupted during download.. you could try removing the ".md5" so it's just a ".tar" an extract with winrar or 7zip to see if any errors occur you can try flashing without the ".md5"
Click to expand...
Click to collapse
Well, I tried what you said so: renaming the .md5 into .tar or just removing the .md5 and letting only .tar. Still I get the same result and on my downloading mode console in my phone I'm getting: SECURE CHECK FAIL: (BOOTLOADER) I tried different firmwares to download... Same result. I tried flashing a custom recovery and it works. This means it's not anything from the drivers.
rick.wardenburg said:
also just flash the tar file otherwise it could be corrupted make sure you download from a reliable source.. use a download manager also. Maybe your partitions got jacked up over time and there not matching when verifying may have to flash a .pit file also.
Click to expand...
Click to collapse
I downloaded the last .tar version from samsung-firmwares.org for j710fn but still no fix... I'm sure it may be from my partitions. If it is, then tell me how can i fix them up?
That's not good I'm sure it means it failed to verify using pit, when you have phone plugged in USB and on download mode go to your device manager screen in windows and check that your name of phone shows up correct, flashing a rom not ment for your device could of caused this by experience
---------- Post added at 10:13 AM ---------- Previous post was at 09:55 AM ----------
Try loading the firmware in all 4 slots of Odin and flashing, you could always extract the tar and make the 4 file flash seems to work a lot also you can get your PIT from twrp by typing in twrp terminal
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176
flash with stock rom if it throws an error about ext4 you'll have to get a PIT from someone with same device an storage capacity
Sent from my LGLS676 using Tapatalk
rick.wardenburg said:
That's not good I'm sure it means it failed to verify using pit, when you have phone plugged in USB and on download mode go to your device manager screen in windows and check that your name of phone shows up correct, flashing a rom not ment for your device could of caused this by experience
Click to expand...
Click to collapse
Well, I saw different baseband versions for each firmware. I don't know how can I find my baseband version if my OS is wiped and can't check whatever information needed for it so I can get the correct firmware for it.
rick.wardenburg said:
That's not good I'm sure it means it failed to verify using pit, when you have phone plugged in USB and on download mode go to your device manager screen in windows and check that your name of phone shows up correct, flashing a rom not ment for your device could of caused this by experience
---------- Post added at 10:13 AM ---------- Previous post was at 09:55 AM ----------
Try loading the firmware in all 4 slots of Odin and flashing, you could always extract the tar and make the 4 file flash seems to work a lot also you can get your PIT from twrp by typing in twrp terminal
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176
flash with stock rom if it throws an error about ext4 you'll have to get a PIT from someone with same device an storage capacity
Sent from my LGLS676 using Tapatalk
Click to expand...
Click to collapse
Nope buddy its not device issue he is downloading wrong firmwares
Dont use sammobile
Its mixed all
Just move to updato.com
And install its firmware
U will pass odin all
Oves786 said:
Nope buddy its not device issue he is downloading wrong firmwares
Dont use sammobile
Its mixed all
Just move to updato.com
And install its firmware
U will pass odin all
Click to expand...
Click to collapse
I'm assuming he has right firmware flashing some ROMs and then Odin factory firmware will cause this also
Sent from my LGLS676 using Tapatalk
rick.wardenburg said:
I'm assuming he has right firmware flashing some ROMs and then Odin factory firmware will cause this also
Sent from my LGLS676 using Tapatalk
Click to expand...
Click to collapse
nope he downloaded the j710fn firmware from sammobile and samshung has 2 models named j710fn like on8 and j7 2016 so the firmwares are mixed on sammobie an the on8 firmware says cm.bin fail on j7 2016
and updato.co firmware works on j7 2016 so firmware is the issue
i also hadthat issue i too hav j7 2016
Well, thank you everybody for trying to help me out but I already got a custom rom in which works with the phone really nice, and sorry for bumping the topic.
I was trying by odin and MD5 and doesnt work, with odin it stoped at (ANND writing...) and with MD5 WTRP said verification invalid... i was trying for 2 weeks, rooted, twrp installed, bootloader unlock, please somebody help me
ssrickhunter10 said:
I was trying by odin and MD5 and doesnt work, with odin it stoped at (ANND writing...) and with MD5 WTRP said verification invalid... i was trying for 2 weeks, rooted, twrp installed, bootloader unlock, please somebody help me
Click to expand...
Click to collapse
Rename ODIN .tar.md5 file to just .tar. This skips md5 verification.
Skip MD5 verification in TWRP also
hello guys , id be grateful if anyone can help me .
im trying to fix my mother phone , the original problem was that the phone kept rebooting on the samsung galaxy j1 image . after reading on internet , i learned that i have to flash it , which i tried to do but failed . which put me on "the firmware upgrade encountered an issue " . after researching again , i found out i need to download a pit and twrp files , which fixed the problem . now it only boots in the twrp program .
so ive downoalded dozens of firmwares , but not even one seems to work ( the ones with the same firmware baseband fail on odin at .cache .img ) and the other ones fail at the start of system.img .
if anyone knows how to help id be very grateful
MS blades said:
hello guys , id be grateful if anyone can help me .
im trying to fix my mother phone , the original problem was that the phone kept rebooting on the samsung galaxy j1 image . after reading on internet , i learned that i have to flash it , which i tried to do but failed . which put me on "the firmware upgrade encountered an issue " . after researching again , i found out i need to download a pit and twrp files , which fixed the problem . now it only boots in the twrp program .
so ive downoalded dozens of firmwares , but not even one seems to work ( the ones with the same firmware baseband fail on odin at .cache .img ) and the other ones fail at the start of system.img .
if anyone knows how to help id be very grateful
Click to expand...
Click to collapse
anyone ?
MS blades said:
hello guys , id be grateful if anyone can help me .
im trying to fix my mother phone , the original problem was that the phone kept rebooting on the samsung galaxy j1 image . after reading on internet , i learned that i have to flash it , which i tried to do but failed . which put me on "the firmware upgrade encountered an issue " . after researching again , i found out i need to download a pit and twrp files , which fixed the problem . now it only boots in the twrp program .
so ive downoalded dozens of firmwares , but not even one seems to work ( the ones with the same firmware baseband fail on odin at .cache .img ) and the other ones fail at the start of system.img .
if anyone knows how to help id be very grateful
Click to expand...
Click to collapse
You Should have not flashed a pit file, it repartitons the phone and may lead to a Hard-Brick (thankfully it didn't)
i assume that you used a wrong pit file which missed up the partioning leading odin to not being able to flash the whole system, leaving you in the no os state.
but we are going to try to use a factory image frimware first
https://androidfilehost.com/?fid=24340319927534089
download this frimware then extract it
then flash ONLY and ONLY PDA file or maybe also be named as AP
if that didn't work a pit file maybe needed
-Hope- said:
You Should have not flashed a pit file, it repartitons the phone and may lead to a Hard-Brick (thankfully it didn't)
i assume that you used a wrong pit file which missed up the partioning leading odin to not being able to flash the whole system, leaving you in the no os state.
but we are going to try to use a factory image frimware first
download this frimware then extract it
then flash ONLY and ONLY PDA file or maybe also be named as AP
if that didn't work a pit file maybe needed
Click to expand...
Click to collapse
good evening , thank you so much for your help first of all
ive downloaded the file on the link you sent me and ive done just like you asked .
it passed on odin :
<ID:0/003> system.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
but it went directly to the firmware upgrade encountred an issue on the phone , does it mean is that this baseband isnt compatible with the phone ?
and since i couldnt in the begining access into the phone , ive only seen in the orginal recovery mode something like this ( ktu84p .j100fnxxuoaoc2 ) .
what can we do now ? and thank you very much again
MS blades said:
good evening , thank you so much for your help first of all
ive downloaded the file on the link you sent me and ive done just like you asked .
it passed on odin :
<ID:0/003> system.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
but it went directly to the firmware upgrade encountred an issue on the phone , does it mean is that this baseband isnt compatible with the phone ?
and since i couldnt in the begining access into the phone , ive only seen in the orginal recovery mode something like this ( ktu84p .j100fnxxuoaoc2 ) .
what can we do now ? and thank you very much again
Click to expand...
Click to collapse
what do u mean exactly ?
did the baseband change ?
is the sim detected ?
if you could capture what you have got too
https://drive.google.com/file/d/197pnfxR6wry52MadHBvkiBnABcKCKWFp/view?usp=drivesdk
-Hope- said:
what do u mean exactly ?
did the baseband change ?
is the sim detected ?
if you could capture what you have got too
Click to expand...
Click to collapse
no no , i just thought that i should tell you that this ktu84p .j100fnxxuoaoc2 )might be the original baseband.
and i dont really know how to verify if the sim i detected .
heres a picture of the phone after the flashing :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://drive.google.com/file/d/197pnfxR6wry52MadHBvkiBnABcKCKWFp/view?usp=drivesdk
MS blades said:
https://drive.google.com/file/d/197pnfxR6wry52MadHBvkiBnABcKCKWFp/view?usp=drivesdk
no no , i just thought that i should tell you that this ktu84p .j100fnxxuoaoc2 )might be the original baseband.
and i dont really know how to verify if the sim i detected .
heres a picture of the phone after the flashing :
Click to expand...
Click to collapse
Oh ok
use this guide to go through the problem
https://www.youtube.com/watch?v=LqoX7wNhotk
-Hope- said:
Oh ok
use this guide to go through the problem
https://www.youtube.com/watch?v=LqoX7wNhotk
Click to expand...
Click to collapse
Hey , i just tried it for the third time , it keeps failing at 95% .
is the phone broke totally ?
MS blades said:
Hey , i just tried it for the third time , it keeps failing at 95% .
is the phone broke totally ?
Click to expand...
Click to collapse
No I've faced the same problem
Try reflashing and boot
Then if it didn't
Reflash and flash twrp then
We may flash a custom ROM if you could boot it to twrp
-Hope- said:
No I've faced the same problem
Try reflashing and boot
Then if it didn't
Reflash and flash twrp then
We may flash a custom ROM if you could boot it to twrp
Click to expand...
Click to collapse
should i flash twrp without the pit file ?
because after the firmware upgrade encountred an issue , i always flash the pit file and twrp . it boots in the twrp .
i think we can try falshing a custom rom , because it boot sin twrp ?
MS blades said:
should i flash twrp without the pit file ?
because after the firmware upgrade encountred an issue , i always flash the pit file and twrp . it boots in the twrp .
i think we can try falshing a custom rom , because it boot sin twrp ?
Click to expand...
Click to collapse
Man,don't use pit files
Pit files are Dangerous and maybe kill your device
Flash WITHOUT pit files
-Hope- said:
Man,don't use pit files
Pit files are Dangerous and maybe kill your device
Flash WITHOUT pit files
Click to expand...
Click to collapse
oh okay thank you , i thought it was the only possible way.
i just flashed with only twrp , it booted in the twrp menu , after that i went in download mode , and tried kies again , it failed at 95% again .
MS blades said:
oh okay thank you , i thought it was the only possible way.
i just flashed with only twrp , it booted in the twrp menu , after that i went in download mode , and tried kies again , it failed at 95% again .
Click to expand...
Click to collapse
Try a reboot only
If that didn't work we can flash a custom rom
-Hope- said:
Try a reboot only
If that didn't work we can flash a custom recovery
Click to expand...
Click to collapse
a reboot from the twrp menu ?
MS blades said:
a reboot from the twrp menu ?
Click to expand...
Click to collapse
Yes
If that didn't work we can flash custom ROMs
I won't throw any device that boots
-Hope- said:
Yes
If that didn't work we can flash custom ROMs
I won't throw any device that boots
Click to expand...
Click to collapse
should i choose reboot system, recovery or power off ?
MS blades said:
should i choose reboot system, recovery or power off ?
Click to expand...
Click to collapse
System
-Hope- said:
System
Click to expand...
Click to collapse
it shows no os installed and then asks to install super su
MS blades said:
it shows no os installed and then asks to install super su
Click to expand...
Click to collapse
Use the ap file I provided and flash with Odin
Then flash twrp
And try to reboot from it
Don't use pit even experts don't deal with these