[GUIDE]: Android-IA on Surface Pro (with WiFi support) - Android General

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

Related

[Q] windows 8 jailbreak fail

My work just purchased window 8 RT tablets for us. (ASUS TF600T). I tried to jailbreak the tablet using the tool on this site. when I run the tool, it asks me to push the volume down button, the tablet says it detected an error and needs to restart. Sorry, no error code. Id like to able to install some small programs, like keepass, end eventually even a full version of office if it becomes available. Anyone know why it keeps failing and what I can do to jailbreak this thing.
try posting the the windows 8 section of the forum, they probably have tutorials for jailbreaking windows rt
http://forum.xda-developers.com/forumdisplay.php?f=1286
click thanks on the bottom part of the post if helped
Make sure it's got all of the updates installed. I have the same device - once all of the updates were installed on it, the worst I've found is that I have to wait for the system to settle (open Task Manager, wait until most of the usage is by Task Manager itself and not the system, about a minute) before the jailbreak will work, but then it works every time.
Most of the reason for failure that I've seen after startup looks to be because the kernel location that the jailbreak is tweaking isn't at the right location (which is why you need to be fully patched), though it will fail all the time if its done too soon after startup.
Meratiogerr said:
My work just purchased window 8 RT tablets for us. (ASUS TF600T). I tried to jailbreak the tablet using the tool on this site. when I run the tool, it asks me to push the volume down button, the tablet says it detected an error and needs to restart. Sorry, no error code. Id like to able to install some small programs, like keepass, end eventually even a full version of office if it becomes available. Anyone know why it keeps failing and what I can do to jailbreak this thing.
Click to expand...
Click to collapse
irony_delerium said:
Make sure it's got all of the updates installed. I have the same device - once all of the updates were installed on it, the worst I've found is that I have to wait for the system to settle (open Task Manager, wait until most of the usage is by Task Manager itself and not the system, about a minute) before the jailbreak will work, but then it works every time.
Most of the reason for failure that I've seen after startup looks to be because the kernel location that the jailbreak is tweaking isn't at the right location (which is why you need to be fully patched), though it will fail all the time if its done too soon after startup.
Click to expand...
Click to collapse
I did updates as soon as I took it out of the box. apparently it missed a couple, so I had to do It again. worked after all of the updates had been done. Unfortunately more research and it doesn't look like I'm ever going to be able to load access on this thing, which for my work makes it pretty much useless.
Hi
I have a samsung ativ tab.
I ended up downloading all the versions of the RT Jailbreak tool but still haven't succeeded to jailbreak windows RT on my Samsung Ativ Tab.
Any idea what could be the problem?
When I press volume down, it crashes and displays the blue screen with the REFERENCE_BY_POINTER error.
I installed all the updates, gave it about one to two minutes each time I ran it but still couldn't jailbreak.
any idea?
irony_delerium said:
Make sure it's got all of the updates installed. I have the same device - once all of the updates were installed on it, the worst I've found is that I have to wait for the system to settle (open Task Manager, wait until most of the usage is by Task Manager itself and not the system, about a minute) before the jailbreak will work, but then it works every time.
Most of the reason for failure that I've seen after startup looks to be because the kernel location that the jailbreak is tweaking isn't at the right location (which is why you need to be fully patched), though it will fail all the time if its done too soon after startup.
Click to expand...
Click to collapse
crackero said:
Hi
I have a samsung ativ tab.
I ended up downloading all the versions of the RT Jailbreak tool but still haven't succeeded to jailbreak windows RT on my Samsung Ativ Tab.
Any idea what could be the problem?
When I press volume down, it crashes and displays the blue screen with the REFERENCE_BY_POINTER error.
I installed all the updates, gave it about one to two minutes each time I ran it but still couldn't jailbreak.
any idea?
Click to expand...
Click to collapse
I can't get mine to go either. No matter how long I wait after boot. no matter how little resources are using the cpu/ram. I've tried different versions. I've tried different download links. but all I get is a registry key error and it saying I didn't wait the 2 minutes even if I waited 30 min. ASUS TF600T Win8.1 RT.
If ANYONE has any idea. I would greatly appreciate the help.
EDIT: Just realized the pics are blurry. The error syas "ERROR: The system was unable to find the specified registry key or value. Waiting for uptime to reach two minutes." (This was after waiting 10 minutes)

have .fw but need .IMG any ideas?

Long story short.
AGPTEK 718JQ quad core IPS screen, runs like a champ
or did
its my msons, and last night he turns it on and i havve the android robot on his back with his door open.
Som Im thinking corrupted OS
Ive flashed more than my fair share of tablets, but this ones giving me fits/
The maker: http://www.agptek.com/support/download.html has a manual drivers and FW
only problem is all my pcs are either linux or Win7 and theres a known issue w/ WIN7, mostly the driver wont start to allow their tool to connect to the tablet, even if i manually set it up.
Have considered trying to boot WinXP from a USB and trying that, but before I go that route, seems to me as though there should be a method whereby I could convert the .FW files to a .IMG file write it to a micro SD and reboot the tablet/.
anyone w/ any ideas they are deeply appreciated
thanks
j

[HELP] Cannot factory reset a Kyocera Hydro Wave (C6740N) on Metro PCS

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?

[Completed] e-Reader Pandigital Novel Black / Model R70E200 -- sh does not run due libs problem

Hello,
I have "Pandigital Novel Black / Model R70E200 / which supposedly runs Android 1.5" which went through SD card update which did not finished correctly.
My knowledge is limited at this moment about android internals but I am coming from PC Linux world which could help in resolution of following situation.
Yesterday I decided to read some documentation on the e-Reader but found that touch screen did not respond (buttons and orientation worked fine). I did attempted to restart the e-Reader a few times but without any success -- touch screen did not respond (the e-Reader was not used for prolonged period of time).
And it seems that by accident I "hit" a combination of buttons which supposedly initiated some unknown process at boot time. After this incident I had no option as to attempt to re-flash firmware.
For some inexplicable reason the flash process did not went as I would expect. Now it does not matter what I do process verification of firmware never ends.
I've attempted to get into "hard reset" but no success so far -- I always end up in re-flash situation.
To get at least some information for debugging of the situation I installed "adb" and was able to retrieve a log message which states following
link_image[1714]: 1760 could not load needed library 'libm.so' for '/system/bin
/sh' (link_image[1703]: 1760 missing essential tables)CANNOT LINK EXECUTABLE
and similar message about libstdc++
These two messages could explain why re-flash never ends -- I am not sure what happened but some libraries or damaged or missing and I am not able to get "sh" run.
I was able to pull "sh" binary on my computer but in Linux "ldd" could not "decipher" location of missing libraries so that I could attempt to push them in proper location in the e-Reader.
I would be happy to hear any suggestions how the situation can be corrected.
I still keep some hope that the situation can be corrected as "RDU" is still running and e-Reader still "has some breath in it".
RDU Version 2.8.9a (current boot count: 0)
Firmware version S6410_PPP2_BBB_2010_11_18
At normal boot the e-Reader has following behavior:
1. Please be patient while system starts
2. On the screen "Pandigital novel image with Contains Reader(R) Mobile Technology by Adobe System Incorporated" strangely shifted about 1/5 of the screen toward right side
It is quite difficult to establish a connection between adb and e-Reader.
Thank you,
Andromeda
andromeda_2010 said:
Hello,
I have "Pandigital Novel Black / Model R70E200 / which supposedly runs Android 1.5" which went through SD card update which did not finished correctly.
My knowledge is limited at this moment about android internals but I am coming from PC Linux world which could help in resolution of following situation.
Yesterday I decided to read some documentation on the e-Reader but found that touch screen did not respond (buttons and orientation worked fine). I did attempted to restart the e-Reader a few times but without any success -- touch screen did not respond (the e-Reader was not used for prolonged period of time).
And it seems that by accident I "hit" a combination of buttons which supposedly initiated some unknown process at boot time. After this incident I had no option as to attempt to re-flash firmware.
For some inexplicable reason the flash process did not went as I would expect. Now it does not matter what I do process verification of firmware never ends.
I've attempted to get into "hard reset" but no success so far -- I always end up in re-flash situation.
To get at least some information for debugging of the situation I installed "adb" and was able to retrieve a log message which states following
link_image[1714]: 1760 could not load needed library 'libm.so' for '/system/bin
/sh' (link_image[1703]: 1760 missing essential tables)CANNOT LINK EXECUTABLE
and similar message about libstdc++
These two messages could explain why re-flash never ends -- I am not sure what happened but some libraries or damaged or missing and I am not able to get "sh" run.
I was able to pull "sh" binary on my computer but in Linux "ldd" could not "decipher" location of missing libraries so that I could attempt to push them in proper location in the e-Reader.
I would be happy to hear any suggestions how the situation can be corrected.
I still keep some hope that the situation can be corrected as "RDU" is still running and e-Reader still "has some breath in it".
RDU Version 2.8.9a (current boot count: 0)
Firmware version S6410_PPP2_BBB_2010_11_18
At normal boot the e-Reader has following behavior:
1. Please be patient while system starts
2. On the screen "Pandigital novel image with Contains Reader(R) Mobile Technology by Adobe System Incorporated" strangely shifted about 1/5 of the screen toward right side
It is quite difficult to establish a connection between adb and e-Reader.
Thank you,
Andromeda
Click to expand...
Click to collapse
Hello,
Thanks for using XDA Assist.
There's no dedicated forum for your device here in XDA.You can post your query in Android Q&A,Help and Troubleshooting.Experts there may be able to help you
___
v7
XDA Assist

Nokia 1020 - Pulling my hair out doing recovery

HI everyone,
I'm tearing my hair out a little bit on this one.
Before people ask, I'm aware that Windows Mobile is effectively dead. I have no intention of using this device as an actual phone. I just want to try and use the camera in the phone with the app it was intended to use with.
I have picked up a Lumia 1020. On booting the phone, it seemed to be running a build of Windows Mobile 8.1. It seemed to be missing the full Nokia 1020 Camera app these phones were known for, having instead just the default Windows 8.1 camera app. Of note, a Telstra logo (being an Australian telco) was displayed on startup. I am unsure whether this is just branding or whether Telstra were able to get a custom version of the OS done for this device.
I was thinking the easiest solution is to try and reflash the original operating system that came with the device. This should restore all the original apps the phone came with, including the camera app I intend to use. I am absolutely tearing my hair out trying to get it to work.
The WIndows Device Recovery Tool detects the device and, while it complains that a reflash would install an older build of Windows, it does indeed download a copy and then begins the process. It starts to do the initial reboot, I would presume to put the phone into flash mode, and then gives me the error "The operation ended in failure".
I have obtained a copy of the WPInternals tool, which was a common alternative to do this, as well as a copy of the firmware for the device. This attempts to reboot the phone, and then fails with "Failed to reboot into flash mode".
I know it is a bit of a stretch to get this old phone working, however I do like the camera in it, and all I really want is to flash it with the original apps so I can get the proper camera app - the default Windows Mobile 8.1 just does not give me the full options. I'm not sure whether the fact that this has been branded by Telstra has anything to do with it, but if anyone has stumbled across something like this before and can offer any useful morsels of information, it would be appreciated.
Hi,
sorry for the late reply...
Search for thor2.exe on your computer, it is part of Windows Device Recovery Tool.
Have your Lumia ready, connect the USB cable only to your computer, open a command line window and change into the directory you found thor2.exe in.
Type
thor2 -mode rnd -uefitests -skip_com_scan
and connect your Lumia immediately. Normally thor2 detects it and brings it to the red flash screen. Eventually you will have to repeat this input (press the arrow-up key).
If you need to reset the Lumia ("pull battery"), press and hold the volume-down key and press the switch-on key until it comes to live again.
Hope that helps.
Best regards, Joachim

Categories

Resources