Hi,
I've just bought an atrix and would like to try GingerBlur... I followed the SBF flashing guide, but after RSD finished the first step (create image) phone showed up the following message: "sec_exception: febe, 35, 35" while RSD stopped "waiting for re-enumeration"... I freaked out and unplugged it. Fortunatelly everything is fine.
Is this message expected? Should I just wait longer or is there something wrong?
Regards,
Thiago Souza
tsouza said:
Hi,
I've just bought an atrix and would like to try GingerBlur... I followed the SBF flashing guide, but after RSD finished the first step (create image) phone showed up the following message: "sec_exception: febe, 35, 35" while RSD stopped "waiting for re-enumeration"... I freaked out and unplugged it. Fortunatelly everything is fine.
Is this message expected? Should I just wait longer or is there something wrong?
Regards,
Thiago Souza
Click to expand...
Click to collapse
This happened to me. I was using the usb ports on the front of my case. Apparently rsdlite does not like this very much. I plugged into the usb port directly to my motherboard in the back and smooth sailing from there. That could be your problem. You might also want to try uninstalling and reinstalling the drivers.
Hi,
Actually i'm using my notebook... but i think my priblem is that my current version (0.50.0) some how is not supported...
I think its has to do with USB on the front of the computer is usb 1.0 on the back its 2.0 on most notebooks there is 1 USB 2.0 and 2 USB 1.0. Most the time the side that only has 1 usb port is the 2.0 port
Hi,
Thanks for you tips, for I definitely can't do it, tried all my 3 notebook's usb port and got the same result ...
Regards
It looks like it was a compatibility problem... I could successfully install 1.4.2
it is a problem with the latin america atrix
Related
First off, I have read every thread mentioning error 260, every wiki about upgrading, and have not been able to fix my problem.
I am trying to upgrade to Schap's newest 6.0 ROM, not the 6.1. I currently have the OEM 5.0 ROM that came on the device from AT&T. I can connect via activesync perfectly. No issues there at all. When I run the upgrade program, it gets all the way to the status bar showing 0% or 1%, then the phone and computer disconnect the activesync connection, the phone goes back to the today screen, and my computer shows error 260.
I have seen posts saying I need to install HardSPL. I tried that and get error 260 there also.
I have seen posts about installing JumpSPL, I tried that and it only locks the phone up. I must do a soft reset to bring it back to life.
I found the instructions on upgrading the ROM via the SD card. I followed those and renamed the .nbh file and copied it to the fat32 formatted sd card in the phone. Where do the rest of the files go??? The .nbh file cannot possibly contain the entire rom, right? The instructions leave that part out from what I can see.
Help!
Device is a AT&T 8525. Thanks!
okeven said:
First off, I have read every thread mentioning error 260, every wiki about upgrading, and have not been able to fix my problem.
I am trying to upgrade to Schap's newest 6.0 ROM, not the 6.1. I currently have the OEM 5.0 ROM that came on the device from AT&T. I can connect via activesync perfectly. No issues there at all. When I run the upgrade program, it gets all the way to the status bar showing 0% or 1%, then the phone and computer disconnect the activesync connection, the phone goes back to the today screen, and my computer shows error 260.
I have seen posts saying I need to install HardSPL. I tried that and get error 260 there also.
I have seen posts about installing JumpSPL, I tried that and it only locks the phone up. I must do a soft reset to bring it back to life.
I found the instructions on upgrading the ROM via the SD card. I followed those and renamed the .nbh file and copied it to the fat32 formatted sd card in the phone. Where do the rest of the files go??? The .nbh file cannot possibly contain the entire rom, right? The instructions leave that part out from what I can see.
Help!
Device is a AT&T 8525. Thanks!
Click to expand...
Click to collapse
Try a different USB port first, fire the device into bootloader mode manually and see if the device is detected by windows as "HTC USB SYNC"........use a hardwired port NOT a USB Hub aswell.
I tried a different USB port. It is not being plugged in to an external USB hub. I went into the bootloader screen and my computer makes the sound that a USB device was plugged in and it does show in the device manager as "HTC USB SYNC". What now?
Now try to do an update, Sounds like a problem associated with the connection of the device to your machine...usually caused by messed up USB drivers or a conflicting program.
Just tried. Same error again. Tried restarting the computer and tried it again. No dice.
this is the answer
hey man, how u doing. I was getting those errors too, I actually have a Tilt, I got error 200, and 260 trying to change my rom, I was about to give up. then I tried something I didn't think of, I updated my device center software from Microsoft and then miraculously everything worked after that. If you have XP update your Active sync software to the latest one and everything should work after that. Hope this helps.
and one more thing, make sure you install HardSPL v1 (or later when its released) first before trying to install the ROM.
I don't think anything is wrong with your usb drivers
I had actually checked to make sure I had the most recent version already and I do. I cannot install HardSPL either, since it gives me error 260 there also.
Error 260 is an open port error... I believe you have already tried resetting your device, but have you rebooted your pc prior to this procedure... I am grasping at straws for you, since you said you have tried soft resetting to no avail... I believe MrVanx stated to put the phone in bootloader mode and try to run the update utility that way... It works for me...
Can you try this on a different pc? If so, does it work? I have a post on another forum that you might find interesting... I did not compile it on my own, but cannot recall where I got it from... anyway, the link is HERE...
Hope this helps you out...
I have restarted the computer multiple times. I just tried it on my laptop and that did not work. I can boot the phone to the bootloader, but how do I install it from there?
That should be the easiest part... once you have it in bootloader mode, connect it via usb and then launch the update utility...
I get error 260 doing that also. argh!!!
i know how u feel
i had your problem several times. you want to know how i fixed it?
i didn't...
first i tried everything you and the guys mentioned and... nothing. then it worked the next day by itself.
the second time i couldn't connect i was really mad because the errors came sporadically. i tried installing AS, uninstalling, hard resetting the device, changing usb ports, anything logical and illogical and it worked on changing usb ports (but not on the first change).
now i'm at my girlfriends, had no problems until i saw farias new rom and wanted to flash it. guess what connection error
p.s. i've read trough and trough, but i've found no solution
what version and OS?
okeven said:
I get error 260 doing that also. argh!!!
Click to expand...
Click to collapse
yeah, I thought u would dget that again. i don't believe the error is originating from your phone, its more from the computer. what operating system are you using and whats the version number for activeSync or MS Device Center you are using?
I had that error on my home pc and on my girlfriend's laptop prior to updating my device center software. My pc is running Vista ultimate x64 and my girlfriend's laptop is running Vista Home Premium x32. I'm on her laptop right now, the version of device center is 6.1.6965. when I get home I will see which version is on my computer, I remember seeing "beta" on the one I got at home, lol, I didn't know Microsoft sent out beta software through its msupdate.
okeven, someone replied with good suggestions to the thread that u accidentally started over in the kaiser forum. you might want to check that out
I have version 6.1.6965 also. It does not say anything about it being a beta version, but with Microsoft, isn't everything in beta stage?
I did try the "official wm6 AT&T" version. Upgraded just fine. Tried upgrading to another one. Failed with error 260. What is different with the official upgrade program compared to the unofficial ones. THAT is the problem.
help
hi guys,
i have the same problem always the code 260, and also, my tytn's screen become within light, and without any boot number, ni radio, anything appears, please help me,,
thanks,
Finnaly
Hi guys
I also have the 260 problem but i resolved it:
1º- connect pda and make a active sync connection
2º run RUU
3º the 3-color screen will appear and update will stop with the 260 message error. be sure you can install the "qualcomm cdma technologies msm driver" at this moment, by an internet connection.
4º after the driver is installed, the word "USB" will appear in the white strip of the 3 color screen;
5º run RUU again and that´s all!
I´ve tried it in windows 7 ultimate 32-bit
hi,
I had the same issue on my second flash... I resolved it by ignoring all .exe's (which I like in general).
So I copied the .nbh onto the card, renamed to Kovsimg.nbh, bootlader mode, done
cheers
lxlx said:
hi,
I had the same issue on my second flash... I resolved it by ignoring all .exe's (which I like in general).
So I copied the .nbh onto the card, renamed to Kovsimg.nbh, bootlader mode, done
cheers
Click to expand...
Click to collapse
Hermes use HERMIMG.nbh ... kovsimg.nbh is for Xperia X1 ..
Hi gys, I think that this is my first post, but I want to share some solution for with you. The most important think with "connection" errors is to have HSPL installed correctly. I was trying to install on my HD2 universal ones, like Hard spl v7 and 9, but problems occured. So after trying everything, I found HSPL (on this forum) just for HD2. After that, everything wass like a charm
I've been looking around the net for about an hour and have not gotten any answers.
The info:
-Running GingerBlur 4.5
-NOT Unlocked
-Using Windows 7 64bit
-Have used multiple versions of RSD Lite
-Moto drivers installed.
Whats the problem? RSD Lite 5.3 will NOT recognize my atrix when its plugged in. I have tried everything i know of (reboot device, PC, change USB ports, install and reinstall all drivers and RSD) and nothing.
It simply will not recognize my device, even though my computer does and says all drivers installed.
Im trying to unlock and flash a new ROM. Can Gingerblur possibly be causing the issue? Ive read that Win7 64bit may be the problem? Any and all help would be appreciated
i beleve its been updated to 5.5 and also install your drivers and use the usb plug in the back of your pc
EDIT ;;;;;;!Ican confirm its been updated to 5.5. when i googled rsd lite 5.5 it
was the first topic /download on xda
Sent from my MB860 using xda premium
I heard also that WIN7 64bit has some problems RSD.
Try using a different comp with lower WIN version (I know for sure that Vista 32bit works great).
I don't think that the GingerBlur can have any effect, its just a mod, something a little more complex then a theme. besides I unlocked my BL when I was running GladiAtrix, which is another mod, and it went without problems...
Good luck
ltdanno360 said:
i beleve its been updated to 5.5 and also install your drivers and use the usb plug in the back of your pc
EDIT ;;;;;;!Ican confirm its been updated to 5.5. when i googled rsd lite 5.5 it
was the first topic /download on xda
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
I have version 5.6 on my home computer. It is probably higher than that now as I have had it for a while.
I use Windows 7 64 bit without any problems.
You should definitely try a different USB port. There is a common issue of one USB port not seeing devices, whuile the port next to it does.
Uninstall the drivers and Motohelper if you have it, then reinstall Motohelper. I have found that installing Motohelper is better for driver install. You do not need to install the drivers seperately if you install Motohelper, as they are installed with Motohelper.
Boot into fastboot, connect your phone to your PC, bring up a command prompt and, in my case, I do 'cd C:\moto-fastboot' which is the location I have moto-fastboot at. (Obviously you need moto-fastboot on your PC). Then type in 'moto-fastboot devices'. If your computer sees your phone it will be listed and you should be good to go. The just 'moto-fastboot reboot' to reboot your phone.
Thanks for the replies, however i did use an older computer, Vista to be exact. It recognized my phone instantly, i flashed the SBF...
Failed to boot 2... FML
I've been looking all around and am currently going to flash the pudding 2.3.4 SBF. Is that a good call?
CaelanT said:
I have version 5.6 on my home computer. It is probably higher than that now as I have had it for a while.
I use Windows 7 64 bit without any problems.
You should definitely try a different USB port. There is a common issue of one USB port not seeing devices, whuile the port next to it does.
Uninstall the drivers and Motohelper if you have it, then reinstall Motohelper. I have found that installing Motohelper is better for driver install. You do not need to install the drivers seperately if you install Motohelper, as they are installed with Motohelper.
Boot into fastboot, connect your phone to your PC, bring up a command prompt and, in my case, I do 'cd C:\moto-fastboot' which is the location I have moto-fastboot at. (Obviously you need moto-fastboot on your PC). Then type in 'moto-fastboot devices'. If your computer sees your phone it will be listed and you should be good to go. The just 'moto-fastboot reboot' to reboot your phone.
Click to expand...
Click to collapse
I probably should have just tried that before flashing the pudding SBF. Hmm, its currently executing the file, so im kinda SOL at this point.
I upgraded to 5.5 RSD and it still wouldnt pick up my phone? Tried multiple USB ports. Its not my computer not recognizing it, because it chimes and picks up my phone just fine...its RSD.
Well, after flashing the pudding 2.3.4, its stops loading at the white ATT screen, phone will not continue booting. Suggestions?
How long on that screen?
It can take 10-15 minutes to boot up after flashing.
erick161 said:
I've been looking around the net for about an hour and have not gotten any answers.
The info:
-Running GingerBlur 4.5
-NOT Unlocked
-Using Windows 7 64bit
-Have used multiple versions of RSD Lite
-Moto drivers installed.
Whats the problem? RSD Lite 5.3 will NOT recognize my atrix when its plugged in. I have tried everything i know of (reboot device, PC, change USB ports, install and reinstall all drivers and RSD) and nothing.
It simply will not recognize my device, even though my computer does and says all drivers installed.
Im trying to unlock and flash a new ROM. Can Gingerblur possibly be causing the issue? Ive read that Win7 64bit may be the problem? Any and all help would be appreciated
Click to expand...
Click to collapse
I tried also to use Rsdlite on my Win 7 64bit laptop without any luck. My other laptop with same software installed normally works but not the one I had with me at the time. I ended up using a very old XP laptop with shattered screen and no battery and worked like a charm.
I had exactly the same problem with Motorola software update as well. On Some machines they simply refuse to work.
Have you tried booting in RSD Support mode?
Turn the phone off.
Push Volume + rocker and keep it pressed while turning the phone on.
That will boot up the phone in RSD mode and I've always had success with that method.
Hope that helps.
CaelanT said:
How long on that screen?
It can take 10-15 minutes to boot up after flashing.
Click to expand...
Click to collapse
Yeah...I reflashed it when i thought it wasnt working, left it alone and it booted up just fine. Running pudding 2.3.4 GingerBread...
CSharpHeaven said:
I tried also to use Rsdlite on my Win 7 64bit laptop without any luck. My other laptop with same software installed normally works but not the one I had with me at the time. I ended up using a very old XP laptop with shattered screen and no battery and worked like a charm.
I had exactly the same problem with Motorola software update as well. On Some machines they simply refuse to work.
Click to expand...
Click to collapse
yup, my computer still will not recognize it! Only my old netbook w/ XP.
noobsquared said:
Have you tried booting in RSD Support mode?
Turn the phone off.
Push Volume + rocker and keep it pressed while turning the phone on.
That will boot up the phone in RSD mode and I've always had success with that method.
Hope that helps.
Click to expand...
Click to collapse
RSD mode isnt the problem, getting RSD Lite on the computer to recognize the device is the problem.
In my experience, MotoHelper is the culprit. Find the drivers itself without motohelper and try. I figured this out putting a Photon in diag mode, it wont let me read, said the port was already opened. Well was the motohelper service.
Uninstall all drivers and install just Motorola Drivers:
http://handheld.softpedia.com/get/Drivers/Motorola-Handset-USB-Driver-for-Windows-32-bit-38123.shtml
or the 64 bit version.
Hope it helps
pmcnano said:
In my experience, MotoHelper is the culprit. Find the drivers itself without motohelper and try. I figured this out putting a Photon in diag mode, it wont let me read, said the port was already opened. Well was the motohelper service.
Uninstall all drivers and install just Motorola Drivers:
http://handheld.softpedia.com/get/Drivers/Motorola-Handset-USB-Driver-for-Windows-32-bit-38123.shtml
or the 64 bit version.
Hope it helps
Click to expand...
Click to collapse
There are so many contradicting things w/ RSD lite and Win7 64bit. I ended up just manually installing the drivers, still wouldnt work on my PC, had to us XP on my netbook.
I flashed pudding 2.3.4 last night and tried messing with Rom Manager, but it says my phone no longer has root priviledges (had root previously, was running gingerblur 4.5). Superuser is installed on my phone however. Rom Manager states...
"you must root your phone for ROM manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin/su". Use Google Search on your computer to find instructions to root your phone."
How should i reattain root? The SBF was supposed have root preinstalled i thought. Can i flash the BL unlock, use Rom Racer and flash Darkside or something? Or will i not have root still?
I havent quite kept up w/ the Atrix development since the BL was unlocked, and there seems to be many methods and multiple uncleaned threads.
Now this thread is no longer about RSD...but basically restoring root without flashing the wrong thing and bricking my device.
yea when I went from gingerblur gingerbread. I had to re root I just used gingerbreak again and it worked
Sent from my MB860 using xda premium
Change to USB 2.0
Change to USB 2.0
So, My SGS2 was fine, just a few problems with connecting to my MacBook Pro (bootcamped Win7 & Odin), but after a few attempts it would always connect. I tried to update a rom to the new leaked ICS build via Mobile Odin, but something went wrong and all the charging images failed drawing.
Anyways, yesterday I tried to flash a recovery image via odin, to get back to my NAND and it failed halfway through (dodgy connector on SGS2).
Tried it a second time, and failed on flashing kernel.
I can access download screen, but windows refuses to recognize the phone, installing drivers for a "unknown device".
Tried flashing a kernel through OSX Lion and Heimdell, but it keeps failing to either find a device in download mode, or "claiming interface failed"
I've brought a new cable, but i have a feeling my USB port on the SGS2 has gone. Any help? Insurance most likely won't cover because it now says (2 Custom Binary Downloads) and they don't cover, and surely warranty has voided too.
Please help?
I will make a donation to the the person who can help me.
new leaked ICS build via Mobile Odin
Thats a test pre beta build guess its the problem .
Looks a usb driver problem that what you try .
remove Kies reboot reinstall Kies connect phone in download mode and let windows find drivers .
jje
try reinstalling kies. Or better yet use another computer for flashing. Can you boot into recovery mode? If so try flashing a custom rom to try to boot up your phone for the mean time
Sent from my GT-I9100 using xda premium
@JJEgan
Kies idea isn't working. My guess is the fact its 64bit Win7 on MBP bootcamp.
Or at least I'm hoping. Won't get to a desktop computer till monday, so had to buy a cheap backup phone.
@ephraim033
Flashing the new rom removed recovery, and can only access download mode.
I just get a screen saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again".
So far, I have noticed I either restart the computer (after uninstalling failed "unknown device" driver) and/or leave it for a while, and bam, it searches for drivers for the phone when I retry , but it seems to be related to pure luck with the positioning of the cable into the phone.
I have cleaned it several times with canned air and computing alcohol (i wont dare spell the name of it, and don't have the bottle to hand right now) so dust and debris is not the issue.
Edit: the failed driver comes up with "Windows has stopped this device because it has reported problems. (Code 43)" so I'm guessing i have to uninstall and reboot each time I try?
SOLVED. Have found the issue. Uninstalled KIES and all drivers. MEGA DEEP clean with a brand new dry tooth brush (infront and behind the protrusion within the usb port on both the phone and laptop).
Several reboots on both phone and laptop.
Second try, installed serial gadget and Samsung drivers automatically, installed CWM.
Many thanks
Danifamous said:
SOLVED. Have found the issue. Uninstalled KIES and all drivers. MEGA DEEP clean with a brand new dry tooth brush (infront and behind the protrusion within the usb port on both the phone and laptop).
Several reboots on both phone and laptop.
Second try, installed serial gadget and Samsung drivers automatically, installed CWM.
Many thanks
Click to expand...
Click to collapse
Glad you fixed it mate
Sent from my GT-I9100 using xda premium
I tried to install the update to 4.1, but wasn't on .211. I was on 215, so the update failed. I backed up and tried to restore to the very beginning of my backups, that failed and then I rebooted my phone. After that the phone will not turn on. I get the moto dual core screen, then it goes black. I can hold in all 3 buttons and bring up the ap fastboot...I've tried using RSD and razr utility, but the computer isn't recognizing my phone, it doesn't show up in RSD. In ap fastboot it says battery ok (after I've charged it), connect usb, data cable. Before I thought it said it was connected. Please help me!!??!?
I've always been pretty good at figuring out what I'm doing when it comes to rooting and flashing ROMS...guess I got too cocky...lol.
Try a different USB port. Make sure you're using the moto cable. Also try rebooting the computer. If that doesn't work we can try some other things too. PM me if you need help and I'll do my best.
~SU!C!D3~ on Tapatalk
swtkimmie said:
I tried to install the update to 4.1, but wasn't on .211. I was on 215, so the update failed. I backed up and tried to restore to the very beginning of my backups, that failed and then I rebooted my phone. After that the phone will not turn on. I get the moto dual core screen, then it goes black. I can hold in all 3 buttons and bring up the ap fastboot...I've tried using RSD and razr utility, but the computer isn't recognizing my phone, it doesn't show up in RSD. In ap fastboot it says battery ok (after I've charged it), connect usb, data cable. Before I thought it said it was connected. Please help me!!??!?
I've always been pretty good at figuring out what I'm doing when it comes to rooting and flashing ROMS...guess I got too cocky...lol.
Click to expand...
Click to collapse
It is hard to tell if it is showing up in RSD Lite. It doesn't show under "Device Properties"
It will show in the first column of the chart below under "Model" on the first line. Most of what it says there is hidden because he column is so narrow. Bbut if you widen the column it will say "blah, blah, blah, spyder"
I restarted my computer and it registered again, only for my phone battery to be low. I'm hoping it's charging, I have no way to tell.
In RSD there was nothing in any of the columns showing up. After restarting the computer it did show up. It just wouldn't do anything with my battery so low. I'm going to let the phone charge all night and try again tomorrow morning. Thank you for the help. Hopefully I'll be on here saying that it worked instead of asking for more help!
(How did I not think to restart my computer? Lol)
Ok, another problem. My phone was plugged in all night and didn't charge. How am I supposed to charge it? Am I screwed?
It isn't bricked 'till it's bricked
Since you ran out of battery wou will need a factory cable to flash it back to .211, you could buy one on ebay or make it yourself with a disposable micro usb cable.
reading this thread could help you http://forum.xda-developers.com/showthread.php?t=1403100
Yea, that's what I was afraid of. My hubby tried to make me one, but instead of soldering, he tried to just connect the wires. That didn't work. Looks like I'm going to be forking out the money for a cable that I will (hopefully) only use once. Ugh! I feel so stupid right about now...lol. Thank you for all your help!! It's greatly appreciated!
If you have problems getting your phone to be recognized by windows, the droid rzr utility has the drivers you need included in the DRIVERS-REQUIRED folder.
For kicks I tried a GSI ROM on my Jelly 2. It worked well except GSI ROMs don't seem to work well with VZW. So I'm looking to revert to the stock ROM. I have gone through the guide they posted here https://drive.google.com/file/d/1qVlaYucvE44ZJqF1RCHGknEBQWy_Z65m/view and I have the drivers installed and the phone is recognized as "MediaTek PreLoader USB VCOM (Android) (COMx)". Using their flash tool linked from the doc, the tool recognizes the phone on COMx (x depends on which USB port the cable is plugged into) and when I click "Start All" in the tool, in about 3-5 seconds the progress bar fills red to 100% and says "DA" in front of it. Then at about 125s, "DA" changes to "DA ERROR" and that's the end of the process.
Here are some screenshots showing the port in device manager and the flash tool with the "DA ERROR".
I've tried this from different laptops and different cables (the one that came with the phone and a different USB-A to USB-C cable) with no joy. I'm working with their support, but the time difference means communication is slow.
I've tried this with the bootloader locked and unlocked.
The IMEI for the Jelly 2 was recognized as a Jelly Pro, so Unihertz support provided me with an OTA file and instructions for installing it by downloading it to the phone and the using their built in local flash option to install it. They also provided 2 new IMEI numbers that I manually entered after flashing the OTA. This all worked fine, but they note that the IMEIs will revert to their original values after a factory reset. This was done before I flashed the GSI ROM, so I'm mentioning it in case it gives insight into whatever "DA ERROR" means.
Has anyone gone through this process successfully and have any tips?
bra1niac said:
For kicks I tried a GSI ROM on my Jelly 2. It worked well except GSI ROMs don't seem to work well with VZW. So I'm looking to revert to the stock ROM. I have gone through the guide they posted here https://drive.google.com/file/d/1qVlaYucvE44ZJqF1RCHGknEBQWy_Z65m/view and I have the drivers installed and the phone is recognized as "MediaTek PreLoader USB VCOM (Android) (COMx)". Using their flash tool linked from the doc, the tool recognizes the phone on COMx (x depends on which USB port the cable is plugged into) and when I click "Start All" in the tool, in about 3-5 seconds the progress bar fills red to 100% and says "DA" in front of it. Then at about 125s, "DA" changes to "DA ERROR" and that's the end of the process.
Here are some screenshots showing the port in device manager and the flash tool with the "DA ERROR".
I've tried this from different laptops and different cables (the one that came with the phone and a different USB-A to USB-C cable) with no joy. I'm working with their support, but the time difference means communication is slow.
I've tried this with the bootloader locked and unlocked.
The IMEI for the Jelly 2 was recognized as a Jelly Pro, so Unihertz support provided me with an OTA file and instructions for installing it by downloading it to the phone and the using their built in local flash option to install it. They also provided 2 new IMEI numbers that I manually entered after flashing the OTA. This all worked fine, but they note that the IMEIs will revert to their original values after a factory reset. This was done before I flashed the GSI ROM, so I'm mentioning it in case it gives insight into whatever "DA ERROR" means.
Has anyone gone through this process successfully and have any tips?
Click to expand...
Click to collapse
Answering my own question, while I could never resolve the DA ERROR running the SP TOOL on a Windows laptop, it worked running the Linux version from a bootable thumb drive on the same laptop. No idea on this one but I'm not going to dig any deeper. I used fireiso-2.0.0 as the bootable Linux thumb drive and downloaded the Linux SP Tool after the system booted up. Ran it with no changes to anything and it just worked.