Hello everybody,
I just got a Samsung Nexus 9250 phone. I came to this forum to look for tutorials, tips, etc. I'm sure I will find a lot of interesting information around here.
After a few minutes using the device, I noticed that it had never detected my SIM card . My card works perfectly in my older phone. I tried with other people's cards and it happens the same. I have not been asked to input my pin code in any case. There is no message where I am asked to insert a SIM card.
This phone has never been manipulated (no jailbreak, unlock, etc). Then I tried with a hard reset, no. The "plane mode" is not activated.
If I search for available mobile networks / network operators, the phone finds the common ones. But if I try to choose one I get the message : "Unable to connect to this network at this time. Please try again later".
Other features (wifi, etc) seem to work OK. Except that I can't find any icon to use some kind of Android Market / Google Play.
Anyway my priority right now is to make the SIM card work.
So the question is : any ideas about how to make it work? Except, of course, some kind of hardware malfunction in the card reader.
Android version is 4.0.1.
Model number : GT-I9250_EUR_XX
Thanks in advance.
It is hard to believe, but it got fixed when I updated the firmware.
At the begining I tried with the tutorial in this thread :
(4.0.4 Unofficial Changelog *Update2 02/05*)
http://forum.xda-developers.com/showthread.php?t=1481044
But somehow my terminal did not like that version. I got some errors like :
-------------------------------
1.-
assert failed: file_getprop(”......
-------------------------------
2.-
- Install / sdcard …
Finding update package …
Opening update package …
Verifyng update package …
E: signature failed to verify wholefile
E: signature verification failed
Installation aborted.
-------------------------------
Which some people seem to have too.
Never mind, I could upgrade "only" to 4.0.2 and it worked like a charm. I suppose I will wait for 4.0.4 to be available globally.
Thank you very much to the community. You did not answer my question, but there is a lot of useful information out there.
Related
Error Description: send partition data failed
Info: .\RSPL\RSPL.cpp (802)
Error Description:
Info: .\RSPL\RSPL.cpp (545)
Click to expand...
Click to collapse
Many people had this error, although there are fixes offered but for many people, all the offered fixes did not work .. here is a suggestion that includes the previously offered fixes:
1. Disable your anti-virus and firewall
2. Re-download the NAND again
3. Remove Your SD Card
4. if installing from WM, run the MAGLDR 1.11 from WM (NOT FROM BOOTLOADER)
5. Plug your USB cable directly to your computer, do not use hubs or extension wires.
For me, the SD card was in and my anti-virus was on also, only the last 2 points worked after > 6 hours of trying and searching . To save time, just make sure you do the whole stuff
Hope it works with you
Two more working suggestions;
1) If you use the missing flasher files from mdeejay cyanogenmod7 daf build, you will be able to bypass that error while flashing your build of choice.
2) Also disable "allow usb connection" in activesync settings.
Sent from my HTC HD2 using XDA App
Did some research but nothing works
Hi folks, any new workarounds on this?? I did all I had to and am not a beginner... but nothing helped me passing by this error.
An error has occurred
Read below for more information
Error Description: send partition data failed
Info: .\RSPL\RSPL.cpp (1283)
Error Description: block send fail
Info: .\RSPL\RSPL.cpp (1091)
Error Description: flash write failed.
Info: .\RSPL\RSPL.cpp (710)
I am using correct radio, maldr 1.13 etc... disabled usb conn's run as admin, no -usb-hubs... all the way it should and the way I have done it several times.
flashing From Win 7
UseLast24NAND?
Hello
I don't know if someone is still after this and maybe my problem wasn't even quite the same, but I'll share. I was having this same error trying to install several WP7 ROMs; I was also show the error message 'Error Description: Block is after end.'. Anyways, I remembered that all WP7 ROMs I had ever used required you to go to MAGLDR > 10. Services > 4. UseLast24NAND. After doing this, everything was ok
Hey guys. After many frustrated days searching for a solution to "The timer ran out on what we were trying to do.", I found today an official solution posted by Microsoft.
So, for those with either:
800705B4: The timer ran out on what we were trying to do.
OR
80180080: We couldn't update your phone because your operating system might be corrupt.
search for "WPSupportTool" in google (Article ID: 2530409) and download for your Windows PC. (Sorry; can't post links!)
This is the best solution so far to update without erasing/reseting your phone. Enjoy!
From their article:
"Try using the Windows Phone Support Tool. The Windows Phone Support Tool is an application that fixes problems that prevent your Windows Phone 7 from updating successfully. The tool only works for the two error codes listed in the Symptoms section."
How can I use the WP Support Tool on Leo - HD2 > it doesn't have "camera button"
I've also been stuck with 800705B4 for months now. Very frustrating.
I believe I've tried everything...
I can't even unlock my SD card because I also get the 800705B4 error when I try to send the unlocker file via cab sender.
Well, I guess we just have to hope until there's a fix for the 800705B4 on HD2
if i use this tool (WPSupportTool) is it going to erase my phone ?
what about interop-unlock ? am i going to loose it ?
i'll really appreciate your answers
Erase phone: REALLY?? Read the first post:
"This is the best solution so far to update without erasing/reseting your phone."
Remove interop-unlock: highly unlikely, although a few updates do that for anybody.
The obvious answer is make sure you have a backup/restore point (if possible) so you can roll back if something gets messed up.
Hi,
I have been offered a generic phone in February 2014 by an office supplies retailer as part of a special offer.
The make is "SCOTT" and Settings>"About phone" gives me:
Model number: HWD-MP001
Android version: 4.2.2
Kernel version: MT6572
Custom build number: kp.HWD-MP001.v05
Recently, I have been having problems with my Samsung S4 so in order to test whether it was the phone (S4) or another factor, I wanted to start using the Scott phone.
Unfortunately, any adding of my Google account leads to two seemingly-related issues:
I get a "Google Talk authentication failure" message
I can't download anything from the PlayStore or upgrade any app because I get an "RPC:S-7:AEC-7" error.
Believe me, I have tried everything the entire Web suggests, including what the "get help troubleshooting" in the dialog that reports the "RPC:S-7:AEC-7" error says, to no avail. I've been on this for weeks now.
I had installed the Play Store APK in version 5.10.30 on the phone. But today, I noticed that the latest version on the S4 had changed to 6.0.0 so I downloaded it again from the S4 and installed it to the Scott phone. The installation failed without an error other than "App not installed", probably due to very low internal memory (15 MB...).
My question now is: how can I find an appropriate ROM for this phone? Checking for system updates is useless: either (through Software Updates) the phone does not even try to send a single packet over the Wi-Fi: it says right then "Your system is currently up to date" or (through "System updates) I get an additional "Network connection failed" message.
Thanks.
Hello everyone,
i bought the SM-P607T during my deployment in Afghanistan over Ebay USA . Spending my time there i tested the device and installed all updates etc. Back in Germany just my wife used it. Some weeks ago i noticed that an update to Lollipop should be avaible so i took the device to bring it up to date and i noticed some problems.
(Please note that i am just a noobie to flashing and rooting android and just follow guides to get to my goal.)
1. Device only loading while shut down. (After rooting and installation of TWRP it strangely started to load while on again even on PC USB connection)
2. Its not possible to connect the device with any PC.
3. OTA updates stop at around 27% and fail (KitKat 4.4.4)
[In TWRP shown
"E: Error executing updater binary in zip /data/fota/update.zip
E: Error installing zip file /data/fota/update.zip"]
Strange enough that the update info shown in android is Chinese Version
Tried to get some support with Samsung Europe but unfortunately they say US device US problem......
So what did i do in the meantime
1. Tried different loading devices frome Samsung and 3rd party companys. No changes.
2. Tried several different data cables to connect to 4 different PC. Even the one wich worked good with my Honor7 or the Galasy S4 mini dont do with the 607
3. My last try to fix this problem was to change the USB charging dock completely. Also didn´t change anything.
4. Now the step where i am currently stuck. I managed to root the device and install TWRP(v2.8.7.0) . Now tried to install Version P607TUVUBOI2 via SD Card.
Just followed diffenrent Guides on youtube and forums but im stuck at this.
Here is the message i got in TWRP recovery:
"Installing /external_sd/1/TMB-P607TUVUBOI2-20510930112901.zip
Checking for MD5 file....
Skipping MD5 check : no MD5 file found
Error flashing /external_sd/1/TMB-P607TUVUBOI2-20510930112901.zip
updating partition details......
Checked the *.zip on my PC there was just this file in: P607TUVUBOI2_P607TTMB1BOI2_P607TUVUBOI2_HOME.tar.md5
Downloaded the file from a different source again with same result
It would be very nice if someone is capable to help me with this and give me a hint what i possibly did wrong (Please do not mention not to buy in the US). For me it doesnt matter if i got a rooted or not routed version to install my main goal is to get rid of 4.4.2 . The problem with the not working USB connection is the biggest show stopper for me.
[email protected] said:
Hello everyone,
i bought the SM-P607T during my deployment in Afghanistan over Ebay USA . Spending my time there i tested the device and installed all updates etc. Back in Germany just my wife used it. Some weeks ago i noticed that an update to Lollipop should be avaible so i took the device to bring it up to date and i noticed some problems.
(Please note that i am just a noobie to flashing and rooting android and just follow guides to get to my goal.)
1. Device only loading while shut down. (After rooting and installation of TWRP it strangely started to load while on again even on PC USB connection)
2. Its not possible to connect the device with any PC.
3. OTA updates stop at around 27% and fail (KitKat 4.4.4)
[In TWRP shown
"E: Error executing updater binary in zip /data/fota/update.zip
E: Error installing zip file /data/fota/update.zip"]
Strange enough that the update info shown in android is Chinese Version
Tried to get some support with Samsung Europe but unfortunately they say US device US problem......
So what did i do in the meantime
1. Tried different loading devices frome Samsung and 3rd party companys. No changes.
2. Tried several different data cables to connect to 4 different PC. Even the one wich worked good with my Honor7 or the Galasy S4 mini dont do with the 607
3. My last try to fix this problem was to change the USB charging dock completely. Also didn´t change anything.
4. Now the step where i am currently stuck. I managed to root the device and install TWRP(v2.8.7.0) . Now tried to install Version P607TUVUBOI2 via SD Card.
Just followed diffenrent Guides on youtube and forums but im stuck at this.
Here is the message i got in TWRP recovery:
"Installing /external_sd/1/TMB-P607TUVUBOI2-20510930112901.zip
Checking for MD5 file....
Skipping MD5 check : no MD5 file found
Error flashing /external_sd/1/TMB-P607TUVUBOI2-20510930112901.zip
updating partition details......
Checked the *.zip on my PC there was just this file in: P607TUVUBOI2_P607TTMB1BOI2_P607TUVUBOI2_HOME.tar.md5
Downloaded the file from a different source again with same result
It would be very nice if someone is capable to help me with this and give me a hint what i possibly did wrong (Please do not mention not to buy in the US). For me it doesnt matter if i got a rooted or not routed version to install my main goal is to get rid of 4.4.2 . The problem with the not working USB connection is the biggest show stopper for me.
Click to expand...
Click to collapse
I really confused about your description? you using twrp to flash a .zip rom? then you mentioned about .md5 rom on your pc? how did you flash? With .md5 rom you need to use Odin to flash. Can you boot into download mode (hold down volume down + Home buttons then press power button)? If you able to boot to download mode, your pc should able to see the device and you would use Odin to flash the .md5 rom from your pc to the device. Also where did you download the .zip rom?
Hello,
while attempting to root my Blackview BV6000s (containing Mediatek MT6737T chip) I lost both IMEI's. Although I succeeded in rooting the phone, I was not able to restore the IMEI.
1) If I use Mediatek Engineering apk, when I send the string "AT+ EGMR=1,7,"IMEI_1″ I receive the error "This Command is not allowed in user build". I have read a lot of forum posts where they say to put a blank after "AT+", but it doesn't work placing the blank in any place: before or after the "+", or without blank at all. Always the same result: "This Command is not allowed in user build". I have tried all the versions of MTK engineering apk that I found inside and outside google play store
2) It is not possible to get any connection with "MTK Droid tool". Same result with MauiMETA
3) With SN write tool, when I plug the USB cable the phone powers on and the Blackview logo is shown, and after few seconds a red "FAIL" message is shown by the SN writer tool. It seems that the phone is not able to enter in "meta mode"
4) I have generated an IMEI file named "MP0B_001" and I have copied it in the right place with the root browser, but after the reboot the IMEI are still empty. I remark that when I try to set the write permissions, the root browses pops up an error message saying that the file system doesn't allow changing the permissions of the files. Then I packed the MP0B_001 in a zip file and I installed it with the TWRP recovery. The installation with TWRP doesn't show any error, but then after the reboot the IMEI are still invalid (null). Note: in ALL the posts that describe how to install the MP0B_001, they indicate /data/nvram/md/NVRAM/NVD_IMEI/MP0B_001 as the path where the file is stored. But in my phone the path is different, and precisely it is /nvdata/md/NVRAM/NVD_IMEI/MP0B_001. This makes me think that nobody have tried to apply this procedure to BV6000s. Anyhow, I tried to pack and install the zip with both paths, with the same unsuccessful result.
5) The only way I could write something in the 2 IMEI's is with Chamelephon. However there must be an incompatibility between Chamelephon and my phone. In fact, after applying the new IMEI's and rebooting, when reading the IMEI I find random strings instead of null strings. What is odd is that one of the 2 SIM cards succeeds in connecting with to the mobile networks and receive calls and SMS, even with this corrupted IMEI, while the other SIM still gives "invalid IMEI" error. I tried to find newer versions of Chameleon, but it seems that only version 1.0 exists
6) I tried to install all the ROM's that are compatible with MT6737T but the results of attempts 1-5 are the same.
In conclusion, it seems quite impossible to fix the IMEI. I have the impression that nobody tried to fix the IMEI on this specific phone, or that the producer has decided to "punish" whoever tries to root the phone, by preventing the repairing the IMEI. All the forum posts and guides, on which I based the attempts that I have described in this post, are not referring explicitly to BV6000s. Before resigning myself, I decided to create this post. Maybe it could be helpful also to other persons, if a solution exists and is described here.
Best regards
I have solved the issue and I am reporting here the solution for the benefit of those who should face the same problem.
I had to remove the encryption from the phone. I have installed the "no verity" package (no-verity-opt-encrypt-6.1.zip) with TWRP recovery and formatted the data section. This made necessary to reinstall all the applications from scratch. Further information: https://www.androidinfotech.com/no-verity-opt-encrypt-versions/
Then I used ghost phone (from google play store) to fix the IMEI; anyway after removing the encryption also Chamelephon was working.
***
Now I am in doubt whether I should restore the encryption.
If I restore the encryption, I am afraid that this could cause the loss of IMEI's again, or re-introduce some other annoying restrictions.
If I leave it not encrypted, I am afraid that my phone is more vulnerable to rootkits and similar malwares.