Related
Yes, we're all noobs!!!
I have a brand new Excalibur (I bricked my first one five mins. out of the box) and I attempt to upgrade following instructions on the tutorial posted on these forums.
What's not stated on said tutorial (and no one tells you, only after you bricked your phone) is that YOU MUST BACK UP YOUR ORIGINAL ROM before the upgrade, because if anything goes wrong, that is the only ROM you can flash to your phone to restore it, otherwise IT IS BRICKED. (Believe me, it happened to me).
So, to all you experts reading these, please, help us noobs and post here a complete guide on how to back up your original ROM.
We will thank and worship you forever!!!
These days, there is no need to backup your own Rom.
We have a collection of ROMs on this site alone. Or in my signature.
I do suggest to download one prior to updating your ROM.
This forum uses most of a collection of ROM i have uploaded for everyone.
Click here for the forum of original ROMS
Mikey1022 said:
These days, there is no need to backup your own Rom.
We have a collection of ROMs on this site alone. Or in my signature.
I do suggest to download one prior to updating your ROM.
This forum uses most of a collection of ROM i have uploaded for everyone.
Click here for the forum of original ROMS
Click to expand...
Click to collapse
I have two questions: Firstly, there is no official O2 Xda Cosmo ROM or? Secondly, if you back up the ROM first, how can you flash it back to the device? Is there a tutorial for this?
Thanks
READ this thread
uccellino said:
I have two questions: Firstly, there is no official O2 Xda Cosmo ROM or? Secondly, if you back up the ROM first, how can you flash it back to the device? Is there a tutorial for this?
Thanks
Click to expand...
Click to collapse
yeah i'm waiting for the official O2 Xda cosmo ROM. i need it badly because my camera doesn't work anymore with new ROM. and i am totally agree to write a clear reminder to backup your original ROM first before upgrading in the upgrading ROM thread. just in case for noob like me....
Mikey1022 said:
READ this thread
Click to expand...
Click to collapse
After rereading, I still have the questions:
1. How is it possible to flash back a saved backup ROM image?
2. If I use a USPL and then something goes wrong while flashing a cooked ROM, can I only re-flash my original ROM (i.e. for XDA Cosmo which doesn't exist)?
Thanks
Okay - maybe I just figured out the answer to my own question: if I flash the USPL-RUU first before flashing a ROM update, maybe this means I can reflash if something goes wrong? Is this correct, or is there a chance that the SPL get overwritten before the error and I still get stuck?
Well, in fact, it is necessary...
Mikey1022 said:
These days, there is no need to backup your own Rom.
We have a collection of ROMs on this site alone. Or in my signature.
I do suggest to download one prior to updating your ROM.
This forum uses most of a collection of ROM i have uploaded for everyone.
Click here for the forum of original ROMS
Click to expand...
Click to collapse
...When I mean original ROM, I mean the ROM that could only work on a CID-Locked-by-a-carrier Excalibur, not the HTC WW ROM release.
Also, many of us noobs are international, I doubt that on the ROM database on this website we'll be able to find, say, the Movistar Mexico HTC Excalibur WM5 1.15.0000 ROM, which in my case, is the only one I would be able to flash in case anything goes wrong on the upgrade attempt. (I dedicated a week searching this ROM for the first Excalibur I bricked, no results)
Therefore - and I really hate to contradict -, for many of us, a ROM backup IS necessary and a tutorial from you experts on how to do it would be a great, great contribution to this community. (And also to the database, 'cause I'll definitively upload my ROM once I back it up)
velascoperroni said:
...When I mean original ROM, I mean the ROM that could only work on a CID-Locked-by-a-carrier Excalibur, not the HTC WW ROM release.
Also, many of us noobs are international, I doubt that on the ROM database on this website we'll be able to find, say, the Movistar Mexico HTC Excalibur WM5 1.15.0000 ROM, which in my case, is the only one I would be able to flash in case anything goes wrong on the upgrade attempt. (I dedicated a week searching this ROM for the first Excalibur I bricked, no results)
Therefore - and I really hate to contradict -, for many of us, a ROM backup IS necessary and a tutorial from you experts on how to do it would be a great, great contribution to this community. (And also to the database, 'cause I'll definitively upload my ROM once I back it up)
Click to expand...
Click to collapse
Actually, it's quite easy to CID unlock your phone to load whatever ROM you want. Much easier in fact, than dumping your current ROM and restoring it. I was able to flash my first ROM within about 30 minutes of reading on this forum, and had no problems at all.
velascoperroni said:
...When I mean original ROM, I mean the ROM that could only work on a CID-Locked-by-a-carrier Excalibur, not the HTC WW ROM release.
Also, many of us noobs are international, I doubt that on the ROM database on this website we'll be able to find, say, the Movistar Mexico HTC Excalibur WM5 1.15.0000 ROM, which in my case, is the only one I would be able to flash in case anything goes wrong on the upgrade attempt. (I dedicated a week searching this ROM for the first Excalibur I bricked, no results)
Therefore - and I really hate to contradict -, for many of us, a ROM backup IS necessary and a tutorial from you experts on how to do it would be a great, great contribution to this community. (And also to the database, 'cause I'll definitively upload my ROM once I back it up)
Click to expand...
Click to collapse
I completely agree with you
I just have no idea how to restore a backed-up ROM and I haven't read anything saying how to do it either. As you say, many of us a stuck with devices CID locked to some international ROM that is impossible to get.
So once again the question: Does anyone know how to re-flash a backed-up ROM?
I'm no expert but all I'm going to say is this. If you have a Rom from a different carrier that has not leaked to the public, then you are probably out of luck. You take the risk of hoping your phone will not have serious problems down the line of your contract or usage. You should pick up insurance on your phone depending on the stipulations your carrier has about lost or stolen or even broken phones. In that case you could return/replace your phone if need be after modifying it to your liking. I also would suggest that the entire reason we are here is that we don't want to be like the norm. We want what we paid for and don't want to be restricted. It's a risk. You must make that choice and succeed or fail that's not anyone's problem but your own. With all the Roms out there you should find one to your liking. If you brick your phone which seems so much more difficult than my razr modding days, than sell it for parts and lesson learned.
In the U.S. the Open Headset Alliance is our future so what we do to our phones in the future will be our choice.
Good Modding
Pfunk
C'mon guys...
Wy all the negativity?
I'm I conspiring against copyright laws if I want to have a backup of the ROM I paid for?
Is backing up a ROM frowned upon on this community? or is it so easy (from what I can gather it requires "dumping" and "restoring") that it is even insulting for me to ask you how to do it?
Yes, we are all here because we don't conform to the norm, but we are all HERE to help each other out. Why the closure? Why the elitism?
Like all of you, I want to take full advantage of the piece of technology I acquired without the restrictions installed on them by the phone corps. Yes, I would like to have the minimum risks while doing so, and yes, I would like to do it as cost effective as I can, just as anyone of you would.
It is a risk to upgrade a Cid.Locked phone with the bypass provided on this website, It happened to me and to many: USB cord unplugs and voila, bricked phone.
One alternative is to pay $40 bucks for a permanent Cid.Unlock, which will allow you to flash and flash and flash, even if you get stuck in the middle of one process.
The other, used by many here who wont pay, is to use the Cid bypass, while having a backup original rom "just in case".
What I only ask (for myself and my peer noobs) is to have this same other alternative as many, many of you.
Really, is it to hard to post the following?
1. Downoad these softwares;
2. Do this to "dump";
3. Do that to "restore";
4. To re-flash, do this.
C'mon, all for one and one for all right?
p.s. For my friend asking how to re-flash a backed up ROM, from what I've gathered, it goes something like this: your backed up ROM must be in a *.bn format (I still don't know how to even achieve this); then you must get a hold of any HTC RUU Software, extract it (Winrar) and replace the *.bn file inside the extracted folder with your *.bn file; with the HTC connected in bootloader mode, run the exe file in the extracted folder.
velascoperroni said:
...I doubt that on the ROM database on this website we'll be able to find, say, the Movistar Mexico HTC Excalibur WM5 1.15.0000 ROM, which in my case, is the only one I would be able to flash in case anything goes wrong on the upgrade attempt. (I dedicated a week searching this ROM for the first Excalibur I bricked, no results)
Therefore - and I really hate to contradict -, for many of us, a ROM backup IS necessary and a tutorial from you experts on how to do it would be a great, great contribution to this community. (And also to the database, 'cause I'll definitively upload my ROM once I back it up)
Click to expand...
Click to collapse
The Official ROMs collection is as full as I can make it. To have more images, we need everyone to upload ones that are missing to something like rapidshare, mediafire, or one of a few dozen other hosting sites, then tell up here on xda dev. Or upload it to several yourself. Spreading things on the net is much easier than ripping the ROM out anyway, and you benefit from the online backups, too.
So, yes, if you aren't going to back up your ROM, hope that someone else already has. Or, even better, be that first guy who does it, to make things easier for the rest of us. Besides, we might want to see what kinda goodies are tucked in the Movistar version
Indeed!
Profezza said:
...Or, even better, be that first guy who does it, to make things easier for the rest of us. Besides, we might want to see what kinda goodies are tucked in the Movistar version
Click to expand...
Click to collapse
Thanks for the support Profezza, indeed I intend to be the first, but in order to do that, I need to know how to do it.
I'll keep my hopes up for someone to post here the procedure for backing up my own ROM.
Also, the Movistar version is pretty lame, at least it would be a language addition to the database since it is originally in Spanish.
velascoperroni said:
Thanks for the support Profezza, indeed I intend to be the first, but in order to do that, I need to know how to do it.
I'll keep my hopes up for someone to post here the procedure for backing up my own ROM.
Click to expand...
Click to collapse
My post kinda ignored that point, as... I don't actually know how it is done.
velascoperroni said:
Also, the Movistar version is pretty lame, at least it would be a language addition to the database since it is originally in Spanish.
Click to expand...
Click to collapse
I think the version # system is controlled by HTC and fairly consistent across brandings, so it looks like it is a rather old one, but yeah, it could handy just for the Spanish. And ya never know, maybe a better graphic or two in some odd corner. I'll come back and bump this if it looks like it is fading away.
velascoperroni said:
p.s. For my friend asking how to re-flash a backed up ROM, from what I've gathered, it goes something like this: your backed up ROM must be in a *.bn format (I still don't know how to even achieve this); then you must get a hold of any HTC RUU Software, extract it (Winrar) and replace the *.bn file inside the extracted folder with your *.bn file; with the HTC connected in bootloader mode, run the exe file in the extracted folder.
Click to expand...
Click to collapse
Hi velascoperroni!
Thank you for your help - this is helping me to get closer to understanding
Basically I have my old ROM image as .img files (actually 5 of them) produced by bkondisk, together with a log file saying what goes where. So now all we need to figure out is how to turn these back into a .bn file and we'll be in business. For info on bkondisk, which lets you save your ROM (as .img files), see this wiki http://wiki.xda-developers.com/index.php?pagename=bkondisk
Could anyone point me to some resources on these two file formats? Then maybe we could come up with a conversion program when one doesnt exist
Getting closer!
Great, it seems we are getting closer to our goal!!!
But still surprises me that no one has posted a complete how to... perhaps the only few who know the deal haven't read this thread yet.
Now we know the following:
1. Bkondisk: software that allows to backup ROM in *.img format.
2. The original format of the ROM is *.bn
We don't know if the *.img file needs to be converted to *.bn or if they are compatible.
I also found out about an easier method to re-flash the ROM:
1. Format your SD Card in FAT32;
2. Copy your *.bn file to your SD Card;
3. Turn off phone, insert SD Card, Turn on phone in bootloader mode;
4. The phone should automatically recognize the ROM and start the flashing process.
Uccelino: Try placing the *.img file in the SD Card instead of the *.bn file. Maybe, just maybe the phone also recognizes *img files!
Getting closer!
Great, it seems we are getting closer to our goal!!!
But still surprises me that no one has posted a complete how to... perhaps the only few who know the deal haven't read this thread yet.
Now we know the following:
1. Bkondisk: software that allows to backup ROM in *.img format.
2. The original format of the ROM is *.bn
We don't know if the *.img file needs to be converted to *.bn or if they are compatible.
I also found out about an easier method to re-flash the ROM:
1. Format your SD Card in FAT32;
2. Copy your *.bin file to your SD Card;
3. Turn off phone, insert SD Card, Turn on phone in bootloader mode.
4. The phone should automatically recognize the ROM and start the flashing process.
Uccelino: Try placing the *.img file in the SD Card instead of the *.bin file. Maybe, just maybe the phone also recognizes *img files!
Also...
Sorry for the double post back there!!
Also check out this thread I started when I bricked my first Excalibur:
http://forum.xda-developers.com/showthread.php?t=378050
I never got a feasible response to wether sprite backup would work or not, and I did not want to spend $30 bucks to find out.
velascoperroni said:
Great, it seems we are getting closer to our goal!!!
But still surprises me that no one has posted a complete how to... perhaps the only few who know the deal haven't read this thread yet.
Now we know the following:
1. Bkondisk: software that allows to backup ROM in *.img format.
2. The original format of the ROM is *.bn
We don't know if the *.img file needs to be converted to *.bn or if they are compatible.
I also found out about an easier method to re-flash the ROM:
1. Format your SD Card in FAT32;
2. Copy your *.bin file to your SD Card;
3. Turn off phone, insert SD Card, Turn on phone in bootloader mode.
4. The phone should automatically recognize the ROM and start the flashing process.
Uccelino: Try placing the *.img file in the SD Card instead of the *.bin file. Maybe, just maybe the phone also recognizes *img files!
Click to expand...
Click to collapse
I just had an idea: I will flash a ROM, back it up, and compare the *.bn files to the *.img files I get from backing up - maybe they are or are almost the same, and we can convert them
I will try. Thanks
I got the following response:
The application cannot be tested for compliance for Windows Phone 7 Application Certification Requirements because it fails to launch on all Windows Phone 7 devices. The application terminates at launch.
However, I tested it on my own device and emulator, it works fine on all of them.
Here is a little background.
My app requires internet to run, if there is no internet for the phone, it will pop a message to let users know that it needs the internet and exit.
Currently, I am supporting both Nodo and Mango. Mango version has been approved already. The nodo version shares most the code of mango with 7.1 related features removed. The mango version has the title of "XXX for mango", and the nodo version has the title of "XXX for nodo". I don't know if this can be the cause of the problem. Can someone please give me some insights on this?
I am fairly certain that you shouldnt be exiting the application like that. Bring them to a screen/page that lets them retry or make the popup let them retry.
I am not sure if that was the problem tho. because my app has been like this since day 1, and mango version was recently certified too.
Well you can try to resubmit and it might pass...contact create.msdn.com support to get more info.
I did, it failed again. The only reason I can think of is that if its not an clean install, meaning update from an existing older version of the app, there might be some issues, since I changed the structure of the storages. but i don't know how to test it.
Maybe request Microsoft to provide some debug information to you?
If you install your previous version (hope you kept your versioning archived somewhere) by deploying to emulator/phone, then deploy the new version, it may act as an upgrade, and you should be able to see what is happening with debugger attached. I haven't released an upgrade to any of my apps, so I'm not too sure on this feature.
If you did change isolated storage (definitions, etc), that may be your problem (serialization/deserialization).
Try the Windows Phone Power Tools from Codeplex, it has options to 'Upgrade': http://wptools.codeplex.com/ and provides a GUI for browsing storage.
There is also an Isolated Storage Explorer as part of the SDK [http://msdn.microsoft.com/en-us/library/hh286408(v=VS.92).aspx] that should allow you to see everything that may have changed between versions.
Please give me a thanks if this was helpful, it will be my first .
I think you really did provide the kind of help I need, but I don't know how to give you a thanks. Thanks!!! ( Not sure if this is what you meant tho)
My problem is that my app needs this type of changes, and I am willing to take the risk of asking users to reinstall it instead of just updating. Should I be able to do it?
blkjack2u said:
Maybe request Microsoft to provide some debug information to you?
If you install your previous version (hope you kept your versioning archived somewhere) by deploying to emulator/phone, then deploy the new version, it may act as an upgrade, and you should be able to see what is happening with debugger attached. I haven't released an upgrade to any of my apps, so I'm not too sure on this feature.
If you did change isolated storage (definitions, etc), that may be your problem (serialization/deserialization).
Try the Windows Phone Power Tools from Codeplex, it has options to 'Upgrade': http://wptools.codeplex.com/ and provides a GUI for browsing storage.
There is also an Isolated Storage Explorer as part of the SDK [http://msdn.microsoft.com/en-us/library/hh286408(v=VS.92).aspx] that should allow you to see everything that may have changed between versions.
Please give me a thanks if this was helpful, it will be my first .
Click to expand...
Click to collapse
I am seeking beta testers to help me locate the problem. If you are interested please reply/PM me with your live id. I will send you an update once the beta test is live. Your help is much appreciated.
sunxin8086 said:
I think you really did provide the kind of help I need, but I don't know how to give you a thanks. Thanks!!! ( Not sure if this is what you meant tho)
My problem is that my app needs this type of changes, and I am willing to take the risk of asking users to reinstall it instead of just updating. Should I be able to do it?
Click to expand...
Click to collapse
I was thinking the 'Thanks' button that is attached to a post; kind of like receiving a badge for helping others.
As a user I'd probably be unhappy if I was asked to have to reinstall, but I guess if the update contains some good stuff and I wouldn't lose data, it isn't too difficult to uninstall/install again and is only a minor inconvenience.
Is there anyway you can code in to convert from previous storage structure to the new one since a standard WP app upgrade preserves the previous version?
I just did. Well, I just used the tool you pointed me. I first installed the old version of the app, open and close it a few times, check the setting file, making sure, it has the old structure, and i "updated" with the newer version, it opens fine, and I check the setting file, the file has the new structure. So it doesn't really prevent the app from launching. So it is not really the problem. Will you be interested in being my beta tester?
btw, i just "thanked" you in both the replies.
blkjack2u said:
I was thinking the 'Thanks' button that is attached to a post; kind of like receiving a badge for helping others.
As a user I'd probably be unhappy if I was asked to have to reinstall, but I guess if the update contains some good stuff and I wouldn't lose data, it isn't too difficult to uninstall/install again and is only a minor inconvenience.
Is there anyway you can code in to convert from previous storage structure to the new one since a standard WP app upgrade preserves the previous version?
Click to expand...
Click to collapse
Are you using dotfuscator or another tool to ofuscate your code?
No I don't, but I probably should. Can I know why you asked?
MJCS said:
Are you using dotfuscator or another tool to ofuscate your code?
Click to expand...
Click to collapse
My app was rejected again. I am running out of ideas what I can do now.
Alright, let me preface this with a few things... I am FAR from new to android, rooting, linux, exploits, or almost anything embedded (UART, JTAG, SPI, I2C, etc...). I am by no means a guru though...
I am attempting to root this device; it is an unlocked LG G4 US Cellular branded, MM 6.0 lgus991 22a rollback 2, and I am so far at a total impasse... I'll explain my situation.
No fastboot.
Bootloader is locked, and I cannot unlock it. If I try and check "Enable oem unlock" it unchecks itself, and reading through the dmesg it references a file stating two errors; one for lack of permissions, and another for no file(same filename though; likely trying to create the file, being denied, then trying to edit a non-existing file). I forget the exact file name but I have the name of it saved somewhere(persis1234 or something like that, I just don't remember the exact path, I can post it later if it makes a difference).
I have had minor success with the dirtycow exploit, but mostly just replacing files and nothing getting anywhere, or the phone quickly reboots if I replace certain system files(ifconfig, toybox, toolbox, etc...) When it works,it says I have root, but it is VERY limited due to selinux, and the context. Also unable to get a root shell open.
Selinux is protected and I haven't been able to find a way to make it permissive as of yet. Past attempts of editing the recovery or init have resulted in "secure boot error 1003"; phone reboots, and then still stock...
If I grenade this thing, I will only slightly give a f**k. I am not above pulling this thing apart and trying to JTAG my way in if I need to, as it is not my only device. Which seems to me to be the only way at the moment aside from finding another kernel exploit like dirtycow or rowhammer... Unless someone else has another idea, but for now I am going to pursue the JTAG route.
Would something that I already own like a buspirate, RPI, or Arduino Mega, be enough or would I need something like a busblaster? I just don't want to spend more than I need to. I'd rather spend the money on a new phone than something like a medusa pro or something like that.
Any help is appreciated
Why not to flash TOT and then proceed with unlock through lg unlock tool? Maybe it fix the fastboot issue.
aanarchyy said:
Alright, let me preface this with a few things... I am FAR from new to android, rooting, linux, exploits, or almost anything embedded (UART, JTAG, SPI, I2C, etc...). I am by no means a guru though...
I am attempting to root this device; it is an unlocked LG G4 US Cellular branded, MM 6.0 lgus991 22a rollback 2, and I am so far at a total impasse... I'll explain my situation.
No fastboot.
Bootloader is locked, and I cannot unlock it. If I try and check "Enable oem unlock" it unchecks itself, and reading through the dmesg it references a file stating two errors; one for lack of permissions, and another for no file(same filename though; likely trying to create the file, being denied, then trying to edit a non-existing file). I forget the exact file name but I have the name of it saved somewhere(persis1234 or something like that, I just don't remember the exact path, I can post it later if it makes a difference).
I have had minor success with the dirtycow exploit, but mostly just replacing files and nothing getting anywhere, or the phone quickly reboots if I replace certain system files(ifconfig, toybox, toolbox, etc...) When it works,it says I have root, but it is VERY limited due to selinux, and the context. Also unable to get a root shell open.
Selinux is protected and I haven't been able to find a way to make it permissive as of yet. Past attempts of editing the recovery or init have resulted in "secure boot error 1003"; phone reboots, and then still stock...
If I grenade this thing, I will only slightly give a f**k. I am not above pulling this thing apart and trying to JTAG my way in if I need to, as it is not my only device. Which seems to me to be the only way at the moment aside from finding another kernel exploit like dirtycow or rowhammer... Unless someone else has another idea, but for now I am going to pursue the JTAG route.
Would something that I already own like a buspirate, RPI, or Arduino Mega, be enough or would I need something like a busblaster? I just don't want to spend more than I need to. I'd rather spend the money on a new phone than something like a medusa pro or something like that.
Any help is appreciated
Click to expand...
Click to collapse
I am new to LG devices so perhaps this is a bit different(had mostly Samsung or HTC). But from what I can find, that won't help unless it's pre-rooted or my bootloader is unlocked. And I am unable to find a pre-rooted TOT. Unless I am just completely missing something here...
I am not trying to go to stock, the device is already stock and functions mostly alright(aside from the inability to add a Verizon APN, so I'm stuck with 3g). But also attempting to have a bit of a failsafe if I wanton flash something I shouldn't have and still have a recovery option. Which is why I brought up the JTAG option, as I'm sure I would use it in more than just this device.
Not sure why you are attempting to reinvent the wheel with a device that has been out for 2 years....
LG devices are very different from Samsung and HTC. You should read up on the LGUP tool to flash .kdz and .tot file to put the device as close to stock as possible before any further attempts.
Could also look at entering hidden menu options via the dialer in order to select/modify apn settings.
TWRPinFish can be found here in the development section. Will likely be your only option if you cannot fully unlock the bootloader.
Since the Tmo and ATT/international versions allowed bootloader unlock, other variants didn't see as much support. Was easy for us... Sorry to say(for you).
Wish ya the best of luck though
Just a quick remark could jtag be used in such a way to make the boolloader thinks it is something else and maybe trick it in to doing something?????
ElfinJNoty said:
Not sure why you are attempting to reinvent the wheel with a device that has been out for 2 years....
LG devices are very different from Samsung and HTC. You should read up on the LGUP tool to flash .kdz and .tot file to put the device as close to stock as possible before any further attempts.
Could also look at entering hidden menu options via the dialer in order to select/modify apn settings.
TWRPinFish can be found here in the development section. Will likely be your only option if you cannot fully unlock the bootloader.
Since the Tmo and ATT/international versions allowed bootloader unlock, other variants didn't see as much support. Was easy for us... Sorry to say(for you).
Wish ya the best of luck though
Click to expand...
Click to collapse
I don't really see this as reinventing the wheel as right now there is no root for this device, I am looking for a way to do it though. Which is why I was asking about JTAG/eMMc programming as a viable option to do this, especially if I may have a few borked flash attempts, it would be a nice fail-safe.
Most dialer codes do not work, and the few that do, pop up a menu saying "This program does not work on your phone"; even though I can see some info behind the toast, I cannot scroll and as soon as I click ok, it closes.
TWRPinFIsH is a no-go, need to be rooted and be able to disable SELinux, neither of which I can do.
The name of the file that stores the "oem unlock" seems to be /dev/block/platform/soc.0/f9824900.sdhci/by-name/persis1234
Would someone that is able to oem unlock be able to tell me what the contents of that file are?
aanarchyy said:
The name of the file that stores the "oem unlock" seems to be /dev/block/platform/soc.0/f9824900.sdhci/by-name/persis1234
Would someone that is able to oem unlock be able to tell me what the contents of that file are?
Click to expand...
Click to collapse
I own a T-Mobile h811
Running ResurrectionRemix Nougat
.../persis1234 not present
I have an LG H812 and I have the same as previous post - the directory is there but no persis1234 file. The directory you are indicating contains a list of the partitions that are present on the phone's internal memory.
Hello? Anybody still around? I hope so. I need some advice/help. I will bold my questions so they are easier to reference.
I have two identical Lumia 1020’s that I upgraded to Windows 10 using this procedure posted by hikari_calyx https://forum.xda-developers.com/windows-10-mobile/guide-win10-mobile-offline-update-t3527340 and summarized here https://forums.windowscentral.com/windows-10-mobile-how-guides/452310-how-offline-update-unsupported-lumias-8-1-latest-10586-xxx-14393-xxx-15063-xxx-build.html
This procedure got both phones to 10586.107. However, one phone was able to get updates to Redstone automatically. The other is stuck at 10586.107. The stuck phone is my daily driver and the phone that I’d like to be on Redstone. The one that actually made it to Redstone is a spare and has mechanical issues. It was the phone that I upgraded first to familiarize myself with the upgrade process. The phones are identical except the one that fully upgraded does not have an active SIM.
Since the upgrade I’ve been spending many hours in the forums and on youtube looking for reasons why my one phone might not be getting updates and also for ways to force updates. Most posts are very old and maybe I’m late to the party, but I’d like to get this other phone upgraded.
Here’s what I’ve tried:
1) Since the phones are 1020’s I had to modify the “OEMInput.xml” file to get past a bug in the update process. Following this guide https://forum.xda-developers.com/windows-10-mobile/guide-how-to-fix-windows-update- issue-t3697172, I was able to continue getting updates on the one fully upgraded phone. Since I cannot get updates at all on the other phone, I don’t know if this will work for
it yet.
2) I checked that all my registry settings are properly set for my model:
PhoneManufacturer=”MicrosoftMDG”
PhoneManufacturerModelName=”RM-1085_11302”
PhoneModelName=”Lumia 950 XL”
PhoneHardwareVariant=”RM-1085”
I examined the source code for DHTUpgradeAdvisor and I think this is all that should be set.
3) I tried the Windows Insider App, to be sure I’m getting updates but it when I click the “Get preview builds” it throws a Server Error “A connection error prevented us from downloading programs for you. Please check the date/time of your device and its network connection and try again.”
Of course my date time is correct.
I tried reinstalling the Windows Insider App. Same problem.
I did notice a difference between the phones here. When I open the Windows Insider App on the phone that fully upgraded it shows “Go to Settings” instead of “Get Preview Builds”. The phone that fully upgraded has a “Windows Insider Program” link under Settings>Update&Security. The phone that refuses to upgrade does not have this link. The app does not work on either phone. Why is there a difference between the phones here? How can I get the Windows Insider App working again?
4) I’ve tried to add the provisioning for Mobile Enterprise, but I can never get it to show “Enterprise” in the about section. The package does appear in provisioning. I’ve tried multiple .ppkg files. None have worked.
I did see in a post that you must opt out of the Window Insider Program. I’m not sure how to do this since I cannot get into the Windows Insider App. Also it mentions that the SIM should be removed. I did not try this.
Is there a registry setting or something that can be modified to change the update rings or opt out of the insider program? Or does the insider app associate my phone with my Microsoft account and I need to login to my Microsoft account and somehow disassociate it there? Does the SIM really need to be removed?
5) I had the idea to make an image of the fully upgraded phone and then dump it into the non-upgraded phone and then hard reset it and recommission it. I tried to make an image with Windows Phone Internals 2.8. I am able to unlock the bootloader of the upgraded phone but I’m not able to get it into Mass Storage mode in order to make an image. I’m not sure what I’m doing wrong. I have only a basic idea of the phone hardware architecture so I don’t even know what to try next to get an image. Any ideas?
Is this idea even feasible? Is it possible to take an image from one phone and dump it into another effectively cloning the first one? I wasn’t sure if there would be problems with hardware (MAC addresses, etc) mismatches with the software or not. Anyone tried this? Should I pursue this more?
6) The next option is to pump the updates into the phone offline. I am not clear on how to do this. Of course I know how to use iutool (as long as it behaves) since I used it to get the phones to 10586.107.
There is a guide to updating offline here https://forum.xda-developers.com/windows-10/windows-10-mobile/w10m-builds-update-links-collection-cab-t3234805. It looks like this is mostly a guide to capture the cabs for posterity. For upgrading, it’s not clear to me how to begin. There are links to some update cabs in the post, but also this link: https://www.catalog.update.microsoft.com/Search.aspx?q=RM-1085_11302. It has info, but I don’t know what I’m looking at. This is where I get confused. Are these even the cabs I need? Are these update cabs independent of the phone model? Can I just grab the cabs within those links and copy them to my PC and then update my phone using iutool? Do I need to do all the updates in order or can I skip ahead? How do I know which ones I can skip over? What is 000-88 based vs 000-HK based vs CTM-MO based devices? Do I use iutool as I did before (keeping the same files in place and just overwrite the cabs with the new ones)? I see these questions partly answered in the subsequent posts, but I’m still unclear of the cabs to use and the order. This method seem like it’s for people smarter than myself and has a high risk of trial and error and brick potential. I’d rather figure out how to get the proper update pushed over-the-air if possible, but if someone has done this method on a 1020 successfully I might try it.
I would prefer to not have to do hard resets or rollbacks if possible since I feel like I'm very close to getting it to work (It worked on my other phone naturally).
Thank you to anyone who is able to answer any of my questions and give me advice on which of the above methods is best to pursue!
I’ve never posted to a social media site such as this, so if I’ve posted wrongly I apologize.
Your friend,
WolfCobra
If you want to upgrade to higher versions, just go to https://www.wpvision.de/tourniquet and download the "Phone Updater" there. With that you will be able to update any Windows Phone 8.1 up to 15063.297.
You might get into some trouble because you already modified OEMinput.xml. But overall you do not need to do any registry editing to get to build 15063 (Version 1703).
I registered on the wpvision.de site. I am waiting to be accepted for membership so that I can view the posts describing the functionality and operation of the phone updater. I'm not able to access much of the site, so I cannot tell how helpful this will be yet. Thank you for pointing out this site to me; it is one that I have not seen before.
WolfCobra said:
I registered on the wpvision.de site. I am waiting to be accepted for membership so that I can view the posts describing the functionality and operation of the phone updater. I'm not able to access much of the site, so I cannot tell how helpful this will be yet. Thank you for pointing out this site to me; it is one that I have not seen before.
Click to expand...
Click to collapse
I was able to fully update my 1020 with the Phone Updater from wpvision.de. It works very well. I would recommend it to anyone still looking to update an unsupported phone.
WolfCobra said:
I was able to fully update my 1020 with the Phone Updater from wpvision.de. It works very well. I would recommend it to anyone still looking to update an unsupported phone.
Click to expand...
Click to collapse
Can you please provide the linkto the thread?
Hey I'm new to the forum. Ii was on here the other night and found a thread which had a guide on how to back up appx from W8.1M and W10M offline. but I can't seem to find it again. I've even used the search tool. but no luck
I recalling seeing some app that required interop unlock, but I think it only backed up app data. I don't recall seeing anything for backing up the actual appx - that I'd be very interested in. Even better if it'd be possible to extract apps that have been delisted off of my WP8.1 phone to get on my W10.