For some reason my version says mi9 instead of mj5. I completed all steps except step 10 as I wanted to at least get back to nb4. Any idea on what may have happened???
{
"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"
}
Sent from my SAMSUNG-SM-N900A using Tapatalk
Just to be clear I completed @evilpotatoman steps
Sent from my SAMSUNG-SM-N900A using Tapatalk
zinupe14 said:
Just to be clear I completed @evilpotatoman steps
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
I have used those steps twice to get my phone back to MJ5. They work. There is either something your missing or you have upgraded to something different and are having issues going back.
but it does work.
Even the MI9 file included in the list?
Sent from my SAMSUNG-SM-N900A using Tapatalk
zinupe14 said:
Even the MI9 file included in the list?
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
Yes all files less the Mega one which is just a mirror to the MI9 fix anyway.
Got it. Didn't repartition. Thanks
Sent from my SAMSUNG-SM-N900A using Tapatalk
I was asked "forced" to update last night and lost my root. I was wondering if there was any way to get back to MI9?? THANKS
Where is this thread?? And is it up to date??
DirtTrash said:
I was asked "forced" to update last night and lost my root. I was wondering if there was any way to get back to MI9?? THANKS
Where is this thread?? And is it up to date??
Click to expand...
Click to collapse
Once you're on a new build its impossible to downgrade because the bootloader is locked. So sorry to say you're stuck. The builds ending with MJ5, and NB4 are android 4.3 jellybean and aren't bad at all! The 4.4 NC2, and MLG have quirks.
The restore to MJ5 thread is here http://forum.xda-developers.com/showthread.php?t=2559715
MI9 is Odin flashable and available here http://www.mediafire.com/?jmypf8ggtxu1a61
It's only good if you're still on MI9.
There is no restore method for any 4.4 versions. Just some modified NC2 or MLG roms available.
Related
Hi.
I have SIII mini with official JB 4.1.2, not rooted (installed using kies).
Today i received a notification for a 33.25 MB update.
Downloads fine but always fails to update around 28% of the installation.
What is this update and possible reasons why it fails?!
Thanks
slowdyve said:
Hi.
I have SIII mini with official JB 4.1.2, not rooted (installed using kies).
Today i received a notification for a 33.25 MB update.
Downloads fine but always fails to update around 28% of the installation.
What is this update and possible reasons why it fails?!
Thanks
Click to expand...
Click to collapse
Are you rooted?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
soulja4187 said:
Are you rooted?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for repying.
I'm not rooted. I just figure out what might be the problem. 4.1.2 TPH (free from carrier) for Portugal was released 59 days ago (when i updated using kies). But 4 days ago it showed up again, on "sammobile" and "samsung updates live", 4.1.2 TPH (Portugal). Here's the pic:
{
"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"
}
Since i can't update (from 4.1.2 to... 4.1.2 :silly: ) through OTA i'll try with KIES.
All went well using kies :good:
slowdyve said:
All went well using kies :good:
Click to expand...
Click to collapse
I'm glad
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
mine was updated too, no issues downloading with mobile data (29.5mb)
upgrade from:
4.1.2
i8190XXAMA2
3.0.31-809600
to:
4.1.2
i8190XXAMD3
3.0.31-1154865
(Belgium/Lux)
is there ANY way to know what changelog this update has? :/
I'm trying to unlock the bootloader of my C6603 and I keep getting errors or bootloops. My bootloader can be unlocked according to the attached screen.
I tried with Minimal ADB and I'm getting bootloops and with Sony Bootloader Unlock it's failing, according to this pic:
{
"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"
}
Drivers are installed correctly.
What's the catch?
Try using the fastboot package provided by DooMLoRD in his thread - http://forum.xda-developers.com/showthread.php?t=2153261
Also, the unlock key they send you is case sensitive, so double check what you're entering.
Sent from my C6603 using Tapatalk
I tried with DL's method and just tried with FT. STILL getting BOOTLOOPS !
Try flashing a stock FTF with full wipe, then try again.
Also, I just noticed that your IMEI number is in your screenshot. I would remove it from the image if I were you.
Sent from my C6603 using Tapatalk
Tried it. Still getting bootloops.
Then I can't think of anything else apart from trying a different USB cable/port or PC, but that probably won't make any difference.
When I unlocked my bootloader it worked straight away with no problems.
Sent from my C6603 using Tapatalk
It worked on my XS. Looks like this one is a mystery.
Edit: CLEAN flashed it and tried an other port. Worked. Thanks for the suggestion!
You're welcome.
Sent from my C6603 using Tapatalk
As I remember, flashing an unlocked-BL phone won't relock it, right? I'd like to relock it after gaining root on the .569.
That's correct.
Sent from my C6603 using Tapatalk
cipri92 said:
As I remember, flashing an unlocked-BL phone won't relock it, right? I'd like to relock it after gaining root on the .569.
Click to expand...
Click to collapse
Don't forget to backup your TA before you unlock the bootloader. Otherwise you'll loose your DRM keys forever and won't be able to re lock your bootloader
Sent from my C6603 using Tapatalk
Too late.
Hi,
I need help from all of you. Could anyone tell me what is your Phone Model?
I think it should be SM-N900A, but in my friend's phone it is SAMSUNG-SM-N900A, I'm not sure if it is original name or it has been modified.
You can install my app Phone INFO *Samsung* to get the Phone Model name. Download link in my signature.
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Sent from my SM-N9005 using Tapatalk
vndnguyen said:
Hi,
I need help from all of you. Could anyone tell me what is your Phone Model?
I think it should be SM-N900A, but in my friend's phone it is SAMSUNG-SM-N900A, I'm not sure if it is original name os it has been modified.
You can install my app Phone INFO *Samsung* to get the Phone Model name. Download link in my signature.
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
SM-N900A is mine.
htsl said:
SM-N900A is mine.
Click to expand...
Click to collapse
Yes, thank you, it should be.
Don't know why it is 'SAMSUNG-SM-N900A' on my friend's phone.
Anyone else please..
Sent from my SM-N9005 using Tapatalk
mine says SAMSUNG-SM-N900A
sfb14 said:
mine says SAMSUNG-SM-N900A
Click to expand...
Click to collapse
Really? The same as my friend's phone.
Why does it have a different model names for the same phone?!
Sent from my Nexus 7 using Tapatalk
is he running a custom rom? i am running Knoxraid
sfb14 said:
is he running a custom rom? i am running Knoxraid
Click to expand...
Click to collapse
Thanks for your info.
He is still running stock rom
Now you can see a list of all Samsung secret codes available in your device with this app (go to 'Secret Codes' menu).
{
"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"
}
My stock 4.3 says "SAMSUNG-SM-N900A"
My stock 4.4.2 says "SAMSUNG-SM-N900A".
Thank you all for your helps.
For the few of us who still haven't/won't/can't unlock the BL, which roms are safestrap/locked BL compatible?
I'm on Krypton right now, but is there anything else?
metaljr81 said:
For the few of us who still haven't/won't/can't unlock the BL, which roms are safestrap/locked BL compatible?
I'm on Krypton right now, but is there anything else?
Click to expand...
Click to collapse
Eclipse is the only other one I have seen.
How did you get safe strap installed, I'm guessing your not on 4.2.2
Sent from my XT1058 using Tapatalk
metaljr81 said:
For the few of us who still haven't/won't/can't unlock the BL, which roms are safestrap/locked BL compatible?
I'm on Krypton right now, but is there anything else?
Click to expand...
Click to collapse
Are you on 4.4.2?
Sent from my XT1058 using Tapatalk
{
"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"
}
Safestrap requires write-protect to be disabled, correct?
chrisp6825 said:
Safestrap requires write-protect to be disabled, correct?
Click to expand...
Click to collapse
Read the information thread.
http://forum.xda-developers.com/moto-x/general/ref-complete-moto-x-guides-information-t2603358
superp32 said:
How did you get safe strap installed, I'm guessing your not on 4.2.2
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
I just installed Safestrap v3.65 on my os v 4.2.2 with no problem and have done a complete system backup with it to the Moto X's internal SD card. I'm rooted and write protection is removed.
droidzer1 said:
I just installed Safestrap v3.65 on my os v 4.2.2 with no problem and have done a complete system backup with it to the Moto X's internal SD card. I'm rooted and write protection is removed.
Click to expand...
Click to collapse
I'm a tard I meant 4.4.2 , I thought someone figured out how to get safestrap with write protection but just wishful thinking lol
Sent from my XT1058 using Tapatalk
This is available for locked Verizon Moto X's still with write protect off and on the old bootloader - 4.4.2. This avoids updating the bootloader keeping write protect. http://rootzwiki.com/topic/116025-romsafestrap-unlockedxt1060-stock-rooted-vzw-164552-kitkat-442/
EDIT - Sorry I posted old information. Here is the latest safestrap stock ROM by the same Dev. 4.4.4 - http://forum.xda-developers.com/showthread.php?t=2829123
[ROM][SS & UL][4.4.4] Stock Rooted Vzw 212.55.26
Sent from my XT1060 using Tapatalk
I just want to be clear. If not, is it going to be possible to do in the future?
{
"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"
}
Thanks
northtracks said:
I just want to be clear. If not, is it going to be possible to do in the future?
Thanks
Click to expand...
Click to collapse
No root has been achieved. Gonna be awhile for root
Sent from my SM-G925V using XDA Premium HD app
northtracks said:
I just want to be clear. If not, is it going to be possible to do in the future?
Thanks
Click to expand...
Click to collapse
Predicting the future of development is impossible. A root method can appear 5 seconds from now, or 5 months, or never. People working on finding exploits do not post about it until they have a working method to post.
northtracks said:
I just want to be clear. If not, is it going to be possible to do in the future?
Thanks
Click to expand...
Click to collapse
You'll just have to wait until Marshmallow drops and a root exploit is found for that xP
I'm just hoping that we get root eventually for us that never had a chance to get the older one.
Sent from my SM-G925V using Tapatalk
lucky_strike33 said:
No root has been achieved. Gonna be awhile for root
Sent from my SM-G925V using XDA Premium HD app
Click to expand...
Click to collapse
So there is no way to root at all, not just a root that will not trip knox?
nebotmo said:
So there is no way to root at all, not just a root that will not trip knox?
Click to expand...
Click to collapse
correct.
No root for you. at least not until a new exploit is found.
Downgrading
Ok so I accidentally upgraded my phone to g925vvru2aof1 verison, and when I researched to see if I could root I found it wasn’t supported. My question is, can I downgrade this version to a version that you can root? Or am I stuck on this update? Thanks in advance for your help!