Develop Bugs

spv m2000 (no gsm)

hi i had another thread about this
http://forum.xda-developers.com/showthread.php?t=600587
basicly ive upgraded this unit and now have no gsm ive downloaded the software that i was advised but nothing works says files are corrupt or damaged , sometimes the link doesnt work . i need the factory rom for the orange spv m2000 i think can anybody help me pls
thanks.

since it seems to be the old problem, there was no need to open a new thread, you could have bumped the old one.
also, the answer is still the same. you can find shipped roms at http://xplode.tk
the fact that the wm2003 rom, offered in my tut thread, is corrupt, is aready known. i will fix that some time.

Chef_Tony said:
since it seems to be the old problem, there was no need to open a new thread, you could have bumped the old one.
Click to expand...
Click to collapse
i had on the 15/7/2010
i have downloaded the roms from this site for orange uk and get corrupt message i will take screen shot and show you. asap
thx for getting back to me
andy

this is the rom from http://xplode.tk for orange spv m2000 tried the mirror site and get the same message.
{
"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"
}

you cannot just download and double click it, i thought that was self explanatory. you need to right click the exe and extract it, in it you will find the ruu and the roms, then you take a custom ruu, like the Chef_Tony RUU from my signature and use that to flash.
also, since you are using windows 7 to flash the device, you need to install another driver and deactivate usb connections in wmdc. use d-two's tutorial on windows 7 flashing here: http://forum.xda-developers.com/showpost.php?p=5456317&postcount=6
or simply use a windows xp computer and follow the tutorial in my signature.
ts ts, just doubleclicking the exe, if it was that easy, there would be no need for a 30 step tutorial

i had extracted the files to a folder .. anyways ive got more picks to show this error . after doing what was said .

Chef_Tony said:
also, since you are using windows 7 to flash the device, you need to install another driver and deactivate usb connections in wmdc. use d-two's tutorial on windows 7 flashing here: http://forum.xda-developers.com/showpost.php?p=5456317&postcount=6
Click to expand...
Click to collapse
done everything the pdf asked with success yet i still cant extract my orange rom as pictures above show.

you didn't do everything from the instructions, you are still using BAupgradeut.exe.
you were supposed to use MAupgradeut_noID.exe.
also, i don't see the TEST MODE watermark on your desktop, which can mean several things:
1. you use windows 7 32 bit and everything went fine
2. you use windows 7 64 bit and removed the watermark already, also fine
3. something went wrong during the installation or you skipped a step.
you should straighten these 2 things out before attempting to continue.
also you should put the device into bootloader mode before flashing, charge the battery to 100% and remove both the sim and sd card, just a general advice, i don't know, if you already did that.
the problem, the ruu gives you, however, is not solvable with any of the tips given above. the extrom from the rom you downloaded, seems to be corrupt. the extrom is the file called ms_.nbf and contains carrier-related cab files like a custom wallpaper, dialer skin and other useless stuff. here are some ways to get rid of that problem:
1. resize the partitions using mtty and flash without the extrom:
1.1 with a full battery and without sim and sd card, put the device into bootloader mode
1.2 disable usb connections in the wmdc
1.3 start mtty (look it up in the wiki or through google)
1.4 select wceusb or usb, 115200-8-1-N-N-N, press ok
1.5 hit enter, so it shows USB>
1.6 type task 28aa
now, the partitions are back to factory defaults, close mtty and disconnect the device, still in bootloader mode
1.7 delete the ms_.nbf or move it to another folder
1.8 in bootloader mode, start the ruu and flash the rom and the radio rom.
method 2 is easier:
2. crc errors appear during corrupt downloads, maybe your connection speed fluctuated, maybe you use a wi-fi connection which swallowed a bit or two, or the file was actually corrupt to begin with, try another mirror, or maybe even another rom, there are many different english wm2003 roms at xplode's archive, your carrier is not important.
2.1 flash it using maupgrade, bootloader mode, without cards...

followed you last instruction to the letter and all is GOOD
thank very much

EVO on life support

Dear XDA Community,
This post will be as detailed as possible for those who enjoy detail.
It’s about the problems my EVO has been experiencing over the past 3 months and, after trying to fix the problems though IRC it seems that the attention should be brought to the forums for a larger audience. It was 3 months ago when I flashed a rom ( cannot remember the rom ) and my EVO took a turn for the worst.
What Happened :
When the rom was flashed and booted for the first time everything seemed normal but, the rom started to freeze at random. At first I though it was a normal process due to new ROM’s installs but, it kept repeating it over and over until it went into a boot loop syndrome.
Prior to these problems I did my daily clean/wipe dalvik rituals for ROM consumptions.​
After 15 - 30 boot-loops my battery dies and the crusade begins.
I begin looking for another ROM to flash, to rid the sickness the previous ROM infected my EVO with. I installed my favorite (SalvageMod) and, the problems began to show. Salvage installed perfectly fine (as always) but, my phone started to lag, the speed was reduced to about 35 - 50%. It’s noticeable big time. The camera stopped working and everything seemed to be falling apart.
(RECENT)In panic I started looking for ways to RUU so I can avoid any other problems. This is when I noticed that usb was not accessible. I couldn’t mount my device; [CLICK HERE FOR VIDEO], so I used a SD card reader to RUU my phone and get it back to stock.
Phone is back on stock settings but, no root and, without usb support revolutionary.io is lightyears ahead of my time.


Problems :
Not mountable through usb cable [SD Card Reader option / Software Error]
System lag noticeable slower (BestBuy rep even confirmed its unresponsiveness)
Device will not charge when on [Either mount / Software Error],
Camera problems.
[Click Here For Second Video]
{
"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"
}
So can you guys help a member get his EVO back in business, my wallet would greatly appreciate it.
Thanks,
samthewildone
Aspiring Mathematician

​

Well, the easy way out is that now that you're back on stock and a rep has agreed the phone is not working properly and you have no USB, trade it in

I would right click on that device and uninstall the drivers. then hook the phone up to the PC and see if it automatically installs the correct drivers or find better drivers.
This may have been covered, and it looks like there's a lot more going on then just drive issues, but to get this phone into a state in which you can root it and wipe it again, you need to eliminate that variable.
Not saying that the USB drivers are even an issue, but its something worth exploring first and foremost.

Tried that, as in my thread. I uninstalled and reinstalled drivers and, it just keeps showing what that picture shows above. The phone isn't damaged but, the software is borked due to a bad bad kernel or ROM flash.

Not a solution to your problem, but if you are still s-off then you don't need Revolutionary. You can put a PC36IMG of a (reliable, ie Amon Ra) recovery on your SD card. From there you can wipe thoroughly and try flashing something else.
Unfortunately it seems like some sort of hardware failure, so the only fix could be getting a replacement.
Supersonic Evo 4G | MIUI | Tapatalk

Seems like you've gone through the same steps I would've gone through to fix it. Apart from the possible driver issue the phone should still charge when plugged into a wall charger. The fact that it doesn't, in tandem with the inability to access USB via computer, tells me that most likely you've got a hardware failure. Take it to Sprint and get a replacement. Problem solved.

Bricked LG G3 - Need help!

Hi guys, I recently decided that i would root my phone and try and install cyanogenmod (new to me) as my phone seemed quite sluggish with LG's own bloatware on it. I followed the steps from LGG3ROOT and everything seemed to work well, and at the last stage when it asked me to then remove my battery and restart the phone... the phone just stayed on the lg page - never logging into the android system.
Ive tried to plug the device into multiple machines and each time the machines have issues with the device and it says the device has issue starting (10).
Im not really sure what else i can do as the phone seems bricked. Any help would be very much appreciated as i need access to the phone and i assume the warranty is now void.
Thanks in advance.

Walshinho said:
Hi guys, I recently decided that i would root my phone and try and install cyanogenmod (new to me) as my phone seemed quite sluggish with LG's own bloatware on it. I followed the steps from LGG3ROOT and everything seemed to work well, and at the last stage when it asked me to then remove my battery and restart the phone... the phone just stayed on the lg page - never logging into the android system.
Ive tried to plug the device into multiple machines and each time the machines have issues with the device and it says the device has issue starting (10).
Im not really sure what else i can do as the phone seems bricked. Any help would be very much appreciated as i need access to the phone and i assume the warranty is now void.
Thanks in advance.
Click to expand...
Click to collapse
can you post
the guide that you used to root
your phone variant
and whether it boots into download mode
what firmware version you were running

the guide i followed was this (exactly) http://highonandroid.com/android-smartphones/how-to-root-lg-g-flex-2-g2-g3-on-lollipop/
i have a UK D855
I can get it to download mode (but cant get to recovery with the power and down buttons)
unsure exactly which firmware, i hadn't played around with the phone until this happened.
when i let the phone get stuck on the lg page the windows pc seems to recognise the device, if i put it in download mode it comes up with the device error that it is there but cannot be run.
Thanks.

You probably have either
1) A bad usb cable
2) Or your drivers arent properly installed
You are plugging it into a USB2.0 port right?

I installed the drivers from the universal LG driver tool from their site, it worked find with the phone (or so it showed) before this issue, i've also tried a different cable and a different machine for it to come up with that same driver problem (10). Ive also tried uninstalling the driver software and reinstalling, is there a way to get rid of all traces of the bad drivers? thanks again for replying

Error Image
{
"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"
}

Working Fine
This is when the device isn't put into download mode and instead is left to try and boot (where it is stuck on the LG 'life's good' page).

Any idea guys? Im having no luck with any info im getting online at the moment and i'm really in need of this phone to work.
Thanks in advance.

Can you expand the "android device" section.
See if it's android adb

sorry, i think i quite understand. Which part should i expand on?
Thanks

In
device manager, look up Android device.

Update
The phone will now only go straight to firmware update and will never go or show the download mode as it has before. This is causing my LG Flash Tool to come up with 'cant change to download mode' and im not sure why or how this has happened.

The phone is now appearing fine on the device list. Its just the last of download mode. Is there a way to force it in cmd?

Please some screenshot again. The one I linked would be fine for adb

I see you can boot on download mode, so you can restore your G3 by applying a kdz firmware with flashtool2014: http://forum.xda-developers.com/showthread.php?t=2785089
On download mode the G3 is recognized only in ports (com&lpt)

Question Bricked phone - Need help ASAP

Hi.
So.... I ****ed up. I have accidently deleted all internal data on my phone, and I can't use MSMDownloadTool for resetting the phone. As I get the "Sahra Communication error".
I can get into fastboot.
Anyone who has some tips?

zXDexusXz said:
Hi.
So.... I ****ed up. I have accidently deleted all internal data on my phone, and I can't use MSMDownloadTool for resetting the phone. As I get the "Sahra Communication error".
I can get into fastboot.
Anyone who has some tips?
Click to expand...
Click to collapse
I did something similar with the non pro and oneplus replaced the phone, didn't even pay for shipping. Tried every msm tool available. My advice is to open a ticket with oneplus and see what they can do. That being said, my situation was different as it happens weeks after the phone was available (I think I broke it was even available in retail)
So that may have played a huge part of their generosity. I am in the US (may be applicable as well)
That being all said, I never lied to them nor was I looking for a replacement, I just wanted it fixed and assumed I was missing a step that the new phone may have added. I went through every trouble shooting suggestion and even scheduled a remote technician spot.
The technician refused to connect, though, because I downloaded the MSMToolkit he linked to me and said to download and install for it to be available when he remotely connected later. I noticed this technician (who was from germany, oddly enough) sent me a cracked MSMtoolkit (no sign in required like the official one I assumed they would use) the only difference being it was. answer variant the one available to us. So seeing I didn't have to wait for him to initiate it, all I did was attempt it, hoping into at least verify my system drivers were working and that I wouldn't be wasting his time. I replied to him his version was also giving me the error, only in hope he would be better prepared, like maybe it would let him know I needed some special driver or opened port on my network (but it was cracked anyhow)
He replied back in anger " who told you to try? I said to just extract and be ready. we will not assist you further and you are on the hook for any cost of repairs" and then closed my ticket.
I reopened the ticket asking why a technician, who from what I could gather, was a 3rd party service, making such statements on behalf of one plus? I also asked why the same technician was telling me to utilize cracked MSMtoolkits. Next thing I knew I had a next day FedEx label in my inbox to print and ship my phone out.
Maybe it was the timing, the the tech and me calling them out or maybe oneplus can easily fix the problem in house and decided to go that route.
Either way, there's no cost to opening a ticket with one plus, beyond language barriers and tedious preliminary troubleshooting. If you bought it at launch, id be concerned about the length of time and their desire to be as helpful. Not suggesting you lie but maybe just dont over share information.

If you searched, you'd see this :
Completely Bricked! Someone help
One plus 9pr complete brick. Cannot access fastboot or recovery. Will not turn on and when I plug in only shows a connect a chargwer screen. It is charged. I cannot get msm tool to connect either.
forum.xda-developers.com
Make sure you connect the USB cable directly to your computer, preferably in a USB 2.0 port, not via a hub.
Check the other stuff I mentioned in that post too. If you see the sahara communication failure, try rebooting the phone into EDL mode again while the software is running, it'll likely see it the next time. Also make sure you've selected your region in the top dropdown menu in MSM tool.
More info on EDL here : https://www.getdroidtips.com/5-methods-to-enter-edl-mode-on-any-xiaomi-smartphones-qualcomm/

djsubterrain said:
If you searched, you'd see this :
Completely Bricked! Someone help
One plus 9pr complete brick. Cannot access fastboot or recovery. Will not turn on and when I plug in only shows a connect a chargwer screen. It is charged. I cannot get msm tool to connect either.
forum.xda-developers.com
Make sure you connect the USB cable directly to your computer, preferably in a USB 2.0 port, not via a hub.
Check the other stuff I mentioned in that post too. If you see the sahara communication failure, try rebooting the phone into EDL mode again while the software is running, it'll likely see it the next time. Also make sure you've selected your region in the top dropdown menu in MSM tool.
More info on EDL here : https://www.getdroidtips.com/5-methods-to-enter-edl-mode-on-any-xiaomi-smartphones-qualcomm/
Click to expand...
Click to collapse
Not OP, and I truely hope this helps him fix the issue but when this happens to me, I know it wasn't in EDL, as did Oneplus. Thankfully they were open to replacing it for me, but that is nothing to assume ever happening again.

Also had this sahara communication error. Turns out it was just the method of connecting it for me.
What I did was put it into EDL mode with vol up and down for 15s and while holding the keys connect the USB with the software already running, and set to start. I don't remember the message but it said "waiting for communication" or similar, and it would immediately start the recovery when connecting the USB
I recommend this page with some more tips too.. https://www.droidwin.com/fix-sahara-communication-failed-error-msm-download-tool/

Hi
Try to use this tool (credit to craznazn, the developer):
lemonadep_22_I.07_210412.zip | by craznazn for OnePlus 9 Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Set the "Target" button to India, connect your dead phone using vol-up + vol-down + plug in USB, click Start...
I did unbricked LE2120, LE2125 well, using this tool you will get 11.2.4.4, then easily you can find the correct OTA firmware on your choice to be updated locally.
Regards,
xe
{
"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"
}

Question Missing second sim ( K50G / F4 GT )

I am very sorry to hijack a different device's forum, but XDA mods have neglected the F4 GT and we don't have a device forum of our own.
Hopefully the devices are similar enough (that being a modern Qualcomm SoC and running A12 based MIUI13) that you guys can help me solve my issue.
What happened is that I've been trying to enable voWiFi and make it stick while on airplane mode (WiFi re-enabled of course).
After a lot of back and forth with my carrier they did a kind of hard reset on my phone line. I didn't get 4/5G service for a long while, even after restarting multiple times, so I went to the test mode tool (dialing *#*#4636#*#*, which I've done several times before) and tried changing the preferred network type.
Out of desperation, after I nearly selected every other option, I selected TDSCDMA only, which is the only thing I've done differently compared to other times, and I got 4G and 5G working right after my phone did some funky radio reset (maybe a warning sign), but still no voWiFi. Decided to restart and that's when I lost the second sim slot, along with the voWiFi toggle, though it seems to connect just fine now.
Setting the preferred network type to anything else didn't solve the issue, even after several restarts the second SIM is still nowhere to be found.
After that happened the CIT menu shows both IMEI numbers as the same. (Had to censor it, but they are indeed the same).
{
"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"
}
I've read that a factory reset might solve this, but I'd prefer another solution in the meantime. I will factory reset when an AOSP based ROM is released but I don't really want to go through the huge trouble of setting up my device again if I can avoid it.
All other suggestions involve messing with some partitions on TWRP, and while I'm unlocked, rooted and have TWRP installed I don't see why I should go that route when I was using built in tools of Android/MIUI. I'm not entirely aware to the ways that test tool works, but I can't see any where it corrupted anything besides a configuration file somewhere, certainly not messing with any other partitions' files.
I've also read that some AT commands might fix this without messing with anything, but I can't wrap my head around what I have to do (I do know where I can issue those commands, just not the commands themselves and what each does). The page I read mentions it's a temporary fix and it doesn't persist after a factory wipe, but that's kind of what I need right now.
While I don't currently own 2 sims, I was going to get one soon, and if this is a deeper issue, I'd like to know ASAP so that I can restore my phone as it came from Xiaomi and send it to warranty.
And yes, I tried inserting my current SIM in the second slot and it's not detected at all.
Is there some config file I can delete/modify that will solve this? I've already re-flashed my current ROM (as it was also suggested somewhere) and nothing happened. I haven't tried flashing through fastboot, but I don't think it's going to be different, right? Is there something related to this that fastboot would flash that a recovery zip wouldn't? Also, not going to have access to a PC where I could do this for a while (I have a Ryzen PC and it doesn't play well with my phone/fastboot).
Hope you guys can help me.

Oh, no one? Maybe I should post this again on a more general sub-forum.
Or would it be better if it was moved by a moderator?

If you don't want to factory reset everything, why not flash system partition then only and keep app data?

dagoban said:
If you don't want to factory reset everything, why not flash system partition then only and keep app data?
Click to expand...
Click to collapse
Well I tried that and the problem persists; that's one of the many reasons I suspect it has something to do with some config file on the data partition.
I'm thinking on doing the factory reset anyway and try a GSI ROM through DSU, MIUI really gets to my nerves, though I'm still a bit on the fence

Reflash the modem files, that should fix it. If you make changes with QPST it also changes the modem partitions.

Can a moderator move this to the freshly created ingres device forum please?