Develop Bugs

Error [270] - Update Error

Hello
I have a problem during update my xda.
Already my xda is working on OS 5.1.342 (build 15096.3.0.0)
I am trying update to Artemis touch 2.1 WWE or Artemis_Touch_3.01_full.
I follow the steps in guide (activesync then uspl cid unlocking) and (activesync then flash artemis touch rom).
When USPL is run screen on my xda is blinking and white light on the end, after restore itself.
On RomUpdateUtility i click next and next,
"Verify that you want to update the ROM version:
From: Image Version: 1.25.206.2
To: Image Version: 1.00.000.0"
Progress is running, but on 3% xda is restarting itself again.
And I see new window
"ERROR [270] : UPDATE ERROR
The image file is corrupted. Please check your Update Utility"
And EXIT.
Help me please.

Sorry for repeat question.
I hope I find the answer.
http://forum.xda-developers.com/showthread.php?t=311650&highlight=idiot
http://forum.xda-developers.com/showthread.php?t=313486
http://forum.xda-developers.com/showthread.php?t=312052&highlight=vista+drivers

continous reboot after attempting to upgrade.

Hi,
I was following http://forum.xda-developers.com/showthread.php?t=899450 to upgrade my defy to froyo 2.2 . After wiping out cache and data, it now goes to a reboot and does not load android. I see the M logo, after few seconds, reboot and again the M logo. This goes on and on.
When putting the system into recovery mode, I see the following error:
E: can't open cache/recovery/command
A search pointed to someone suggesting to format the SD card. I saved the data and formatted the SD card, in vain. The issue is still there. A search again in the forums suggested that I should use motolite and flash to to UK image.
I connected my defy to the RSD lite.
Results were following:
Device Properties:
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x000910
DRM Version: N / A
File Properties:
Filename: JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB02C.0R_USAJORDANRTGB_P035_A011_HWp3_Service1FF.sbf
Creation Date: 12/11/2010 06:21:14
File size: 380766623
RAM DL Version: v0x001000
Bootloader Version: -------------
Platform: 4G OMAP
HAB Type: Signed Production
Status:
Failed flashing process. Failed flashing process. Unable to retrieve initialization values from INI file. (0x7929); phone connected.
RESULT: FAIL
This phone is not under any contract, so I am free to test out ideas in order to solve this issue.
Please let me know how I can get the 2.1 version loaded there back, or a way to recreate the /cache/manager/commands.
Thanks.
Sam

I tested with a few more versions of RSDLite and one worked fine with version 4.0.1
Isn't there any sbf for 2.2 that can be used for defy ?
Thanks.

I'm using the orange deblur http://forum.xda-developers.com/showthread.php?t=940238
I tried using the nandroid backup first but got problem like yours http://forum.xda-developers.com/showpost.php?p=11282731&postcount=12. Then I used rsdlite to flash the 2.51.1 sbf to rescue the phone. After that I used rsdlite to flash the orange deblur sbf.
But note that after flashing the orange deblur sbf you cannot flash back to the 2.1 (2.51) sbf.

[Q] No computer recognizes my xperia play

[SIZE="<font><font>7</font></font>"]Hello people of XDA, I come to ask for help on my problem.[/SIZE]
My problem is that no computer recognizes my xperia play (R800a) I have tried everything and nothing, not recognized either in flash mode, is not in fastboot mode and SEUS does not recognize it, I tried rootearlo without PC and I think achieved but still I can not install CWM recovery, thought I could install CWM recovery but reboot my phone, lights the blue LED preciono the volume / down key and does not enter the recovery mode, any solution?
[SIZE="<font><font>6</font></font>"]Specifications of my phone: [/SIZE]
Xperia play (R800a)
Android 2.3.3
Baseband version: 7X30-AAABQMAZM-1290_21-22
Core Version: 2.6.32.9-perf SEMCUser @ SEMCHost No. 1
Phone Software Version: 1245-8821_3.0.1.A.0.145 GENERIC - user
File System Version: WORLD-1-2-5_3.0.1.A.0.145
S1 Boot Version: 1242-5099-10
Customization Version: 1247-6272-R11C
Memory card: No file found
Content Version: PA1
Type Number ADD-3880087-BV
And nothing about the Bootloader
: Crying: : Crying: : Crying:

hi
TraceurMcBeto said:
[SIZE="<font><font>7</font></font>"]Hello people of XDA, I come to ask for help on my problem.[/SIZE]
My problem is that no computer recognizes my xperia play (R800a) I have tried everything and nothing, not recognized either in flash mode, is not in fastboot mode and SEUS does not recognize it, I tried rootearlo without PC and I think achieved but still I can not install CWM recovery, thought I could install CWM recovery but reboot my phone, lights the blue LED preciono the volume / down key and does not enter the recovery mode, any solution?
[SIZE="<font><font>6</font></font>"]Specifications of my phone: [/SIZE]
Xperia play (R800a)
Android 2.3.3
Baseband version: 7X30-AAABQMAZM-1290_21-22
Core Version: 2.6.32.9-perf SEMCUser @ SEMCHost No. 1
Phone Software Version: 1245-8821_3.0.1.A.0.145 GENERIC - user
File System Version: WORLD-1-2-5_3.0.1.A.0.145
S1 Boot Version: 1242-5099-10
Customization Version: 1247-6272-R11C
Memory card: No file found
Content Version: PA1
Type Number ADD-3880087-BV
And nothing about the Bootloader
: Crying: : Crying: : Crying:
Click to expand...
Click to collapse
when blue light appears on led .... just tap on the screen

kks111 said:
when blue light appears on led .... just tap on the screen
Click to expand...
Click to collapse
I did, but still does not let me into recovery and still does not recognize any computer: Crying:

One M9 Demo Unit, how to convert

Hey guys,
I recently bought a used HTC One M9 DEMO UNIT from a private seller on eBay, which I'd like to convert to a normal phone. A HTC Demo App starts automatically right after boot-up that is not listed in the list of recently used apps and, therefore, cannot be killed, i.e. it's going to pop up every 2 minutes or so regardless of what else I do on the phone. This Demo App also cannot be removed, and additionally a lot of options on the settings menu are blocked. A factory wipe does not help, it only wipes all data and settings made previously, and restores everything including the Demo App to default settings.
The readme thread for One M9 phones states that I'm probably going to need S-OFF for the conversion in order to be able to change the CID. However, as the software and firmware versions of my device do not match those of any other demo unit I found on the net, I'd like to kindly ask someone with deeper knowledge to verify that I'm on the right track in the first place.
- I do need S-OFF to convert, right?
- Is this a GSM unit (as I believe it is, judging from the seller's location in Germany)?
- Can I convert directly to LineageOS or do I have to flash RUU/stock first?
- Is it possible/necessary/recommended to upgrade the firmware from 1.x to something more recent?
- Aside from that, is it generally safe to follow the conversion procedure described in post #5 of the Readme thread with this phone?
(Btw, Bootloader is unlocked via HTCDev, and a working adb/fastboot/HTC_fastboot environment is available on Linux and Windows 8.1, USB drivers are installed, HTC Sync thing not anymore).
Thanks,
Ras*
Additional questions, just out of curiosity:
1) Is it normal that booting to recovery is refused with an error message? ("Failed to boot to recovery mode. Press volume up or down to back to menu. This build is for development purposes only [...]" in red on a white HTC logo.)
2) Is it normal for such a unit that flashing or booting into TWRP 3.1.1.0-hima does not work using adb and fastboot (tried both the standard version of the tools, but also the HTC version)?
3) Could not flash RUU (RUU_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.30.617.12, from HTC website for unlocked/developer version of M9), this fails with error 127, signature error. What causes this, CID/SKU mismatch?
Information extracted from the device:
Bootloader:
Code:
*** Software status: Official ***
*** UNLOCKED ****
*** S-ON ***
Download mode:
Code:
htc_himauhl PCT S-ON
LK-1.0.0.0000
RADIO-01.01_U11440061_52a.01.50225G_2
OpenDSP-v20.2.6-00452-M8994_0216
OS-1.32.401.3
Feb 27, 2015, 15:11:23(493992)
Security checking failed NOT_FIND_SMARTIO
FILE /mnt/media_rw/ext_sd/0PJAIMP.zip
File NOT FOUND
System Info:
Code:
S/N **hidden**
IMEI: **hidden**
MB: 42E3552G07619
> fastboot getvar all
Code:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: **hidden**
(bootloader) version-main: 1.32.401.3
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__002
all:
finished. total time: 0.016s
Software:
Android 5.0.2
HTC Sense 7.0
Software number 1.32.401.3
Kernel 3.10.49-g864284c
[email protected] #1
SMP PREEMPT
Baseband version 01.01_U11440061_52a.01.50225G_2_F
Build number 1.32.401.3 CL493992 release-keys

Rastullah said:
I recently bought a used HTC One M9 DEMO UNIT from a private seller on eBay, which I'd like to convert to a normal phone. A HTC Demo App starts automatically right after boot-up that is not listed in the list of recently used apps and, therefore, cannot be killed, i.e. it's going to pop up every 2 minutes or so regardless of what else I do on the phone. This Demo App also cannot be removed, and additionally a lot of options on the settings menu are blocked. A factory wipe does not help, it only wipes all data and settings made previously, and restores everything including the Demo App to default settings.
Click to expand...
Click to collapse
That's normal. The demo app gets triggered by the unique CID demo units use (HTC__002). Without removing that CID you won't get rid of the demo app.
Rastullah said:
The readme thread for One M9 phones states that I'm probably going to need S-OFF for the conversion in order to be able to change the CID. However, as the software and firmware versions of my device do not match those of any other demo unit I found on the net, I'd like to kindly ask someone with deeper knowledge to verify that I'm on the right track in the first place.
Click to expand...
Click to collapse
The demo units use the same hard-/firm-/software as the unbranded European M9. It actually is an unbranded European M9 that simply uses a specific CID (c.f. the first paragraph of my reply).
Rastullah said:
- I do need S-OFF to convert, right?
- Is this a GSM unit (as I believe it is, judging from the seller's location in Germany)?
- Can I convert directly to LineageOS or do I have to flash RUU/stock first?
- Is it possible/necessary/recommended to upgrade the firmware from 1.x to something more recent?
- Aside from that, is it generally safe to follow the conversion procedure described in post #5 of the Readme thread with this phone?
Click to expand...
Click to collapse
Correct, yes it is (c.f. above), no you can't due to your firmware, yes it definetly is if you want to boot any of the currently available custom roms and yes it is.
Rastullah said:
Is it normal that booting to recovery is refused with an error message? ("Failed to boot to recovery mode. Press volume up or down to back to menu. This build is for development purposes only [...]" in red on a white HTC logo.)
Click to expand...
Click to collapse
Rastullah said:
Is it normal for such a unit that flashing or booting into TWRP 3.1.1.0-hima does not work using adb and fastboot (tried both the standard version of the tools, but also the HTC version)?
Click to expand...
Click to collapse
Yes it is if you try to flash a version that isn't compatible with your current firmware (c.f. either the official TWRP thread or the FAQ of the ReadMe thread). Fastboot booting a custom recovery was disabled on this phone on firmware 1.x and 2.x, btw. I've added another warning to the unlocking/rooting guide, now.
Rastullah said:
Could not flash RUU (RUU_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.30.617.12, from HTC website for unlocked/developer version of M9), this fails with error 127, signature error. What causes this, CID/SKU mismatch?
Click to expand...
Click to collapse
You don't own a dev edition M9. That's a different hardware model. (The differences aren't too big, though.) If you want to flash that RUU you need to convert your phone and to update the firmware to 4.x*, first, since versions 1.x to 3.x use different encryption keys than 4.x. Therefore, you can't use 4.x RUU on phones with older firmware versions.
* e.g. by flashing a 3.x RUU for your SKU and installing the 4.x OTA or by flashing a custom made 4.x firmware pack from Sneakyghost's firmware thread.

Polaroid MIDK148PJE custom recovery or root

Hello guys.
I'm trying to fix "Device is not certified by Google" error when trying to open playstore on my sisters tablet. It's Polaroid MIDK148PJE02.112 device which is based on Mediatek MT8163V SoC (Windows recognizes it as POLAROID RAINBOW). My plan is to flash custom recovery or obtain root by any other means available so that I can install gapps which will hopefully resolve problem with Play Store.
So far I have tried couple of Windows based root tools (KingRoot, KingoRoot, some chineese tool) and none of those where successful.
I have also tried to use adb and fastboot do unlock bootloader but when I reboot to fastboot mode and run "fastboot oem unlock" it asks me to confirm this by pressing the volume up button but this tablet doesn't have hardware volume buttons.
Then i found some tutorials which mention MTK Droid tools, scatter file and SP Flash tool. When I run Droid tools and click on "Boot map" button it shows only one entry and it start address and everything elese is 0000000. I have attached device info from Droid tools.
Also i have de-soldered battery to be able to start device in that mode for SP Flash tool and device was successfully recognized (drivers installed) but I couldn't do anything without scatter file.
Can anyone give me a hand with this device? I don't have much experience with android phones and tablets but I'm not total noob either.
Code:
Hardware : MT8163
Model : MIDK148PJE
Build number : JE10_EM-T8512-V6.0M_MT8163_OSA60_V1.2
Build date UTC : 20160824-135302
Android v : 6.0
Baseband v: -----
Kernel v : 3.18.22 ([email protected]#8) (gcc version 4.9.x-google 20140827 (prerelease) (GCC) ) #1 SMP Thu Aug 25 11:06:48 CST 2016
--->>> Connect to device <<<---
--- ERROR : --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!
--- Unknown ROM structure, backup NOT possible!
ATTENTION! File /system/recovery-from-boot.p which restore factory recovery in case of phone switching on in a normal mode Is Found!