Related
Hi all!
When I try to read an extended ROM image with the softworkz ER2003Edit tool, I get an error-box saying "Error accessing image files", no matter which ROM I try to load (have tried several operators/countries). What am I doing wrong?
Thx.
/Joe72
I've got the same problem.
anyone any idea pls????
thnx
i had the same problem, i kept on messing with the application and eventually was through.
Reason :
when you open er2003edit and click on file and then open rom image a window pops up, over most of us tend to go directly to the file which we want to open, BUT in actual you are suppose to change the FILES OF TYPE in that window at the bottom and select "WM2003 EXTENDED ROM (ms_.nbf)" and then open the file.
this will solve the issue FOR SURE
regards
jeetz
zairyaab said:
i had the same problem, i kept on messing with the application and eventually was through.
Reason :
when you open er2003edit and click on file and then open rom image a window pops up, over most of us tend to go directly to the file which we want to open, BUT in actual you are suppose to change the FILES OF TYPE in that window at the bottom and select "WM2003 EXTENDED ROM (ms_.nbf)" and then open the file.
this will solve the issue FOR SURE
regards
jeetz
Click to expand...
Click to collapse
it's working.
thnx 4 the tip
cheers :lol:
any time ...by the way if anyone of you guys want downloads links or ne thing on this forum or for any softwares follow http://forum.xda-developers.com/viewtopic.php?p=81950#81950
cheers
jeetz
Warning:I am not responisible for any damage to your phone and rooting usually nullifies the warranty. so please procede with your own risk
I tried to root my karbonn A2 for 2 weeks and finally i got it. so im gonna share the steps involved in rooting and also provoide the tools for it.
NOTE: I do not take credit for any tool since all the tools were already available online, so credit goes to whoever programmed them. only thing i did was to alter the method slightly to get my phone rooted.
Lets begin. Before we start rooting our phone, most important thing is the drivers. so u need two types of drivers one is ADB (android debugging bridge) drivers and the other is preloader drivers. i have attached both of these drivers in the attachments u can download it.
Step1[only for beginners]: Go to setting>applications>development>enable USB debugging in the phone, then connect your phone to ur pc (remove all previous drivers if u have installed) then go to device manager>devices, right click on the usb device and click update driver and browse to folder containing the SPdrvers (u need to extract the folder from the attachment first).If driver is successfully installed then u should see "android phone" in ur device manager. to confirm it just run adb devices from the command line by chagning the directory to where adb.exe is, u should see the list of devices attached to ur pc. (usually adb.exe will be in android sdk tools folder or if u dont have one then check in ADB folder from superoneclick in the attachment).
Step2: ok, now that u have installed adb drivers, u need to install preloader driver (also known as downloading mode in some devices). to do this, disconnect ur phone from the pc, then switch off the phone, remove the battery and then connect ur phone to pc again (without the battery). then u should see windows trying to install drivers and fails. then go to device manager again and browse to folder containing USB VCOM drivers (see attachment). after it successfully installs procede to step 3.
Step3:: download, extract the files MTKROM and SPflash tool to ur pc. then put the battery inside ur phone then switch it on, connect it to pc (enable debugging all the time). then open command line then go to adb folder then type :adb devices- u should see the list of device attached (u will get some long numbers so dont worry). then type "adb shell" (without the quotes). u will get a $ sign, then type "cat proc/mtd > /sdcard/firmware.info" if its successful then a file named firmware.info will be created in ur sdcard root. then copy that file to ur pc.
Step 4: Now open that firmware.info in MTKROM.exe u should see a list tables and address like in the image below. then click save scatter and rename the filename to MT6575 instead of MT6573 (and leave everthing else as it is). so a file named "MT6575_Android_scatter.txt" will be created.
Step 5: Now open Spflash tool and load the scatter file in that. u should see something like this in the image below.
STEPS TO BACKUP ORIGINAL BOOT AND RECOVERY
Step 6: Before we actually begin to root its important to make a backup of current images. so to do that, go to READ BACK tab in sp flash tool. click on Add>double click on the page file and save as "Boot.img" somewhere safe. then click on "Read Page only", this is very important. then look at the address side by side from MTKROM and enter into sptool. the start address is the address in which the boot.img begins and length is the length of boot.img. so final address will be startaddress+length =start address of next image (recovery.img). In MTKROM the start address is given as "PART ADDRESS". after entering those carefully click ok. if u want to be sure then use programmer calculator and add the address.
Note :the address will be in hexadecimal format not decimal.
Step7: In order to read the firmware from the phone, disconnect the phone from your pc, remove the battery, dont connect it yet. now click on "Read back" button in the sptool (its after Add,remove button). now the software starts searching for the device. now connect the device to the pc (without battery ofcourse). now if have installed USB VCOM drivers correctly then the sp tool should detect ur device and start reading from it. u will see Red colour in the
task bar when it detects then blue colour while the tool is reading the phone. wait untill the reading is complete. A green circle will pop up after it successfully reads from the device. (refer the images below)
Step 8: repeat step seven as described above for recovery.img (save the file as recovery.img) then select "read page only" option, enter start address as 0x0980000 and length as 0x0500000. (please enter the address carefully cross check with MTKROM image addresses.)
Note: You have to disconnect the device first then click read back button after entering the addresses then connect the device, otherwise the sptool wont detect your device!.
Actual Rooting Procedure
Step 9: Now that you have backed up both boot and recovery images its time to start the actual rooting. download the boot.img file from the attachment and save to your pc (dont replace it with your backup image that you saved earlier). go to download tab in the sp tool and tick only boot.img and uncheck all others (if any of them has been checked already) and click on Bootimg and browse for the folder where u downloaded boot.img from the attachment and NOT THE BACKUP! after that disconnect your device, then click download button above( after format->upgrade button) or f9 from keyboard. the tool will start searching the usb com ports. now connect your device and wait till it downloads fully. Note: In downloading your will get RED colour first, then YELLOW colour while flashing, and finally a GREEN circle after flashing is complete).
Step 10: The most important and complicates steps are over. now all you have to do is put your battery to your phone and switch it on. now after it sucessfully boots up, open superonclick.exe (you will get this software online and its very popular tool for rooting) and connect the device to your pc (enable debugging of course), then click Root button in superoneclick and Voila! your phone is rooted. enjoy and dont forget to press thanks button if ive helped
Note: u will need .NET framework 3.5 to run superoneclick.
Method To Unroot
For unrooting your mobile all you have to do is flash the original, backup boot image back to your phone. just open sptool and load the scatter file, then click on bootimg then browse to wherever u have stored backup boot.img then click download button then connect your device without the battery and thats it. you will get back original firmware without the root!.
Clockwork mod recovery for A2
There is no official cwm recovery for A2, but i ported cwm for other MT65xx devices to A2. so here are the steps to flash.
step 1: download recovery.img from the attachment.
step 2: open sp flash tool and load scatter.txt (for detailed description refer rooting steps). then tick recoveryimg and browse and set the path of the recovery.img you just downloaded from attachment.
step3: click on download button at the top or press f9. then take out the battery from the phone and connect it to the pc. the tool will detect your phone and start flashing cwm recovery.wait untill the green circle pops up.
step 4: now put in the battery and press power button+volume up and hold it for few seconds and voila!! cwm recovery boots up. And to revert back to original recovery just flash the recovery.img that you backed up during rooting process using the above steps.
Note: Do Not factory reset your phone without backing up the IMEI number. After rooting your device please backup your phones IMEI number which is stored in data/nvram/md/NVRAM/NVD_IMEI/MP0B_001 to a safe place. or there is an application called mobileuncletools (a chinese app) which helps to backup your IMEI to sdcard and restore it back. if u loose your IMEI and reset your phone then you cannot call or recieve sms etc
No service and invalid IMEI solution
explanation:
In case u did factory reset of the phone, then all your data will be wiped including the imei number. it will be reverted to factory imei number, hence you cannot connect to any mobile networks in india or anywhere else because most network operators wont allow to use the network with dupicate or invalid imei numbers. every device has a specific imei number. in this device your original imei numbers (15 digits) will be on the back of your battery.
Restoring is tough very simple procedure, creating the required files is a major headache. At first i thought it was impossible to restore the imei back (trust me i tried all the available solutions that u get in the internet, infact there are 5 different types of solutions, none of which worked for this device). luckily one day i found a chinese software which actually did create a imei file that is compatible with this device (phew !, yeah i know) and so i did successully restored my imei back and i can once again connect to mobile network and make calls..:victory: so here it goes.
How to restore IMEI number? (MUST BE A ROOTED PHONE)
1) if u have made the backup of MP0B_001 file in /data/nvram/md/NVRAM/NVD_IMEI/MP0B_001 , then install root explorer and simply replace your current file with the backed up MP0B_001 and set the permissions to rw-rw---- and restart.
2) if u havent backed it up (too bad), then download the chinese software sn_gen.zip from the attachments and enter both imei numbers that is found in the back of your battery (enter the numbers correctly and cross check it again, its 15 digit number). then the software generates a new MP0B_001 file, copy and paste in the above mentioned directory and set the permissions to rw-rw---- and restart.:fingers-crossed:
dont forget to press thanks button if ive helped you :good:
Download Links:
Drivers: http://www.4shared.com/rar/XLiLMsG3/sp_drivers_v14.html?
SP flsah tool: http://www.4shared.com/archive/bjTXvBtd/sp_flash_tool_v3122401.html?
scatter txt: http://www.4shared.com/office/W7Fk6VOm/MT6575_Android_scatter.html?
I need to root my A2 too,can you tell me how?
thanks but I want to put ICS in my device karbonn a2 can u help more
thanx in advance
Sent from my Karbonn A2 using xda app-developers app
vickykeeth said:
thanks but I want to put ICS in my device karbonn a2 can u help more
thanx in advance
Click to expand...
Click to collapse
its not possible to put ICS in A2 (since its officially not supported to our device), although cyanogenmod 9 can be installed but its very difficult to build it since most of the drivers are properitery and they wont release the sources. so its almost impossible to run cm9 and even if someone did build cm9 it wont run smoothly because of very low amount ram in our device (<256MB and ICS needs more than that to work smoothly). however im working to build cm7 (based on gingerbread) for our device and even that is really difficult since there is no device tree in github for this device. so i need build cm7 from scratch and that is not an easy job. so if any developers are working on building cm7 for A2 please pm me so that we can work together..
cm10
abhiatreyas said:
its not possible to put ICS in A2 (since its officially not supported to our device), although cyanogenmod 9 can be installed but its very difficult to build it since most of the drivers are properitery and they wont release the sources. so its almost impossible to run cm9 and even if someone did build cm9 it wont run smoothly because of very low amount ram in our device (<256MB and ICS needs more than that to work smoothly). however im working to build cm7 (based on gingerbread) for our device and even that is really difficult since there is no device tree in github for this device. so i need build cm7 from scratch and that is not an easy job. so if any developers are working on building cm7 for A2 please pm me so that we can work together..
Click to expand...
Click to collapse
if we create any partion sd memory for our internal memory can it run cm10 b'cuz galaxy ace can run cm10 it has just 256MB ram and some wat 800MHZ speed only but our device has 256MD ram with 1GHZ processor speed so i think it can also run cm10 if we create a partition memory from ous sd card thats wat i think so........
waiting for reply from ur side thanks in advance.......
urgent help
i tried to reset my karbonn a2 and done it after reboot it shows no service and also no network wat to do pls tell me thanx in advance..........
vickykeeth said:
if we create any partion sd memory for our internal memory can it run cm10 b'cuz galaxy ace can run cm10 it has just 256MB ram and some wat 800MHZ speed only but our device has 256MD ram with 1GHZ processor speed so i think it can also run cm10 if we create a partition memory from ous sd card thats wat i think so........
waiting for reply from ur side thanks in advance.......
Click to expand...
Click to collapse
lol i was a galaxy ace user untill last dec. (its touch digitizer got broke, so i temporarily bought karbonn). anyway i do know ace can run cm10 and pretty much any device can, even ours can run it. i did not say our device doesnt run at all. i said it wont run smoothly and developing cm other than stock os version is very very difficult since our device is a local device and threre is no lot of support for it. so if anything goes wrong we may permanently brick our devices and may not find solution at all.
on the other hand, since i was a former ace user, i know that even though ace can run cm9 and cm10 there were a lot of problem in getting camera, video recording, and other applications because of unavialablity of their sources. so furthermore most of extra features that arent available in gingerbread cannot be used ex: face recognition, google now,otg usb etc( they are built for high end devices). u wont notice the difference in optimizations and performance of jelly bean in low end devices because they need sufficient hardware to utilize the os to full extent. so only thing u get out of installing cm is user interface (which u can change using of launchers, oh yes there are big bunches of launchers out there) and some features of cm (deodexd rom,custom kernel with overclocking features and some tweaks.)
coming back to our device, ive been trying to build cm7 for our device and its really difficult without a device tree and some good prior experience in building cm for atleast 2 devices. so my advice is that first we will build a fully working cm7 for our device and later if possible we will port cm10.
vickykeeth said:
i tried to reset my karbonn a2 and done it after reboot it shows no service and also no network wat to do pls tell me thanx in advance..........
Click to expand...
Click to collapse
what do u mean by reset? did u do factory reset from recovery or did u clear flash from by holding power+down? (oh btw recovery is power+up in our device).
either way ur imei number has been erased and it will be reset to factory number . i spent 1 week day and night searching for a solution and that is exactly why i told u to backup your MB0P_001 file.
in order to repair it u need to root ur phone. follow above steps and paste ur imei number (dial *#06#).
Nothing in SuperOneClick
I am successful in doing everything, but when I open SuperOneClick, it does not show any device, and clicking "Root" greys off the button for a few seconds, and everything is back to normal again. Nothing happens to the phone.
What is wrong?
shyamsn00 said:
I am successful in doing everything, but when I open SuperOneClick, it does not show any device, and clicking "Root" greys off the button for a few seconds, and everything is back to normal again. Nothing happens to the phone.
What is wrong?
Click to expand...
Click to collapse
ru sure u replaced boot.img which was attached in attachments to your phone? if it was successful then u have unlocked the bootloader. the problem here seems to be like superonclick isnt detecting ur phone when connected to pc. In case if the usb debugging is turned off enable it and check if ur device is listed in adb devices command as explained above. if it does and still rooting doesnt work, then maybe you are using wrong version of superoneclick. because some of the loopholes which is used to root your phone (by gaining temporary access to shell) is not available in older versions. the version must be compatible with gingerbread. try downloading superonclick 2.3.3 version.
also, after u root with superonclick, restart it and please check if u have superuser app in ur phone(it will be automatically installed by superoneclick, dont install it manually since the app should be in /system/app and su command should be in /system/bin directory, which u cannot do by installing it manually). if its installed then u have root access, if u still want to confirm just download root checker app from google play and run it.
CM10 means Jelly Bean Which has minimum Requirement of 512MB ram... device cant even Support Cm9(ics)...And generally cynogenmods are not developed for local Indian Brands.....Instead Try this making your phone look like XPERIA:
http://forum.xda-developers.com/show....php?t=2095956
abhiatreyas said:
ru sure u replaced boot.img which was attached in attachments to your phone? if it was successful then u have unlocked the bootloader. the problem here seems to be like superonclick isnt detecting ur phone when connected to pc. In case if the usb debugging is turned off enable it and check if ur device is listed in adb devices command as explained above. if it does and still rooting doesnt work, then maybe you are using wrong version of superoneclick. because some of the loopholes which is used to root your phone (by gaining temporary access to shell) is not available in older versions. the version must be compatible with gingerbread. try downloading superonclick 2.3.3 version.
Click to expand...
Click to collapse
I have indeed replaced the boot.img file and am using the latest version of S1C [ 2.3.3, I guess ]. Can the problem be because of Win8? Should I try doing this in W7?
hi there thanks for sharing that
But i can't find the way to do anythings that u said .....
i cant updated my phone driver, when i do it says up to date ....
can u please help me
thanks
Mr1010ass said:
hi there thanks for sharing that
But i can't find the way to do anythings that u said .....
i cant updated my phone driver, when i do it says up to date ....
can u please help me
thanks
Click to expand...
Click to collapse
im sorry, im not able to understand your problem. please give more information about your issue.
shyamsn00 said:
I have indeed replaced the boot.img file and am using the latest version of S1C [ 2.3.3, I guess ]. Can the problem be because of Win8? Should I try doing this in W7?
Click to expand...
Click to collapse
ok try it once in win7 and check if the issue is resolved, if not please explain clearly what is the problem and what error message you are getting.
need ua help
hey with your help i rooted my phone successfully.. Thanxx alot,,
Bt please invent custom for karbonn A2.. please
Waiting for your reply..
First 3 steps problem
I already downloaded everything and it seems like even before I started I already encountered a problem. When I try step 2 my KArbonn A2 device cannot be found on the list of devices on the cmd.... No "Android Phone" is found on my device manager but only "Karbonn - A2MS USB Device". When I update the driver it says that it is already the best driver for my device.... I need help pls.....:crying:
BOOTLOOP????????
I cannot boot up after flashing the boot.img,you provides...I've been able to flash cwm recovery successfully and make backups of my recoveries and boot.img...But when I flash the provided boot.img,My phone goess inot a bootloop It shows Karbonn A2 splash and shuts down and restarts,doing the same thing over and over again...Please tell me whether it is a problem with the boot.img or have I done something wrong in the flashing procedure???
Thank you..... finally found out where I went wrong... now my phone is rooted..... A hundred thanks....:victory:
I was running a version of RR, earlier, camera did however not work so I thought that I should switch, the problem is that android determined to change my screen lock to something that I don't know of, I can use adb still to get around but there I get another error that says: "This package is for "OnePlus3"; this is a "oneplus3"
well for the error "this package is for..." you open your rom.zip file and go to META-INF--> com--> google-->android and open updater-script with a text editor and in the first line " then getprop..." change it from OnePlus3 to oneplus3
timrock7 said:
well for the error "this package is for..." you open your rom.zip file and go to META-INF--> com--> google-->android and open updater-script with a text editor and in the first line " then getprop..." change it from OnePlus3 to oneplus3
Click to expand...
Click to collapse
Thank you i tried and somehow got out of the annoying loop that occured, many thanks!
Guys i tried to install MIUI 7 on my amazon firephone i downloaded all the files and did a reboot in recover all going good then when i tried to install miui files it got stuck in the recovery mood and i restarted the phone and now it is stucked on amazon logo nothing doing else even i tried wipe data twice from hard reset mood please help did it brick my phone? help me to solve this.
hamza said:
Guys i tried to install MIUI 7 on my amazon firephone i downloaded all the files and did a reboot in recover all going good then when i tried to install miui files it got stuck in the recovery mood and i restarted the phone and now it is stucked on amazon logo nothing doing else even i tried wipe data twice from hard reset mood please help did it brick my phone? help me to solve this.
Click to expand...
Click to collapse
if you can acces to recovery, the only thing you can do is adb sideload ...bin
with an original stock ROM for your fire phone
(.bin must be the extension of the file, that you can get from official amazon site)
pipataki said:
if you can acces to recovery, the only thing you can do is adb sideload ...bin
with an original stock ROM for your fire phone
(.bin must be the extension of the file, that you can get from official amazon site)
Click to expand...
Click to collapse
Thanks a lot for your help after starting this thread i did a lot of research about it and i got the same solution from Xda and i tried it is same manner as some nice people posted it on this site but now another issue is being created automatically which is adb sideload command is not working when i write the following command
adb sideload "filename.bin"
its shows me an error "*cannot read filename.bin"
i tried it by changing the file name as "update.bin" and also tried it same file name which i downloaded from the amazon site. Please help me to resolve issue. Thanks again.
hamza said:
Thanks a lot for your help after starting this thread i did a lot of research about it and i got the same solution from Xda and i tried it is same manner as some nice people posted it on this site but now another issue is being created automatically which is adb sideload command is not working when i write the following command
adb sideload "filename.bin"
its shows me an error "*cannot read filename.bin"
i tried it by changing the file name as "update.bin" and also tried it same file name which i downloaded from the amazon site. Please help me to resolve issue. Thanks again.
Click to expand...
Click to collapse
filename is the name of file... <file.bin> you have to download that file from amazon or see in index thread
pipataki said:
filename is the name of file... <file.bin> you have to download that file from amazon or see in index thread
Click to expand...
Click to collapse
yeah i downloaded the file from amazon site and its original name was "update-kindle-35.4.6.6_user_466001420.bin" but i changed it to "update.bin" and it didn't work.
hamza said:
yeah i downloaded the file from amazon site and its original name was "update-kindle-35.4.6.6_user_466001420.bin" but i changed it to "update.bin" and it didn't work.
Click to expand...
Click to collapse
its still not working still showing that error "cannot read file.bin"
hamza said:
its still not working still showing that error "cannot read file.bin"
Click to expand...
Click to collapse
If you have the device via adb (with adb devices command) you can do an adb sideload sure... so in your case I supose, the file is corrupted... better dont rename it... but, if you can connect via adb, you can sideload sure...
pipataki said:
If you have the device via adb (with adb devices command) you can do an adb sideload sure... so in your case I supose, the file is corrupted... better dont rename it... but, if you can connect via adb, you can sideload sure...
Click to expand...
Click to collapse
no file was not corrupted because i downloaded another file from another site and it is showing same error i really cant understand what is happening. Is there any administration need?
hamza said:
no file was not corrupted because i downloaded another file from another site and it is showing same error i really cant understand what is happening. Is there any administration need?
Click to expand...
Click to collapse
did you do adb devices first?... first you have to know if adb can connet with the device... that will be listed with that command... adb devices
if you want send an screenshot with the result of making adb devices
Try to sideload what version of fire os you had before MIUI upgrade. If you had fireos 4.6.6, sideload 4.6.6, if you had 3.6.5 sideload 3.6.5
ozan2 said:
Try to sideload what version of fire os you had before MIUI upgrade. If you had fireos 4.6.6, sideload 4.6.6, if you had 3.6.5 sideload 3.6.5
Click to expand...
Click to collapse
i was having 4.6.6 and i sideloaded this version i am shocked that all things i am doing are totally good but why this error is occuring
hamza said:
i was having 4.6.6 and i sideloaded this version i am shocked that all things i am doing are totally good but why this error is occuring
Click to expand...
Click to collapse
I think that here in my computer I have the original update of Stock Rom, If you want I can upload it to my shared folder...
(left 3 hours and 5 minutes, maybe)...
to be sure that the upload and the download then is rigth, I tell you the exactly weight of file...
1314263238 bytes, you can test if the file you had has the same weight...
pipataki said:
I think that here in my computer I have the original update of Stock Rom, If you want I can upload it to my shared folder...
(left 3 hours and 5 minutes, maybe)...
to be sure that the upload and the download then is rigth, I tell you the exactly weight of file...
1314263238 bytes, you can test if the file you had has the same weight...
Click to expand...
Click to collapse
Size of my file is 1.2 GBs which is approximately equal to your file as you told me. I actually download it from amazon original site not any third party site but yeah upload it and please give me the link i will surely be thankful to you. I really appreciate your help and really happy to be new here at Xda developer.
hamza said:
Size of my file is 1.2 GBs which is approximately equal to your file as you told me. I actually download it from amazon original site not any third party site but yeah upload it and please give me the link i will surely be thankful to you. I really appreciate your help and really happy to be new here at Xda developer.
Click to expand...
Click to collapse
is uploaded totally...
the url of shared folder is in my Lollipop thread...
Are you accesing sideload by recovery?...
sideload only works invoked in recovey of the phone, in safestrap or in stock recovery
pipataki said:
is uploaded totally...
the url of shared folder is in my Lollipop thread...
Are you accesing sideload by recovery?...
sideload only works invoked in recovey of the phone, in safestrap or in stock recovery
Click to expand...
Click to collapse
Yes I am accessing it through phone recovery because i cant turn my phone on thats why i cant use safestap thats why i put my phone on recovery mood and selects install from adb option then from laptop i open console by pressing nd holding shift and right click and selecting open command prompt where my original amazon rom is placed then i use to write the sideload command which is adb sideload <filename.bin> and the then it shows error *cannot read <filename.bin>
That is all the procedure what i do everytime and it get failed please let me know if i am doing any thing wrong in it. Thank you
hamza said:
Yes I am accessing it through phone recovery because i cant turn my phone on thats why i cant use safestap thats why i put my phone on recovery mood and selects install from adb option then from laptop i open console by pressing nd holding shift and right click and selecting open command prompt where my original amazon rom is placed then i use to write the sideload command which is adb sideload <filename.bin> and the then it shows error *cannot read <filename.bin>
That is all the procedure what i do everytime and it get failed please let me know if i am doing any thing wrong in it. Thank you
Click to expand...
Click to collapse
Try using another wire and/or another port and/or another file... (the original stock that I had is in my shared folder, that one for exemple or any other one)... I hope you could relive it...
pipataki said:
Try using another wire and/or another port and/or another file... (the original stock that I had is in my shared folder, that one for exemple or any other one)... I hope you could relive it...
Click to expand...
Click to collapse
Thank You so much for your such response got it okay the problem was i didn't unblock the update file which dont know earlier but as you reffer me another link i worked on it and i got my phone back. Once again thank you so much it was really nice to be here. I will suggest all my friends your site.
hamza said:
Thank You so much for your such response got it okay the problem was i didn't unblock the update file which dont know earlier but as you reffer me another link i worked on it and i got my phone back. Once again thank you so much it was really nice to be here. I will suggest all my friends your site.
Click to expand...
Click to collapse
you can go to mobile shop and it will cost only 200 to 300 rupee for software, i also had this issue (soft brick) then i tried alot but finally i go to mobile shop and install the software ..
hamza said:
Yes I am accessing it through phone recovery because i cant turn my phone on thats why i cant use safestap thats why i put my phone on recovery mood and selects install from adb option then from laptop i open console by pressing nd holding shift and right click and selecting open command prompt where my original amazon rom is placed then i use to write the sideload command which is adb sideload <filename.bin> and the then it shows error *cannot read <filename.bin>
That is all the procedure what i do everytime and it get failed please let me know if i am doing any thing wrong in it. Thank you
Click to expand...
Click to collapse
Hello,
This may be a stupid question but did you specify the proper path? ie: c:\'filename"
just a shot, good luck
slim1001 said:
Hello,
This may be a stupid question but did you specify the proper path? ie: c:\'filename"
just a shot, good luck
Click to expand...
Click to collapse
Yes man, his phone is recovered and I had this error, solution for "cannot read" is here: https://forum.xda-developers.com/fire-phone/help/adb-sideload-error-read-t3634246
For those who are still waiting for a fix for the update error and don't want to undergo the recovery process, I found a different solution, which doesn't need a recovery operation on the phone.
I tested it with success on my 1020 and another 925 which were stuck in the CU build .297.
Keep in mind that the parameters that I will use are specific to these phone models, so if you have a different one you need to find the parameters specific to your phone model.
This is an heuristic procedure, tested on a limited number of phones, so use it at your risk, keeping in mind that you could have problems or need to recover your phone loosing all your data, so do a proper backup before.
Let's start.
The problem appears because, during update phase, the oeminput.xml file becomes corrupted: as far as I know it happens only on some x20 models, and not for all the users.
Now we're going to rebuild it...
Go to the following link
https://msdn.microsoft.com/en-us/library/windows/hardware/dn756630(v=vs.85).aspx
Copy the content of example file oeminput.xml: i.e. copy the content of the framed zone after the phrase "The following example shows the contents of a sample ProductionOEMInput.xml file"
Paste in a .txt file which you'll rename and change extension so that it becomes oeminput.xml. Save it with notepad.
Now modify the file
at the node <SOC>{PROCESSOR_NAME}</SOC> modify {PROCESSOR_NAME} fake parameter in order to have the processor name of your phone: for the 920/925/1020 use QC8960
at the node <Resolution>480x800</Resolution> instead of 480x800 use the resolution of your phone: for the 920/925/1020 use 768x1280
in all the nodes related to language <Language>en-US</Language> use the language of your phone: I used for example it-IT because I have the phone in Italian language.
Save the file.
Now if you still don't have interop tools installed (but I think you should have if you arrived to CU with an x20 phone model) install it.
Launch interop tools and then click this device and enable full file system access. Reboot your phone, connect it to a pc with cable: you'll see more directories than usual, because you also unlocked system dirs: be careful not to delete or modify any dir apart from what you find in this guide or you'll risk to damage your phone. If you want to find your usual dirs (docs photos...etc), go to phone\Data\Users\Public. I advise you that after the procedure I couldn't deactivate full file system access, because it continues re-activating in interop tools, maybe there is a way: but you can live with this, because you can find the usual dirs in the path that I specified...
Now go to phone\windows\imageupdate, make a backup on pc of the current oeminput.xml and overwrite it with the new one.
At this point in the phone go to settings, update and then search for updates: you should find Fall Creators Update...
Good Luck!
p.s. I didn't extensively search on the forum if a similar guide has been already posted, in the case sorry for the duplication.
Thanks to Antonio who has actively participated in the realization of this guide
sigfrid696 said:
https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx
Click to expand...
Click to collapse
The link is wrong
Thank you!
I modified it, now it should be ok!
friend can you share the oeminput.xml file that you used?
NeoTriXz said:
friend can you share the oeminput.xml file that you used?
Click to expand...
Click to collapse
Done! Let me know if it works...change only language to match your phone language and do a proper backup of your original file...
sigfrid696 said:
Done! Let me know if it works...change only language to match your phone language and do a proper backup of your original file...
Click to expand...
Click to collapse
no friend did not work, I keep throwing the same error, some idea that can be or another solution?
NeoTriXz said:
no friend did not work, I keep throwing the same error, some idea that can be or another solution?
Click to expand...
Click to collapse
At this point I think it's not a problem of corrupted oeminput file.
I googled around...not so many people having the problem...I found this link...
https://answers.microsoft.com/de-de...nd-eimem/0a6e1776-9005-40e8-a18e-9eaf0f35b648
It's in german language, but from what I understood the problem has been solved with Recovery Tool via pc: I know that's not the best solution, but maybe better than remaining without updates. Another significative information is that an hard reset alone doesn't solve the issue!
I hope that can be of any help...
sigfrid696 said:
At this point I think it's not a problem of corrupted oeminput file.
I googled around...not so many people having the problem...I found this link...
https://answers.microsoft.com/de-de...nd-eimem/0a6e1776-9005-40e8-a18e-9eaf0f35b648
It's in german language, but from what I understood the problem has been solved with Recovery Tool via pc: I know that's not the best solution, but maybe better than remaining without updates. Another significative information is that an hard reset alone doesn't solve the issue!
I hope that can be of any help...
Click to expand...
Click to collapse
thank you friend, for your time, but I already solved it, well I had to perform a hard reset,
does this works for lumia 520
and what parameter should i used for my lumia 520 Rm 914
i'm stuck on 15063.251
and my lumia finds fall cu update
but shows Error 0x80070273
does this really resolve this error
i could not able to copy paste it it shows you don't have permission
how i get permission
---------- Post added at 06:42 AM ---------- Previous post was at 06:22 AM ----------
it gives me this error
Yash Agarwal windows said:
does this works for lumia 520
and what parameter should i used for my lumia 520 Rm 914
i'm stuck on 15063.251
and my lumia finds fall cu update
but shows Error 0x80070273
does this really resolve this error
Click to expand...
Click to collapse
I think you should use for 520
<SOC>QC8227</SOC>
<Resolution>480x800</Resolution>
If you receive an error when you try to overwrite oeminput.xml, it means that your phone has not been unlocked for full filesystem access. Please refer to the guide in order to enable full filesystem access
thanks
it worked for me
Getting this error code - 0x8018830f while updating to 14393.1884 (Lumia 730)
Can I try the fix from this post for this error?
Donz7733 said:
Getting this error code - 0x8018830f while updating to 14393.1884 (Lumia 730)
Can I try the fix from this post for this error?
Click to expand...
Click to collapse
this error is get due to incorrect processor no or incorrect screen resolution
Donz7733 said:
Getting this error code - 0x8018830f while updating to 14393.1884 (Lumia 730)
Can I try the fix from this post for this error?
Click to expand...
Click to collapse
You can examine your oeminput.xml file and check if it is somehow not well-formed.
If that is the case you can use
<SOC>QC8926</SOC>
<Resolution>720x1280</Resolution>
Thanks for the reply guys.
I couldn't wait longer, so went with an reset. It updated fine after that.
Later came to know it was some server issue
how do you replace the xml file? it says copying but refuses to actually replace the file.
rancorx2 said:
how do you replace the xml file? it says copying but refuses to actually replace the file.
Click to expand...
Click to collapse
you should need completely interop unlock your device using interop tools
then restart your phone
then after it copies without error
Yash Agarwal windows said:
you should need completely interop unlock your device using interop tools
then restart your phone
then after it copies without error
Click to expand...
Click to collapse
how is complete unlock ??????????
I use interop tools
bloody_earth said:
how is complete unlock ??????????
I use interop tools
Click to expand...
Click to collapse
The error overwriting oeminput.xml happens when you haven't obtained full filesystem access.
In order to obtain full filesystem access:
Open Interop Tools, then this device, then Interop Unlock.
Check Full Filesysytem Access and restart your device.
Refer to this thread to download correct version of Interop Tools
https://forum.xda-developers.com/windows-10-mobile/tutorial-restore-glance-windows-10-t3540571
Let me know if you can solve the problem this way.