Related
I'm trying to flash an updated modem on my i337M which is running a custom DANDVH-GE-4.4.2-01162014-INTNL-STOCK.ZIP which is a Google Play work alike. I am trying to change the modem because it keeps droping the data connection and will only stay stable in 2G mode. Right now its modem is on AMDJ. I've tried to flash both the XXUEMKF, XXUFNA1, modems but I keep getting the following error:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> modem.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Receive Response from boot-loader
<OSM> All threads completed. (succeed 0 / failed 1
I'm adding the modem.bin to the CP portion of Odin 3.09. I've tried doing this on all my USB ports using two new cables (all w/ the updated samsung drivers). I am using Win 8.1. All the same results. My phone says:
Code:
Odin Mode
Product name: SGH-I337M
Current Binary: Samsung Official
System Status: Official
CSB-OEM_CONFIG_LSB: 0x30
Write Protection: Enable
Then when I start flashing the following to messages appear right under the write protection message:
Code:
Start [224, 1440]
Secure Check Fail: mdm
After doing this I have to restart the phone for odin to pick it up again. It boots fine normally, and the original AMDJ modem still shows.
What's going on with this? I've looked in our forums but I can't find anything. I have TWRP installed, and I am rooted.
AHLASSICH said:
I'm trying to flash an updated modem on my i337M which is running a custom DANDVH-GE-4.4.2-01162014-INTNL-STOCK.ZIP which is a Google Play work alike. I am trying to change the modem because it keeps droping the data connection and will only stay stable in 2G mode. Right now its modem is on AMDJ. I've tried to flash both the XXUEMKF, XXUFNA1, modems but I keep getting the following error:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> modem.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Receive Response from boot-loader
<OSM> All threads completed. (succeed 0 / failed 1
I'm adding the modem.bin to the CP portion of Odin 3.09. I've tried doing this on all my USB ports using two new cables (all w/ the updated samsung drivers). I am using Win 8.1. All the same results. My phone says:
Code:
Odin Mode
Product name: SGH-I337M
Current Binary: Samsung Official
System Status: Official
CSB-OEM_CONFIG_LSB: 0x30
Write Protection: Enable
Then when I start flashing the following to messages appear right under the write protection message:
Code:
Start [224, 1440]
Secure Check Fail: mdm
After doing this I have to restart the phone for odin to pick it up again. It boots fine normally, and the original AMDJ modem still shows.
What's going on with this? I've looked in our forums but I can't find anything. I have TWRP installed, and I am rooted.
Click to expand...
Click to collapse
Hey there, I'm trying to update my I337M's modem as well (I have a post in this forum) so I'm in the same boat as you. From the looks of it, it seems like you're not using the correct modem firmware. If you'd want to update I believe it's something like UMUEMK6 for our phones, I've tried looking around and I can't find it anywhere. Hopefully that offers some direction but I'm waiting to see as well since I'm having the same problem with Google ROMs as well (The data signal never works).
Hello once again,
After a bit of work, I managed to update the modem on my phone to MUMUEMK6 (which is the newest baseband version for the I337M). Since flashing the modem firmware, I've re-installed Danvdh-GE-4.4.2-01232014b.zip and I haven't had a problem since, works without a hitch. What you need is this file which I've RARd up for you :
(Sorry, I have to obfuscate the URL since I'm a new user on these forums, just replace *dot* with a dot)
rtigue *dot* ca/files/SGH-I337M_MK6 *dot* rar
Once you've downloaded the file, simply just boot your phone in ODIN mode, open up ODIN, add the 'modem.bin' to the Phone section in ODIN and click Start. Wait a few moments and after that you should be good to go.
Let me know if anything comes up
For some reason, yours is the only version of the mk6 modem file that worked for my i337m after I was on 4.3 GE and went to old MDJ modem to try sim unlock. Which didn't work, sigh... Thanks!
SimonPalmieri said:
Hello once again,
After a bit of work, I managed to update the modem on my phone to MUMUEMK6 (which is the newest baseband version for the I337M). Since flashing the modem firmware, I've re-installed Danvdh-GE-4.4.2-01232014b.zip and I haven't had a problem since, works without a hitch. What you need is this file which I've RARd up for you :
(Sorry, I have to obfuscate the URL since I'm a new user on these forums, just replace *dot* with a dot)
rtigue *dot* ca/files/SGH-I337M_MK6 *dot* rar
Once you've downloaded the file, simply just boot your phone in ODIN mode, open up ODIN, add the 'modem.bin' to the Phone section in ODIN and click Start. Wait a few moments and after that you should be good to go.
Let me know if anything comes up
Click to expand...
Click to collapse
@ SimonPalmieri
Hello. I'm also running a rooted i337m (Bell) with 4.2.2 i337mvluamg1 stock rom.
Please let me know if the new modem MUMUEMK6 changes the bootloader with KNOX integrated.
Thanks.
jk2rd said:
@ SimonPalmieri
Hello. I'm also running a rooted i337m (Bell) with 4.2.2 i337mvluamg1 stock rom.
Please let me know if the new modem MUMUEMK6 changes the bootloader with KNOX integrated.
Thanks.
Click to expand...
Click to collapse
Bootloader and modem are not tied together..... MK6 is the latest modem and works with 4.4.2 roms (for I337M), once the actual 4.4.2 update drops for i337m we will be able to update to that modem.
Thanks for replying Gage_Hero.
So I'm then assuming that it's NOT a good idea to flash the mk6 modem.bin on my current rom?
MK6
jk2rd said:
Thanks for replying Gage_Hero.
So I'm then assuming that it's NOT a good idea to flash the mk6 modem.bin on my current rom?
Click to expand...
Click to collapse
First you need to decide if you want to sim unlock the phone, still possible on mvluamg1, not possible on MK6. I would make sure you have a copy of modem.bin for mvluamg1 first, just incase. Then flash the MK6, I run MK6 on 4.4.2 GErom since we don't have a kitkat modem for i337m yet... once there is I will be updating.....
PS if you can find files that have md5 checksum, that is always good because then you can check the file to make sure it is complete. I had that issue flashing the MK6 modem, first file I downloaded failed in Odin, plus it had no md5 for me to check. Second one I donwloaded had the md5, which I checked and it flashed perfectly....
I need help how Change Product Name GT-I9500CHN TO GT-I9500
I try Sboot but on KK version Not working show error when i write sboot
<ID:0/012> Added!!
<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> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> sboot.bin
<ID:0/012> NAND Write Start!!
<ID:0/012> FAIL!
Click to expand...
Click to collapse
and in phone ( SW REV: Invalid Magic String
There is any other sboot file for KK version or other solution thanks in advance
still waiting for solution anyone help me
imeicodes said:
I need help how Change Product Name GT-I9500CHN TO GT-I9500
I try Sboot but on KK version Not working show error when i write sboot
and in phone ( SW REV: Invalid Magic String
There is any other sboot file for KK version or other solution thanks in advance
Click to expand...
Click to collapse
Hi mate,
Not 100% sure what you want to do but as far as i know the only difference between the Chinese version and the international was the PIT , in the Chinese the internal SD is bigger about 11.5gb
If you want to use the non chinese rom you have to change the PIT
Check here.
http://forum.xda-developers.com/showthread.php?t=2265477
Thanks for reply
u read that thread but my firmware version updated on Kitkat 4.4.2
And there is available Sboot to 4.2.2 u have 4.4.2 Sboot Firmware
Code:
Note 6: If you flash I9500 stock firmware for China region, it will flash sboot.bin with it, that leads to have a Chinese bootloader (download mode will be in Chinese language and boot splash name will change). Even if you flash other stock firmware, it will not change the bootloader. So flash "GT-I9500_sboot.tar" (attached) as pda in Odin and it will fix the issue. (works on 4.2.2 firmwares!)
imeicodes said:
Thanks for reply
u read that thread but my firmware version updated on Kitkat 4.4.2
And there is available Sboot to 4.2.2 u have 4.4.2 Sboot Firmware
Code:
Note 6: If you flash I9500 stock firmware for China region, it will flash sboot.bin with it, that leads to have a Chinese bootloader (download mode will be in Chinese language and boot splash name will change). Even if you flash other stock firmware, it will not change the bootloader. So flash "GT-I9500_sboot.tar" (attached) as pda in Odin and it will fix the issue. (works on 4.2.2 firmwares!)
Click to expand...
Click to collapse
Hi,
That is a different case , that is if you wish to keep the old firmware
I would flash the PIT with a the NEW firmware
Note 2: If you have a corrupted partition table (Odin says: "there is no pit partition" or "Re-Partition operation failed"), flash pit file for your device (attached, dont forget to unzip it) (put it in pit window) with your firmware (some users reported that it worked without firmware), in this case "Re-Partition" must be marked.
Select the new firmware plus select PIT on Odin ..so it will flash the new firmware with the already included sboot with the new Partition tables (PIT)
Flash it all together
Hello,
My phone got stuck in a boot loop suddenly, during normal use.
Now I am trying to get it working again.
I have tried several tutorials to reflash stock firmware/unbrick the phone but without any success.
Now I am at a point where I have no idea how I should continue. Maybe someone of you guys can help me what I can try next, before I have to accept that it's dead.
I am able to boot into download mode, not into recovery mode.
When I am trying to turn on the phone the error "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again".
When I am trying to flash a stock firmware file (I9505XXUHOJ2_I9505ATOHOJ1_ATO or I9505XXUFNB9_I9505AUTFNA2_AUT) Odin starts the upgrade and fails with Complete(Write) operation failed.
I have tried different cables, usb ports, odin version, with/without admin priviliges without any success.
Any ideas how i could get the phone running again?
Thx and br,
Christian
Flash the firmware in the BL/Bootloader location in Odin to resolve the "Firmware encountered an issue" warning.
Hello,
I have tried to flash my 1 file firmware with the BL button:
"There is no PIT mapping."
When I am adding a PIT file (so I am using PIT and BL) the error is "Complete(Write) operation failed." again.
Also I tried to extract the Bootloader from my 1 file firmware but i am not sure which file i should use (the tutorials are all referring to sboot.img). My firmware contains only
aboot.mbn
boot.img
cache.img.ext4
hidden.img.ext4
modem.bin
NON-HLOS.bin
recovery.img
rpm.mbn
sbl2.mbn
sbl3.mbn
system.img.ext4
tz.mbn
Any ideas?
Thx and br,
Christian
Take your phone in for service. It sounds like you have a hardware issue, especially if the PIT file doesn't work.
I have tried to flash with it with heimdall and it looked better than with odin:
J:\stefan\stefan\I9505XXUHOJ2_I9505ATOHOJ1_ATO\entpackt>heimdall flash --APNHLOS
NON-HLOS.bin --ABOOT aboot.mbn --BOOT boot.img --HIDDEN hidden.img.ext4 --MDM m
odem.bin --RECOVERY recovery.img --RPM rpm.mbn --SBL2 sbl2.mbn --SBL3 sbl3.mbn -
-SYSTEM system.img.ext4 --TZ tz.mbn --CACHE cache.img.ext4
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading APNHLOS
100%
APNHLOS upload successful
Uploading ABOOT
100%
ABOOT upload successful
Uploading BOOT
100%
BOOT upload successful
Uploading HIDDEN
100%
HIDDEN upload successful
Uploading MDM
100%
MDM upload successful
Uploading RECOVERY
100%
RECOVERY upload successful
Uploading RPM
100%
RPM upload successful
Uploading SBL2
100%
SBL2 upload successful
Uploading SBL3
100%
SBL3 upload successful
Uploading SYSTEM
100%
SYSTEM upload successful
Uploading TZ
100%
TZ upload successful
Uploading CACHE
100%
CACHE upload successful
Ending session...
Rebooting device...
Releasing device interface...
Now it hangs at the Samsung Galaxy S4 boot logo or shuts down immediately after the logo flashes up.
br,
Christian
@maschi86
Again, like @Strephon Alkhalikoi said, hardware issue.
Sent from my GT-I9500
krasCGQ said:
@maschi86
Again, like @Strephon Alkhalikoi said, hardware issue.
Sent from my GT-I9500
Click to expand...
Click to collapse
It's so hard to accept .
Thank you guys.
br, Chris
This is the latest firmware for Tmobile Galaxy Note 4. Flash it at your own risk
I am not responsible if your phone blowup or sing the national anthem.
Samsung Galaxy USB Driver
New N910TUVU2EQC1
MDSUM: f86917e3e1763e9fb59bba6ca642fb22
How to root this:
1. Odin TWRP "uncheck auto reboot in odin" pull battery out put back in.
2. Boot to TWRP by holding Volume up Power and Home key together.
3. Flash SuperSu or flash this by PVSGH rooted rom
Enjoy
"Install Xposed Framework"
Install this first as apk XposedInstaller_3.1.1.apk
Go this this thread and flash xposed framework
I install this Qb1 stock RomControl. you guys can try it
For SM-N910T
MDSUM: 0b38870b792e37de28d1c6de721f5543
Odin 3.1.1
TWRP 3.0.2.0
Use this guide for root HERE
MDSUM: 29358c76fd6de55c086eb67bb1bff418
New firmware for SM-N910T3 (N910T3UVS3EQB1) Download HERE
Thanks for sharing, is the bootloader locked? are we able to downgrade? Thanks1
The-Accountant said:
Thanks for sharing, is the bootloader locked? are we able to downgrade? Thanks1
Click to expand...
Click to collapse
I have N910t and its not lock. I don't know about t3. You can use the guide posted by Deexii HERE just find the latest supersu if you will. Its has a good battery life. Always full wipe after and before odin. Good luck
boot loader and modem parted out
I've parted out the bootloader (BL) and modem (CP) for this firmware for those who don't wanna update their system: https://www.androidfilehost.com/?w=files&flid=158710
I've not flashed these yet myself, but did the same thing for EPK2 and had no issues flashing them. I'll probably get to updating my 910t this weekend and comment here if I have any issues.
Screenshots
I know I'm kinda late but I thought I would throw up some screenshots of the description of the update for anyone interested.
I have t3 and I can i use the BL and CP from T build rather than the T3. thanks
I have a n910t and update it for odin but on startup it stays on the T-mobile screen. any ideas
**Forget it and start 10 minutes the first start
razholio said:
I've parted out the bootloader (BL) and modem (CP) for this firmware for those who don't wanna update their system: https://www.androidfilehost.com/?w=files&flid=158710
I've not flashed these yet myself, but did the same thing for EPK2 and had no issues flashing them. I'll probably get to updating my 910t this weekend and comment here if I have any issues.
Click to expand...
Click to collapse
Just tried the modem alone not HLOS and not the bl stuff and it seems to work okay w/cm14. LTE works and a call went through anyway. Thx for doing this I hate having to download 2 gigs just to get like 100K of files.. I'll probably update the bl and such soon..
(updated via heimdall not odin fwiw)
razholio said:
I've parted out the bootloader (BL) and modem (CP) for this firmware for those who don't wanna update their system: https://www.androidfilehost.com/?w=files&flid=158710
I've not flashed these yet myself, but did the same thing for EPK2 and had no issues flashing them. I'll probably get to updating my 910t this weekend and comment here if I have any issues.
Click to expand...
Click to collapse
I've since flashed bq1 bl&cp and everything is working fine, though I'm on emotion 14.1 which hsbadr keeps updated with the latest proprietary blobs.
razholio said:
I've since flashed bq1 bl&cp and everything is working fine, though I'm on emotion 14.1 which hsbadr keeps updated with the latest proprietary blobs.
Click to expand...
Click to collapse
Cool. I'll give it a try in the next day or two and report back.
Update: Got impatient.. Tried the rest:
$ sudo heimdall flash --ABOOT aboot.mbn --APNHLOS NON-HLOS.bin --RPM rpm.mbn --SBL1 sbl1.mbn --DBI sdi.mbn --TZ tz.mbn
....
Uploading ABOOT
100%
ABOOT upload successful
Uploading APNHLOS
100%
APNHLOS upload successful
Uploading RPM
100%
RPM upload successful
Uploading SBL1
100%
SBL1 upload successful
Uploading DBI
100%
DBI upload successful
Uploading TZ
100%
TZ upload successful
Ending session...
It auto-rebooted. SEEMS to be working, but it's been about 30 seconds of testing
BTW, for anyone reading this who wants to also flash to modem, just add --MODEM modem.bin to the list of files above.
I see Baseband version N910TUVS2EQB1 listed in About Phone so that's good too.
(also-- I notice that it unfortunately didn't fix the timezone thing-- I still have to manually set it to keep it from jumping back to GMT)
Also, quick question-- I notice that NON-HLOS seems to always be grouped with modem.bin-- although I flash the modem as a standalone by itself (and used an older one for months alone) and it never had an issue.. is there a reason those two are treated as a group? I think (but am not 100%) that the NON-HLOS stuff contains the key stuff in /vendor. It's been a while tho since I did it so maybe it's muddled in my brain
Edit: Also, for the record, I'm using the Heimdall from here: link... No wait, actually that's gone. I pushed my working Heimdall source to here. It may be fixed better upstream but this works on Note 4 for me.
Thanks for the upload. Much faster than Sammobile's download.
Thank you for posting the ROM, I appreciate it.
Anybody has the md5sum for the sammobile firmware?
rajil.s said:
Anybody has the md5sum for the sammobile firmware?
Click to expand...
Click to collapse
Look again @ the first page
Installing this gives me 2 phone shortcuts and 2 broken Knox container apps? What is this
fattire said:
Also, quick question-- I notice that NON-HLOS seems to always be grouped with modem.bin-- although I flash the modem as a standalone by itself (and used an older one for months alone) and it never had an issue.. is there a reason those two are treated as a group? I think (but am not 100%) that the NON-HLOS stuff contains the key stuff in /vendor. It's been a while tho since I did it so maybe it's muddled in my brain
Edit: Also, for the record, I'm using the Heimdall from here: [email protected]:SaburoJiro/Heimdall.git... No wait, actually that's gone. I pushed my working Heimdall source to here. It may be fixed better upstream but this works on Note 4 for me.
Click to expand...
Click to collapse
Wish I had something intelligent to say on NON-HLOS, but I suspec the components of CP and BL are grouped together because of possible interdependencies, not that they necessarily have to break when out of sync, but the possibility exists. I've worked on build systems, and that's how I would define build artifact units.
Thanks for the heimdal links. I'd prefer not to ever have to fire up my aging winxp VM, but in the past, my heimdal attempts have always failed to identify my samsung products. I'll give this one a try.
Uh is anyone else's phone shortcut missing from the lockscreen?
I can't get this to flash, I have an N910T. Odin does recognize my phone, it shows the blue indicator. I'm using the AP box in Odin. The blue bar moves a bit, then stops cold. I checked the MD5, it matches what OP posted.
Samsung USB driver v1.5.45.0 (downloaded from Samsung's website)
Odin v3.11
Odin log:
<ID:0/005> Odin engine v(ID:3.1101)..
<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> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've also tried different cables, different USB ports, no go. I bought this phone brand new in factory-sealed box from a reputable seller on Amazon. I'm pretty sure it's not a fake/clone.
Please help, I don't want to be stuck with a brick that I've only had for less than 24 hrs!
AnonVendetta said:
I can't get this to flash, I have an N910T. Odin does recognize my phone, it shows the blue indicator. I'm using the AP box in Odin. The blue bar moves a bit, then stops cold. I checked the MD5, it matches what OP posted.
Samsung USB driver v1.5.45.0 (downloaded from Samsung's website)
Odin v3.11
Odin log:
<ID:0/005> Odin engine v(ID:3.1101)..
<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> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've also tried different cables, different USB ports, no go. I bought this phone brand new in factory-sealed box from a reputable seller on Amazon. I'm pretty sure it's not a fake/clone.
Please help, I don't want to be stuck with a brick that I've only had for less than 24 hrs!
Click to expand...
Click to collapse
Download this and unzip use Odin N910TUVS2EQB1_N910TTMB2EQB1_TMB-v6.0.1.zip
@gmenik6: Thanks, but I got the issue fixed without your zip. I got my file from SamMobile, the only source I really trust. It had the same MD5 as what OP posted.
I had to use a cable from my LG v10, it looks like all my other cables are shot. I'm just surprised that the cable that came with this new phone couldnt cut it, but it charges fine. The ROM flashed and booted fine. But now I'm running LineageOS.
Thanks again!
I was going through the posts and realized how helpful you were to a noob like me who helped me to install a stock custom rom i think i forgot to turn off the updates or something apprently my phone was initially stuck in bootloader the atnt now it wont even show the atnt logo keeping my fingers crossed that i havent screwed my phone
My phone can go in the android system recovery <3e>
LRX22C. I337UCUGOC3
if i am not wrong i cant just install any custom rom since bootloader is still locked i dont know for sure
in the screen below
#manual mode#
--applying multi-csc
applied the csc-code: ATT
Successfully applied multi - CSC
what have i tried uptill now
just wipe data/factory reset
can you help ?
Can you get into recovery mode? If it is just stuck booting to download mode only, then it sounds like you need to ODIN back to stock or use a debrick image. Your bootloader is locked so no TWRP recovery can be installed. You can use flash fire, which is like safe strap sort of, but your phone has to be booted into Android for it to work.
StoneyJSG said:
Can you get into recovery mode? If it is just stuck booting to download mode only, then it sounds like you need to ODIN back to stock or use a debrick image. Your bootloader is locked so no TWRP recovery can be installed. You can use flash fire, which is like safe strap sort of, but your phone has to be booted into Android for it to work.
Click to expand...
Click to collapse
i can get into recovery tried to sideload a rom gives some footer error
y2kyasir said:
i can get into recovery tried to sideload a rom gives some footer error
Click to expand...
Click to collapse
and signature verification error
StoneyJSG said:
Can you get into recovery mode? If it is just stuck booting to download mode only, then it sounds like you need to ODIN back to stock or use a debrick image. Your bootloader is locked so no TWRP recovery can be installed. You can use flash fire, which is like safe strap sort of, but your phone has to be booted into Android for it to work.
Click to expand...
Click to collapse
can you help ??
maybe i am installing not the appropriate rom ?
y2kyasir said:
can you help ??
maybe i am installing not the appropriate rom ?
Click to expand...
Click to collapse
You are on the OC3 bootloader right? Try to install golden eye ROM, which is touchwiz based. Since the bootloader is locked, you can only install touchwiz based ROMs and I think Google play edition ROMs. Trying to install cyogen mod or any other AOSP ROM won't work. Have you tried finding the debrick image or the stock ODIN tar file? With all those errors, I would try one of those routes.
StoneyJSG said:
You are on the OC3 bootloader right? Try to install golden eye ROM, which is touchwiz based. Since the bootloader is locked, you can only install touchwiz based ROMs and I think Google play edition ROMs. Trying to install cyogen mod or any other AOSP ROM won't work. Have you tried finding the debrick image or the stock ODIN tar file? With all those errors, I would try one of those routes.
Click to expand...
Click to collapse
i am on on nb1 since i did try to get it back to stock rom i found in the forums bootloader is locked i dont know about the debrick image but i am sure i did flash the stock odin tar from odin
i had no error everything went smoothly on odin 0 fail
i did download the rom put it odin everything went fine
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> sbl1.mbn
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> persdata.img.ext4
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> NON-HLOS.bin
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/005> Removed!!
StoneyJSG said:
You are on the OC3 bootloader right? Try to install golden eye ROM, which is touchwiz based. Since the bootloader is locked, you can only install touchwiz based ROMs and I think Google play edition ROMs. Trying to install cyogen mod or any other AOSP ROM won't work. Have you tried finding the debrick image or the stock ODIN tar file? With all those errors, I would try one of those routes.
Click to expand...
Click to collapse
and i know you are a pro so you can drag my noob ass out of this situation
Have you tried this thread?
http://forum.xda-developers.com/showthread.php?t=2674223
Is that the file you flashed in ODIN for NB1?
I'm no Android developer or anything, I just know the basic stuff. Most of what I know I learned from the XDA forums here.
StoneyJSG said:
Have you tried this thread?
http://forum.xda-developers.com/showthread.php?t=2674223
Is that the file you flashed in ODIN for NB1?
I'm no Android developer or anything, I just know the basic stuff. Most of what I know I learned from the XDA forums here.
Click to expand...
Click to collapse
yes https://forum.xda-developers.com/showthread.php?t=2674223
yes the rootable odin stock
but not the non root one
is there any specific time you guys are around so i dont have to wait days sorry a bit anxious to get my phone up and going
I am here off and on while I am at work Monday thru Friday 12 p.m. to 6 p.m. though my times will vary.