Related
So let's start this thread by saying I was stupid.
In my desperation to upgrade my ROM I went and flashed my Focus with the new Omnia engineering rom. Stupid yes but it flashed. The reason I did it was non of the Samsung focus retail Roms would flash with the WP7 flashing tool not even the jK2 ROM. Which is suppose to be the basic 7004 ROM.
Every time I flashed it would say "This Rom does NOT match the device" or "this device is NOt retail."
So let me just state I had the "RTM Mango" flash on my device already flashed and worked. I was trying to upgrade the firmware and radio stacks. The phone aways worked and was NOT a demo device.
I have tried to flash:
1. jK2 stock Rom same error as above
2. Rom for v1.4 won't work same error as above
3. Rogers Rom on my AT&T focus same error as above.
Basically the only rom that flashed was the engineering rom for the Omnia.
Now the phone boots (with a Omnia splash screen ) I can get it to download mode I can even use the phone just none of the buttons work! I really just want to get a Samsung focus rom back on don't care if it's not Mango at the moment.
My questions:
1. Anyone got an engineering rom for the focus seems to be the only Roms that can load on my device
2. Anyone got some advise to get it back to a Samsung focus rom?
I know I shouldn't have but it's done and can't cry over spilt milk.....
I would really appreciate the help.
I'm not sure what you mean by Jk2's rom, but have you tried the 1.3 version, not rogers?
http://forum.xda-developers.com/showthread.php?t=1131022
this thread has rogers, att 1.4 and att 1.3, all for focus. Ive successfully flashed my 1.3 focus several times. Also, in this thread they talk about how flashing 1.4 is always iffy.
Best way to get back to a Focus ROM is probably to restore a backup that was taken when you upgraded the phone. I hope you can still connect the phone to the Zune software? If so, try that.
The Omnia has physical buttons, the Focus uses capacitive buttons only (for the front three). I'm not surprised the drivers are different.
Did you by any chance use a hack to get NoDo on the phone? The "debranding" hack shouldn't prevent flashing, but will result in you receiving a different ROM from the upgrade servers than was quite meant for your phone. Chris Walsh's update hack did not install the full set of update packages it should have, resulting in what has become known as a "Walshed" phone. Walshed phones, because they're kind of partway between updates, can't receive further updates. A tool was later released to fix a Walshed phone.
The fact that the Focus ROMs wouldn't flash but the Omnia onw would is quite odd; I'm not sure what would cause that.
If at all possible, I recommend restoring your phone to a retail configuration using a Zune backup, and them trying the official update path again. Only once you've exhausted your options there should you try anything else.
GoodDayToDie said:
Best way to get back to a Focus ROM is probably to restore a backup that was taken when you upgraded the phone. I hope you can still connect the phone to the Zune software? If so, try that.
The Omnia has physical buttons, the Focus uses capacitive buttons only (for the front three). I'm not surprised the drivers are different.
Did you by any chance use a hack to get NoDo on the phone? The "debranding" hack shouldn't prevent flashing, but will result in you receiving a different ROM from the upgrade servers than was quite meant for your phone. Chris Walsh's update hack did not install the full set of update packages it should have, resulting in what has become known as a "Walshed" phone. Walshed phones, because they're kind of partway between updates, can't receive further updates. A tool was later released to fix a Walshed phone.
The fact that the Focus ROMs wouldn't flash but the Omnia onw would is quite odd; I'm not sure what would cause that.
If at all possible, I recommend restoring your phone to a retail configuration using a Zune backup, and them trying the official update path again. Only once you've exhausted your options there should you try anything else.
Click to expand...
Click to collapse
Firstly thank you for the time you took to reply.
Yes the history of this device is quite a lengthy one. I did do a NODO hack to get it to NODO. I then used the internal MS bits leaked to the net to force it to Mango. I was picking up some funnies like no matter how quick or soft I pressed the back button it would go into multi tasking making the phone impossible to use.
So I looked and researched and found my firmware, bootloaders etc were way out of date. I flashed the Omnia rom onto the Focus in hope that it was the same phone but alas its to late now......
Ok so when I connect it to the PC Zune picks it up all dandy but as a new phone - Omnia not my old focus. Is there a way to trick it into thinking its my Focus?
The phone functions in the sense that it boots, I can use it just don't have any buttons to use it with. All the screen functions work perfectly.
I will download Walsh tool to un Walsh the phone and try again...
I really appreciate the help!
I don't think you can "trick" it into seeing it as your Focus, because from a software perspective, it just isn't. However, the restore points (backups) are tied to the hardware, not the software. To see if you can restore one, first check in Window Explorer at the path %localappdata%\Microsoft\Windows Phone Update\ and see how big the contents of that folder are. There should be hundreds of meg to a few gigs, depending on how big the backup is.
Now, that's only going to be the most recent restore point. If you made backups of your earlier restore points, you can send the phone even further back, hopefully to before quite so many things get messed up. However, each time you do an update with Zune it overwrites the location where the previous restore point was. Note that if you installed any updates through a mecanism other than Zune, for example usign the WPSHIFT tool that was used for the beta, it probably took a backup but might have put it in a different location (often in TEMP, which hopefully you haven't cleaned out).
If you have Volume Shadow Copies enabled on your PC (Vista/Win7/any recent Server), you may be able to use the Previous Versions feature to pull an older restore point than the most recent one, or to recover a restore point if it was deleted for some reason. Be careful, though - old shadow copies are deleted as space is needed for other things, but they aren't deleted atomically; it's possible you'll pull only half of an old restore point or something equally silly (they're made up of hundreds or thousands of small files).
Once you've got your restore point, I strongly recommend making a backup of it by copying the folder! Then, connect your phone and start Zune, and go to Settings -> Device -> Update. It'll probably say there aren't any updates available, that's fine. In the same part of the window where it says that, though, there should be an option to restore a backup (it'll give the date of the backup and a restore button). If that button isn't visible, re-copy the restore point over the location where Zune expected to find it (%localappdata%\Microsoft\Windows Phone Update\), and check for updates again.
As for the un-Walshing tool, it probably won't do anything on your OmniaFocus. It may fix the problem if you successfully use a restore point (and get back to a pure Focus), though. There's a good chance that the last restore point you have will be from right before you began the Mango update process, in which case your phone will be back in its Walshed state, ready for un-Walshing using the tool.
I hope that helps. If you do decide to try flashing again (if you don't have a restore point, this is probably the only option), make sure you're using a ROM for your hardware revision of the Focus. There are two, the 1.3 revision (the first one released), and the 1.4 revision (released later, identical except it uses a different Flash memory chip internally and therefore has different drivers). If you bought your phone any time in 2011, it could be either a 1.3 or a 1.4. There are a few ways to check, but one of the best (since your software is currently messed up) is to look under the battery. There's a sticker that should say soemthing like "rev1.3/rev1.4". You need to match that revision number when selecting a ROM to flash, or (even if it works) you wouldn't be able to access the phone's internal storage.
It seems a little unlikely to me, but it's possible that Walshing your phone made it report itself as an Omnia, thus the reason you could flash that ROM (but not the Focus ones). I'd expect that to be based on lower-level hardware checks, though.
GoodDayToDie said:
I don't think you can "trick" it into seeing it as your Focus, because from a software perspective, it just isn't. However, the restore points (backups) are tied to the hardware, not the software. To see if you can restore one, first check in Window Explorer at the path %localappdata%\Microsoft\Windows Phone Update\ and see how big the contents of that folder are. There should be hundreds of meg to a few gigs, depending on how big the backup is.
Now, that's only going to be the most recent restore point. If you made backups of your earlier restore points, you can send the phone even further back, hopefully to before quite so many things get messed up. However, each time you do an update with Zune it overwrites the location where the previous restore point was. Note that if you installed any updates through a mecanism other than Zune, for example usign the WPSHIFT tool that was used for the beta, it probably took a backup but might have put it in a different location (often in TEMP, which hopefully you haven't cleaned out).
If you have Volume Shadow Copies enabled on your PC (Vista/Win7/any recent Server), you may be able to use the Previous Versions feature to pull an older restore point than the most recent one, or to recover a restore point if it was deleted for some reason. Be careful, though - old shadow copies are deleted as space is needed for other things, but they aren't deleted atomically; it's possible you'll pull only half of an old restore point or something equally silly (they're made up of hundreds or thousands of small files).
Once you've got your restore point, I strongly recommend making a backup of it by copying the folder! Then, connect your phone and start Zune, and go to Settings -> Device -> Update. It'll probably say there aren't any updates available, that's fine. In the same part of the window where it says that, though, there should be an option to restore a backup (it'll give the date of the backup and a restore button). If that button isn't visible, re-copy the restore point over the location where Zune expected to find it (%localappdata%\Microsoft\Windows Phone Update\), and check for updates again.
As for the un-Walshing tool, it probably won't do anything on your OmniaFocus. It may fix the problem if you successfully use a restore point (and get back to a pure Focus), though. There's a good chance that the last restore point you have will be from right before you began the Mango update process, in which case your phone will be back in its Walshed state, ready for un-Walshing using the tool.
I hope that helps. If you do decide to try flashing again (if you don't have a restore point, this is probably the only option), make sure you're using a ROM for your hardware revision of the Focus. There are two, the 1.3 revision (the first one released), and the 1.4 revision (released later, identical except it uses a different Flash memory chip internally and therefore has different drivers). If you bought your phone any time in 2011, it could be either a 1.3 or a 1.4. There are a few ways to check, but one of the best (since your software is currently messed up) is to look under the battery. There's a sticker that should say soemthing like "rev1.3/rev1.4". You need to match that revision number when selecting a ROM to flash, or (even if it works) you wouldn't be able to access the phone's internal storage.
It seems a little unlikely to me, but it's possible that Walshing your phone made it report itself as an Omnia, thus the reason you could flash that ROM (but not the Focus ones). I'd expect that to be based on lower-level hardware checks, though.
Click to expand...
Click to collapse
Thank you for the reply!
So looks like I am screwed. I looked for the backup and nothing on my machine even tried volume shadow copy and nothing in the Windows Phone Update folder.
I might have to try create a USB JIG to force a flash onto the phone. That should work right? That should flash which ever ROM I like regardless of the checks that things like WP7 Downloader do?
I would appreciate the guidance before I go ahead and build the USB JIG.
PS _ Anyone know what files are inside the backup folder maybe I can search windows for those and find the back up folder somewhere
The updates are usually stored here:
"C:\Users\%YOUR_USER%\Local Settings\Microsoft\Windows Phone Update\"
Either search for a "RestorePoint" folder (without quotes) or "Data.0.dat" "Data.1.dat" etc files
EnderPsp said:
The updates are usually stored here:
""
Either search for a "RestorePoint" folder (without quotes) or "Data.0.dat" "Data.1.dat" etc files
Click to expand...
Click to collapse
THANKS so much I FOUND a backup C:\PreMangoState
This is when I did the Mango upgrade using the "MS internal leaked" files.
Going to try this.
I am going to suggest you try the engineering ROM for the Samsung Focus: http://forum.xda-developers.com/showthread.php?t=1045968
day2die said:
I am going to suggest you try the engineering ROM for the Samsung Focus: http://forum.xda-developers.com/showthread.php?t=1045968
Click to expand...
Click to collapse
THAT WORKED YOU ROCK
Now can I ask why only engineering ROM's are working and will I be able to get it to MANGO?
myphonerules said:
THAT WORKED YOU ROCK
Now can I ask why only engineering ROM's are working and will I be able to get it to MANGO?
Click to expand...
Click to collapse
So as soon as I plugged it in Zune found the phone and upgraded all the upgrades all the way to mango
Thank you once again. Do you know what the latest GSM firmware is?
I have similar problem except mine is stuck on the samsung logo screen so cannot connect to zune.
I am trying to flash this engineering ROM that seemed to work for you, but it keeps saying Error!! "This Device does NOT match with selected binary. Downloader will NOT do anything" and thus the flash will nto complete.
Any suggestions?
neibl said:
I have similar problem except mine is stuck on the samsung logo screen so cannot connect to zune.
I am trying to flash this engineering ROM that seemed to work for you, but it keeps saying Error!! "This Device does NOT match with selected binary. Downloader will NOT do anything" and thus the flash will nto complete.
Any suggestions?
Click to expand...
Click to collapse
Have you tried the retail roms (check the general forum there is a sticky with the retail roms) if you getting the error "This device does not match with the selected binary" with the flasher it could be one of two things:
1. Your device is not an engineering device and you need to use the right retail rom.
2. Which version of the WP7 Downloader tool are you using 7.05, 7.21 or 7.41?
For the retail ROM you should use 7.05
For the engineering ROM you should use 7.41.
7.41 comes with the new leaked Samsung OMNIA 7 ROM (Do a search for that rom) DO NOT FLASH (like I did ) the OMNIA ROM onto your focus it will not work.
The other question is if your phone is stuck on the "SAMSUNG" screen can you get it into DOWNLOAD mode (Turn the phone off, then hold CAM + VOL DOWN and POWER) It should then turn on and go into DOWNLOAD MODE. The WP7 tool will only see the phone is in DOWNLOAD MODE. From what you telling us with the error above you are getting into DOWNLOAD MODE but just confirm.
IMO if you can still get into DOWNLOAD MODE not all is lost.
I already have flashed the omnia ROM onto my phone that is why I am in this problem. I have reflashed the focus ROm but it is frozen on the logo screen no matter what I do.
Seems like this engineering ROM fixed it for the lad who created this post, so I might give it a try, what do you think?
Yes I can get the phone into download mode & also the format mode (it doesn't do anything though), I cannot connect the phone to zune because it freezes on the logo screen before launch. Also I have 7.03, 7.05, & 7.21 and have tried all of them thus far, did not know of the 7.41.
So 7.41 and flash the engineering rom? It sounds like you have some ideas, please share it would be greatly apreciated.
neibl said:
I already have flashed the omnia ROM onto my phone that is why I am in this problem. I have reflashed the focus ROm but it is frozen on the logo screen no matter what I do.
Seems like this engineering ROM fixed it for the lad who created this post, so I might give it a try, what do you think?
Yes I can get the phone into download mode & also the format mode (it doesn't do anything though), I cannot connect the phone to zune because it freezes on the logo screen before launch. Also I have 7.03, 7.05, & 7.21 and have tried all of them thus far, did not know of the 7.41.
So 7.41 and flash the engineering rom? It sounds like you have some ideas, please share it would be greatly apreciated.
Click to expand...
Click to collapse
Ok so you need to download the latest Samsung Omnia 7 ROM it will have the WP7 Downloader 4.21. Thats the only one that will flash the engineering ROM onto the device.
Zune will not pick up the phone till it completely boots so Zune wont help you in this case. You have to try and fix it using your WP7 downloader(s).
This is the link I used to get the Downloader: http://www.mobiletechworld.com/2011/10/15/update-your-samsung-omnia-7-to-the-latest-i8700xxki3-firmware-now/
Good luck!
Engineering ROM did not work, still frozen on samsung logo screen, something is definitely broken on the phone that will not let it get past this point and I have no idea. Seems like no one else knows either as no one has been able to solve this for over 7 months.
If anyone thinks they can solve this please suggestions are welcomed. If you need more details please let me know. If someone can fix this I'd be willing to paypal them real cash no joke.
Much thanks to myphonerules for helping!
If I call samsung and complain will they tell me i'm out of luck? I got the phone off ebay so its not covered by anything.
neibl said:
Engineering ROM did not work, still frozen on samsung logo screen, something is definitely broken on the phone that will not let it get past this point and I have no idea. Seems like no one else knows either as no one has been able to solve this for over 7 months.
If anyone thinks they can solve this please suggestions are welcomed. If you need more details please let me know. If someone can fix this I'd be willing to paypal them real cash no joke.
Much thanks to myphonerules for helping!
If I call samsung and complain will they tell me i'm out of luck? I got the phone off ebay so its not covered by anything.
Click to expand...
Click to collapse
You sure you don't have a DEMO phone? Has it ever worked on a GSM network?
No its not a demo phone, i used the phone with my AT&T SIM card for few days. Then i put in a 32mb microsd card and after 24 hours it reset into a gimped mode with only 15 mb where i couldn't do anything and had no at&t apps on it strangly also. I flashed the samsung omnia 7 ROM onto the phone and would not load past the omnia 7 load screen. Then I flashed the focus ROM (it wasn't available originally) back and it would not load past the samsung screen. By this point I really just think the phone is completely done.
Any suggestions? or think its garbage?
I'm debating buying a focus with broken screen off ebay and using the screen from this one to replace it and bam pretty much new phone.
Is there a way to get a convert a non retail focus to retail? Is there a retail ROM available for the focus that can be flashed on the non retail version?
So my friend got her a window phone 7 from Craigslist tmobile (htc 7) and she can't erase whats on her phone , I think is because it used to be a display phone for the tmobile store, reason I think that is because it let us reset everything but all the stuff comes back again, and I saw an animation playing like the display phones, is there anyway she can erase everything on it ? Like a regular phone , thanks
Flash a retail ROM onto it. If it's actually the same hardware (should be, but it's possible it's not) then this should get it working just fine. Check the device-specific forum for ROMs that are available, and read the flashing instructions carefully - you don't want to mess anything up.
You could also try flashing a custom ROM, if you want to get a few cool features at the cost of needing to mess with the secondary program loader (bootloader, essentially).
GoodDayToDie said:
Flash a retail ROM onto it. If it's actually the same hardware (should be, but it's possible it's not) then this should get it working just fine. Check the device-specific forum for ROMs that are available, and read the flashing instructions carefully - you don't want to mess anything up.
You could also try flashing a custom ROM, if you want to get a few cool features at the cost of needing to mess with the secondary program loader (bootloader, essentially).
Click to expand...
Click to collapse
So is it like root for android ? Or jail breakin? Mm how long could it take cause I only see her at work , and I would need to take my laptop right ?
No and No, it's not like either of those. It's simply re-installing the OS that would have come with the device if you'd bought it at a store. Make sure the ROM matches - if it's a HD7, the code name is Schubert. If it's a 7 Pro, Gold. If it's something else, look it up.
For what it's worth, there's a non-trivial risk that the phone is stolen (display phones don't typically get sold, much less sold on CL). I also make no promises that its hardware is the same internally, which means it may never be usable as a normal phone. If you want to try, though...
I think flashing a full ROM takes something like 30 minutes, though I've never done it myself. You need to download the ROM and have the RUU (ROM Update Utility) installed on your PC. Reboot the phone, holding the Volume Down button to put it into Secondary Program Loader mode (SPL, which allows you to modify the ROM). Connect the USB cable to the PC; the SPL screen should say USB at the bottom after the PC automatically installs some drivers. Total time thus far ~2 minutes. Then run the RUU, select the ROM to flash, and give it time.
GoodDayToDie said:
No and No, it's not like either of those. It's simply re-installing the OS that would have come with the device if you'd bought it at a store. Make sure the ROM matches - if it's a HD7, the code name is Schubert. If it's a 7 Pro, Gold. If it's something else, look it up.
For what it's worth, there's a non-trivial risk that the phone is stolen (display phones don't typically get sold, much less sold on CL). I also make no promises that its hardware is the same internally, which means it may never be usable as a normal phone. If you want to try, though...
I think flashing a full ROM takes something like 30 minutes, though I've never done it myself. You need to download the ROM and have the RUU (ROM Update Utility) installed on your PC. Reboot the phone, holding the Volume Down button to put it into Secondary Program Loader mode (SPL, which allows you to modify the ROM). Connect the USB cable to the PC; the SPL screen should say USB at the bottom after the PC automatically installs some drivers. Total time thus far ~2 minutes. Then run the RUU, select the ROM to flash, and give it time.
Click to expand...
Click to collapse
Thanks for the tip I really appreciate it , I am try tomorrow I saw about phone and compared to online it looks the same, I'll try tomorrow and let you know
Just noticed that the Chinese site Rerede.com has finally managed to build support for the WiFi card in the Surface Pro in a build of Android-IA.
This build seems to support everything, apart from bluetooth:
Original link: I don't have rights to place URLs in as I haven't posted enough here. If a moderator can add the link here, I would appreciate it.
Original text (from Google Translate):
Code:
All along, only heard Surface Pro can run Ubuntu and Android. But never seen someone real up and running, often took a running Live CD boot to coax interface, now Rerede.com released China's first support for Surface Pro Android system. Support the Android installed on your machine up. And it can coexist with your Windows!
Working conditions:
· Touch
· Keyboard
· Camera
· Gravity sensor · WIFI
· Other
Not supported:
· Bluetooth
Compatibility:
· Support and native dual-boot Windows 8
• The need to disable Secure Boot
Data is priceless! Please make the necessary data backup before installing! We do not assume any responsibility for loss of data!
Unzip password: rerede.com
Copy the code
Preparation:
In a hard disk to free up more than 1G unallocated space, 4GB recommended
Installation:
1, decompress, burn to use UltraISO to live.img U disk
2, disable SecureBoot
3, the use of U disk boot, select the third item, manually install Android4, tips Choose disk to install Android, select the disk you want to install, I chose Surface of SSD (1),
Tips Do you want to preserve Windows and dual boot (if dual boot Windows), press Y
5 Tips Do you want to resize Windows to make more space (whether android resized), press N
6 Tips Install GummiBoot BootLoader (using gummiboot), press Y
7, when prompted Enter boot menu timeout (boot menu wait time), I chose 5
8, press Enter to install, the installation process approximately less than 1 minute.
9 After the installation is complete, unplug the U disk, enter the restart to complete the installation reproduced or quoted, please indicate from the hot community , Rerede.com
Pictures attached
That looks really nice. Hope they figure out the bluetooth as well.
JLIT99 said:
Just noticed that the Chinese site Rerede.com has finally managed to build support for the WiFi card in the Surface Pro in a build of Android-IA.
This build seems to support everything, apart from bluetooth:
Click to expand...
Click to collapse
Thanks for this, it's really working, although far from perfect. Fastest touch response on android =))
Here's the direct link to download: http://rerede.com/surface.android-ia.rerede.com.vPRC2.zip
Could you get the front Cam working?
Turns out that front cam doesn't run by default. I fixed it along with some other things like youtube playback, play store etc. It's almost perfect now
Surface 2 Pro
Has someone tested these instructions on a Surface 2 Pro ? Working ?
Unfortunatly, I have a Surface 1 Pro and encounter the following error:
FATAL: ASERTION FAILED bootable/iago/plugins/gummiboot.c:gummiboot_execute:154 'efibootmgr' encountered an error (status 100)
Gummiboot the EFI bootmgr does not install. Maybe it would be possible to install it manually.
Secure Boot is disabled, and I also tried different USB sticks and the original unmodifed Android-IA image. No success.
Current progress: managed to boot into Android-IA using Refined, which itselfs loads Gummiboot.
However the overall stability of Android-IA on the Surface Pro is not good:
- Wifi most of the time does not work. Turning it on/off does not help. Neither does it help to disable power saving features. Maybe we could try a different driver
- Sometimes when the device is not used for about 2 minutes and goes black, it cannot be turned on again. I have to hold the power button to force a shutdown.
ToniSoft said:
Current progress: managed to boot into Android-IA using Refined, which itselfs loads Gummiboot.
However the overall stability of Android-IA on the Surface Pro is not good:
- Wifi most of the time does not work. Turning it on/off does not help. Neither does it help to disable power saving features. Maybe we could try a different driver
- Sometimes when the device is not used for about 2 minutes and goes black, it cannot be turned on again. I have to hold the power button to force a shutdown.
Click to expand...
Click to collapse
What do you mean by using Refined?
how do you get this installed? When i reach the instructions to press Y if to save dual boot my type keyboard does not work. How did you proceed? Thank you.
zcrugby,
How do you get this installed? When i reach the instructions to press Y if to save dual boot my type keyboard does not work. How did you proceed? Thank you.
Click to expand...
Click to collapse
You need to use a USB hub, so that you can have you USB stick and USB keyboard attached simultaneously. This installation program does not recognize the Surface keyboard, but it does recognize a standard USB keyboard.
I, however am having a different problem. I get (almost) to the end of the whole process, after it says press enter to continue with the installation and does a bunch of stuff, but then give the following error:
FATAL: ASERTION FAILED bootable/iago/plugins/gummiboot.c:gummiboot_execute:154 'efibootmgr' encountered an error (status 100)
It was mentioned earlier in this thread, but no one seemed to shed any light on the subject. In other forums some have suggested that it was just an incompatible memory stick, but I have not tried multiple memory stick by different manufactures...
Others have suggested that you need to disable AHCI and instead run in IDE mode, but with the Surface Pro 2's woefully underwhelming BIOS, I haven't yet figured out how to disable AHCI. There's some that say that simply changing some registry keys will do the trick, but I haven't gotten that to work yet, and I don't have extremely high hope for it when I do.
Does anyone here have any thoughts about this error??? Anyone run into it who has successfully gotten it working after seeing this error? If so, how?
Thanks!
please help: Fatal Asertion Failed... (status 100)
Does anyone have any light to shine on the follow error? Please?
FATAL: ASERTION FAILED bootable/iago/plugins/gummiboot.c:gummiboot_execute:154 'efibootmgr' encountered an error (status 100)
I've detailed some of the (failed) solutions I've found on other boards/threads regarding to how to get around this error on other devices, but none seem to be the trick for getting past this error on the surface. I'm really surprised that there don't seem to be more people trying to install Android on the MS Surface... or perhaps there are, but for most people things go more smoothly. Any help our there, please?
Thinking about returning the surface if I can't get android on it. I'm really interested in a powerful tablet that can dual boot windows/android.
Quixtrike said:
Does anyone have any light to shine on the follow error? Please?
FATAL: ASERTION FAILED bootable/iago/plugins/gummiboot.c:gummiboot_execute:154 'efibootmgr' encountered an error (status 100)
I've detailed some of the (failed) solutions I've found on other boards/threads regarding to how to get around this error on other devices, but none seem to be the trick for getting past this error on the surface. I'm really surprised that there don't seem to be more people trying to install Android on the MS Surface... or perhaps there are, but for most people things go more smoothly. Any help our there, please?
Thinking about returning the surface if I can't get android on it. I'm really interested in a powerful tablet that can dual boot windows/android.
Click to expand...
Click to collapse
When you get this error, it means that efibootmgr is unable to create the boot entry but all the files are in fact in boot partition. I also received this error, but since I also had Ubuntu (well, you kind of also need Ubuntu to access Android partitions easily anyway) I used the efibootmgr in Ubuntu to manually create Android entry. This way, I'm able to select advanced boot options under Windows (created desktop shortcut) and switch to Android really easily. You should leave the Windows as default so that you might never need a keyboard attached for boot menu. If you don't want to install Ubuntu just to solve this error, you *might* get away with a live Ubuntu CD, however I never tried that.
ozkaya said:
When you get this error, it means that efibootmgr is unable to create the boot entry but all the files are in fact in boot partition. I also received this error, but since I also had Ubuntu (well, you kind of also need Ubuntu to access Android partitions easily anyway) I used the efibootmgr in Ubuntu to manually create Android entry. This way, I'm able to select advanced boot options under Windows (created desktop shortcut) and switch to Android really easily. You should leave the Windows as default so that you might never need a keyboard attached for boot menu. If you don't want to install Ubuntu just to solve this error, you *might* get away with a live Ubuntu CD, however I never tried that.
Click to expand...
Click to collapse
Hi ozkaya, this sounds really promising, and I've even kind of gotten it installed, but it was going crazy (constant nonstop scrolling to select a boot mode as if I were holding down the arrow key; ended up being like Russian Roulette booting), so I decided to clean the slate and try again, the only problem is, I keep getting this error again... As a side note, I'm not overtly familiar with Ubuntu though I do have OSX successfully running on the Surface Pro 2, but I'm using a thumb drive to boot into it.
A few follow up questions:
-Are you saying that you use grub to boot into Android rather than gummiboot?
-Would you be willing to described "used the efibootmgr in Ubuntu to manually create Android entry" in more detail?
-How exactly to you select advanced boot options under Windows & create desktop shortcut?
*sorry if any of these questions are super basic. Back in the early XP days I was fairly savvy with dual/triple booting, but windows 8 and the Surface Pro's lackluster BIOS options are completely baffling me.
Quixtrike said:
Hi ozkaya, this sounds really promising, and I've even kind of gotten it installed, but it was going crazy (constant nonstop scrolling to select a boot mode as if I were holding down the arrow key; ended up being like Russian Roulette booting), so I decided to clean the slate and try again, the only problem is, I keep getting this error again... As a side note, I'm not overtly familiar with Ubuntu though I do have OSX successfully running on the Surface Pro 2, but I'm using a thumb drive to boot into it.
A few follow up questions:
-Are you saying that you use grub to boot into Android rather than gummiboot?
-Would you be willing to described "used the efibootmgr in Ubuntu to manually create Android entry" in more detail?
-How exactly to you select advanced boot options under Windows & create desktop shortcut?
*sorry if any of these questions are super basic. Back in the early XP days I was fairly savvy with dual/triple booting, but windows 8 and the Surface Pro's lackluster BIOS options are completely baffling me.
Click to expand...
Click to collapse
1- No I'm not using grub, in fact I also tried to daisy chain grub booting gummiboot booting Android and it doesn't work. I'm using native EFI entry.
2- I don't have it written up somewhere, I did it as I was reading and trying. But basically, you first need to install Ubuntu with dual boot with Windows. Have a look at the /boot partition, you will see the gummiboot files and config files there. Then research command line parameters for efimootmgr program and create the entry for the gummiboot file in /boot partition.
3- Just use google for this one, you can select advanced startup options somewhere from the settings in Windows 8 fancy menu. You can also create desktop shortcut for this. Once you completed Step 2, you will see Windows, Ubuntu and Android entries there. Since, Windows will be default, when you would like to switch to Android, you just double tap the shortcut and select Android. In Android you just power off and next restart will be Windows again. No keyboards, mouse etc needed. I also got the front cam and youtube playback working. Only bluetooth doesn't work.
Surface Pro 2
Anyone got this to work with Surface Pro 2? I am thinking of getting one, and if it could run android, im definitely getting one!
(I don't really see the point of getting Surface 1 when the 2 is out now)
I have followed the instructions and it installed fine, and then booted to android however as soon as I reboot I can no longer run android (or fastboot/recovery) without reinstalling it all over again from USB.
The error I get from gummiboot is:
HandleProtocol (DiskIoProtocol): Unsupported
Failed to start boot image 'Android': Unsupported
I would really appreciate some help from anyone who has a better understanding of this since I couldn't find anyone with a similar problem.
(I am using a 128gb Surface Pro 1/Original)
Thanks
when turning trusted platform module on and off it works sometimes
Jacob.Halsey1 said:
I have followed the instructions and it installed fine, and then booted to android however as soon as I reboot I can no longer run android (or fastboot/recovery) without reinstalling it all over again from USB.
The error I get from gummiboot is:
HandleProtocol (DiskIoProtocol): Unsupported
Failed to start boot image 'Android': Unsupported
I would really appreciate some help from anyone who has a better understanding of this since I couldn't find anyone with a similar problem.
(I am using a 128gb Surface Pro 1/Original)
Thanks
Click to expand...
Click to collapse
I'm having the same problem over and over .. still no luck
on my lumia 925 i was going to update to the windows 10, and when it was ready to install, it restart and the gears begin to spin, however it restart but in the gears the gauge doesn't fill, then no more than 5 or 7 seconds and it restart again the lumia has been stucking in this eternal loop of AT&T LOGO FOLLOWING THE GEARS.
i can prove that i have done everything in the correct way:
1. i have my account in hte windows insider program.
2. i have the app of windows insider.
3. i have leave it download all the night.
4. the smartphone has the full charge.
5. and for credibility: i'm a student of software development.
the big trouble is for the lumia software recovery tool and nokia care suite, with the lumia recovery, i open it in: MY PHONE DOES NOT START OR RESPOND and the software can't recover my phone because i have done a hard reset, flash mode and i still don't know all the combination bottoms to put an end to the loop while it is connected to the pc, while it is without connect it just turn off, it is the same for nokia care.
please someone help this is my only, i know that this is a risk but in the end i was hoping just common errors but THIS!!!.
PS: i live in Panamá there is not a microsoft store, there is not a windows phone expert.
XDA Visitor said:
on my lumia 925 i was going to update to the windows 10, and when it was ready to install, it restart and the gears begin to spin, however it restart but in the gears the gauge doesn't fill, then no more than 5 or 7 seconds and it restart again the lumia has been stucking in this eternal loop of AT&T LOGO FOLLOWING THE GEARS.
i can prove that i have done everything in the correct way:
1. i have my account in hte windows insider program.
2. i have the app of windows insider.
3. i have leave it download all the night.
4. the smartphone has the full charge.
5. and for credibility: i'm a student of software development.
the big trouble is for the lumia software recovery tool and nokia care suite, with the lumia recovery, i open it in: MY PHONE DOES NOT START OR RESPOND and the software can't recover my phone because i have done a hard reset, flash mode and i still don't know all the combination bottoms to put an end to the loop while it is connected to the pc, while it is without connect it just turn off, it is the same for nokia care.
please someone help this is my only, i know that this is a risk but in the end i was hoping just common errors but THIS!!!.
PS: i live in Panamá there is not a microsoft store, there is not a windows phone expert.
Click to expand...
Click to collapse
Hi, thanks for using XDA assist!
First, please create an account so you can post in other forums.
After creating your account, please post your question here:
http://forum.xda-developers.com/showthread.php?t=2257421
The device experts in that thread will be able to help.
Good luck!
Greetings to all the developers and registered users on this site... Yes, this is my first post, but I read here pretty often and I used the search function, trust me! Seriously, I've tried all I could and I am at my wits end, but this is technology, we can't let it own us, we gotta continue owning it and that's what online communities like xda help us do, so thanks for all your past, present, and future contributions here. So I got this Metro PCS Kyocera Hydro Wave (C6740N) that I can't factory reset for a number of reasons, but mainly because I believe that there is either no boot-loader or no recovery partition as a result of Metro PCS flashing the ROM...
Anyway, lets get to the juice:
- Device powers on/off, but no combo of Vol -/+ and Power buttons bring up a recovery menu or anything (holding any combo down just boot-loops)
- Device has no SIM and no micro SD card, and the battery is not removable
- Device is locked... Like, pattern-locked/google account info/too many attempts/yada yada yada
- Device has no data and no WiFi connection active, so I could not use the google account to get past the lockscreen
- Device does not have USB debugging enabled/Google drivers for ADB do not work (Windows 7 auto-detects when I plug in the phone and installs a generic Microsoft driver which cannot be removed even after uninstalling the device, and also I pointed the Device Manager to the correct Google drivers I installed with the Android SDK Tools, as well as the Samsung Naked Universal Drivers I found on this forum, and Kyocera ADB drivers I found through Google which all failed, Windows returned a message stating that the most up-to-date or best driver for this device is already installed)
What I've tried (everything possible really):
- Hard reset/Recovery from phone: FAILED
- Connect to Linux and install ADB, then tried running the adb shell, adb devices, fastboot devices, etc but phone not detected: FAILED
- Connect to Windows 7 and install ADB (Android SDK Tools), I literally checked every single box and installed Platform-tools, google drivers, everything, got to the command prompt as admin, cd to the ADB directory, ran same commands as in linux, also tried commands on several forums and posts like adb shell rm /data/system/gesture.key to remove the lock but everything: FAILED
- Connect to Windows 7 and attempt to install proper drivers using RootGenius, MoboRobo, PDAnet, and several other suggestions which all were oblivious/unable to detect the device despite Windows recognizing it, so they all: FAILED
- Connect to Windows 7 and attempt running ADB through a Cygwin terminal, but the command "sudo" was not recognized/not valid, so: FAILED
- Connect to Windows 7 and use XRYViewer to extract data from the phone, possibly to see the system files and get an actual understanding of what everybody is saying you need to mount from the recovery partition, but no clue how to use this, since I can't find an XRY file in the internal storage, so: FAILED
- Connect to Windows 7 and access data/recover data from device using "Wondershare Dr.Fone for Android" and "iLike Android Data Recovery Pro" but both programs instructed me to enable USB Debugging, which is not possible, so the both also: FAILED
Despite this being my first post, I have scoured the forums here in addition to every other forum and webpage regarding this issue as well... There just isn't much about this phone except negative reviews, and I have come to the conclusion that on this particular model phone, I am out of options... I have a paperweight... I'm not very familiar with Android... So please correct me if I'm wrong...
Any input?
I'm curious if there are any options at this point, I have been trying to get through to this phone on several computers for the past couple days and it is frustrating me... Any input from the community would be much appreciated...
Mojo2XL, I guess you did not find an answer?
Mojo2XL said:
I'm curious if there are any options at this point, I have been trying to get through to this phone on several computers for the past couple days and it is frustrating me... Any input from the community would be much appreciated...
Click to expand...
Click to collapse
I have the exact same problem and it appears I am several months after your post. I just want to use this device as an e-reader but like you, I cannot get anything to recognize it!~
eenuckols said:
I have the exact same problem and it appears I am several months after your post. I just want to use this device as an e-reader but like you, I cannot get anything to recognize it!~
Click to expand...
Click to collapse
may be this:
*2767*3855# - Think before you give this code. This code is used for factory format. It'll remove all files and settings including the internal memory storage. It'll also reinstall the phone firmware.
I found code in internet, but may be it works? can't check, my "wave" comes to me from USA by post for a few weeks..
barabeka said:
may be this:
*2767*3855# - Think before you give this code. This code is used for factory format. It'll remove all files and settings including the internal memory storage. It'll also reinstall the phone firmware.
I found code in internet, but may be it works? can't check, my "wave" comes to me from USA by post for a few weeks..
Click to expand...
Click to collapse
doesnt work.. you can only get to emergency dialer which can only b used to make emergency calls
elliwigy said:
doesnt work.. you can only get to emergency dialer which can only b used to make emergency calls
Click to expand...
Click to collapse
okay. i will try something, when my phone will come. is your Wave locked?
barabeka said:
okay. i will try something, when my phone will come. is your Wave locked?
Click to expand...
Click to collapse
i bought another phone and they threw it in free but it has a pin code lock so i cant even get to google screen to bypass frp as im stuck at pin lockscreen and these darnphones have no recovery..
i doubt ull figure out a way as im real savvy with this stuff lol theres no recovery to boot into in order to reset and no way to update tje phone wothout knowing the pin code
any luck? i cant believe this thing is this locked down. makes apple look like chils play
warriorpluto said:
any luck? i cant believe this thing is this locked down. makes apple look like chils play
Click to expand...
Click to collapse
i believe it can be done with a pc
Did you happen to get the files the other member posted that was only available for eight days?
Mojo2XL - Sort of.
I saw a youtub video (sorry no link) that says there was a OTA update that changed the phone's firmware that solved all the problems mentioned here. Thing is I have no carrier and cannot find this new firmware, but, I am still hunting....
eenuckols said:
I have the exact same problem and it appears I am several months after your post. I just want to use this device as an e-reader but like you, I cannot get anything to recognize it!~
Click to expand...
Click to collapse
I'm having the same problem, I have been trying to get this thing to hard reset for a week now. There has to be a way to reset this Hydro Wave.. Has anyone dealt with this thing?
Hey hold the buttons as follows volume- & power at the exact same time while your phone is off be warned if you phone was preowned you need the goole account originally activeated with that phone if you do not have that then your in the same vote as me i cant remember any of my gmail account info to my wave from when i had it active I have litterally tried every thing to recover the info and i still can't recover it
WhiteWolf77 said:
Hey hold the buttons as follows volume- & power at the exact same time while your phone is off be warned if you phone was preowned you need the goole account originally activeated with that phone if you do not have that then your in the same vote as me i cant remember any of my gmail account info to my wave from when i had it active I have litterally tried every thing to recover the info and i still can't recover it
Click to expand...
Click to collapse
That doesn't work on this phone the hydro wave from AT&T has factory reset protection so it cannot be reset using the volume down and power button reset
Any update?
dannybz said:
Any update?
Click to expand...
Click to collapse
let me work on this, been trying to master as many FRP bypasses as i can. I don't have the device but a client is in the same boat
I accidentally stumbled upon a something weird. I've managed to make the camera crash to the home screen somehow. I believe this was a result of holding both volume buttons and opening numerous menus while using the camera. My guess is that it overloads it after a certain amount of times and causes it to crash. I've gotten the android UI to crash like this before. I will try to recreate the scenario and update you guys on this. it's on a Kyocera Hydro Wave. Running android 5.0 I believe. Try going wild until the phone starts to lag. eventually stuff will crash and the lock screen may go with it. use this to your advantage and enable USB debugging as quickly as possible because it will reset itself after about 30 seconds. Someone else on YouTube has recently told me that it worked for them. I would look into doing that.
PhoneScrambler said:
I accidentally stumbled upon a something weird. I've managed to make the camera crash to the home screen somehow. I believe this was a result of holding both volume buttons and opening numerous menus while using the camera. My guess is that it overloads it after a certain amount of times and causes it to crash. I've gotten the android UI to crash like this before. I will try to recreate the scenario and update you guys on this. it's on a Kyocera Hydro Wave. Running android 5.0 I believe. Try going wild until the phone starts to lag. eventually stuff will crash and the lock screen may go with it. use this to your advantage and enable USB debugging as quickly as possible because it will reset itself after about 30 seconds. Someone else on YouTube has recently told me that it worked for them. I would look into doing that.
Click to expand...
Click to collapse
Is there anything a little more realistic possible? Lol, I can see an update available, can't connect to WiFi to update haha. The stuff they lock these phones with anymore i swear
I'm new to this forum, but NOT new to this site . I have visited here on numerous occasions seeking the help that needed . With that being said, I would like to offer a Bonafide, Tried and True way to factory reset the Kyocera Hydrowave . I KNOW that this work's for I have done in on numerous occasions for a friend of mine that works for Metro PCS ....
Step One: Completely power off the phone .
Step Two: Hold the Power AND Volume DOWN Buttons SIMULTANEOUSLY .
Step Three: DO NOT release any buttons, even when you get to the Boot Menu . (Very Important, If you don't do it right, you have to start all over lol ) .
Step Four: Once inside the Boot Menu, ONLY release the Power Button; or the Boot Menu will close and you have to start all over again .
Step Five: Use the Volume Down Button to Highlight the Wipe/Factory Reset Option .
Step Six: Use the Power Button to Select the option .
Step Seven: Watch the bottom of the screen for the progress, and then use the Volume Up Button to restart .
And there you have it . I hope that this helps out SOMEONE out there, because I feel good giving back for the help that I have received on here .
PS.( If you would like for me to post a Video Tutorial on this, can someone please tell me how to post the Video; I guess by me being a Newbie on here, I'm not allowed to do as of yet ) . If Anyone needs to contact me, as I'm not on here very often, my email is [email protected] .
LilAnt530 said:
Is there anything a little more realistic possible? Lol, I can see an update available, can't connect to WiFi to update haha. The stuff they lock these phones with anymore i swear
Click to expand...
Click to collapse
As unrealistic as it may sound it actually works Trust me on this. its similar to the LG attack which... is nothing but entering a long password.
betanews.com/2015/09/16/bypass-the-android-lollipop-lockscreen-by-entering-a-really-long-password
Just give it a go. it already worked for one dude on youtube. it takes a while but it honestly works. If you can get it, update the phone as soon as possible turn the screen timeout off and let it update. when the phone resets the update will install and you will be able to factory reset.
I mean it couldn't hurt. if you're locked out with no factory reset and ADB tools won't work what else can you do?