Related
Hello,
My HTC 3300 is blocked on Windows start screen.
I have hard reboot my device and un screen with 3 color appear.
When i plug my device with USB cable, my computer play a song to inform my device is well connected.
But when i launch Artemis USPL, a popup appear with the message : "No Device Connected : Would you like to try copying again ?" Yes, No, Cancel.
I'm blocked a this step.
Can you help me ?
Thx
PS: Sorry for my bad english. I'm french guy.
hi guys,
i have the same problem....
I was trying for the first time to upgrade my Artemis!!! I DIDN'T DO THAT!!!!
Please help me!
TNH
USPL only work if you are in WM. It doesn't work at the booloader.
Zecanilis said:
USPL only work if you are in WM. It doesn't work at the booloader.
Click to expand...
Click to collapse
yes... i know
i am reading.... i am looking for a solution.
I read on the POF USPL guide that probably (Unfortunately ) this problem should be caused by same PDAmobiz tool!!!!
i am being funny!!!
yet another bricked artemis owner
Hi…
Newbie as I am I’ll try to explain to you what you should do...I’ve bricked mine artemis()but I think it is more related to hardware issue. You should try this:
1. Download mtty
2. Disable usb in active sync
3. Bring your Artemis to boot loader(pres start record +start phone+ reset)
4. Start mtty, choose usb and you’ll get popup up screen with direct access to your device.
5. Type this in command line of mtty (NOTE-YOU MYST TYPE IT/NO COPY PASTE WORKS)
Password BsaD5SeoA
6. You’ll get %indicator bar on your phone and then you can switch off mtty(do not disconnect your phone!!!)
7. Just start your ROM upgrade (it has to be factory rom if your phone is locked) and you should be ok.
(You need to have downloaded your original factory rom...For me it was O2 UK...do not start until you have it all)
If it fails, or you get some error massages, repeat all from point 2. Or follow on screen instructions...recovery etc...
If it fails,repeat,repeat,repeat....
Hope it will help you and save you from reading s... load of threads!!
P.S.
I’m still trying to bring mine to life….
zikizile said:
Hi…
Newbie as I am I’ll try to explain to you what you should do...I’ve bricked mine artemis()but I think it is more related to hardware issue. You should try this:
1. Download mtty
2. Disable usb in active sync
3. Bring your Artemis to boot loader(pres start record +start phone+ reset)
4. Start mtty, choose usb and you’ll get popup up screen with direct access to your device.
5. Type this in command line of mtty (NOTE-YOU MYST TYPE IT/NO COPY PASTE WORKS)
Password BsaD5SeoA
6. You’ll get %indicator bar on your phone and then you can switch off mtty(do not disconnect your phone!!!)
7. Just start your ROM upgrade (it has to be factory rom if your phone is locked) and you should be ok.
(You need to have downloaded your original factory rom...For me it was O2 UK...do not start until you have it all)
If it fails, or you get some error massages, repeat all from point 2. Or follow on screen instructions...recovery etc...
If it fails,repeat,repeat,repeat....
Hope it will help you and save you from reading s... load of threads!!
P.S.
I’m still trying to bring mine to life….
Click to expand...
Click to collapse
It solved my problem: I've played around with some dll's on my Artemis and it won't boot anymore.
Just one thing: you must type password BsaD5SeoA, cause it's case sensitive.
THANK YOU VERY MUCH!!!
Hi guys,
i fixed my problem!!!!!
i flashed an official ROM (1.12.405) using a SD card (512mb)
now i'm going to work with ARTEMIS_USPL!!!! WOOOOWWWW
owner of a brick called artemis
glad it helped you solve problem...
when I was young I use to poke with programming...
but that was looooong time ago (remember zx spectrum?48 kb ram..haha)now you got it in your pocket(working if you're lucky guy, not like me)
Any way, point is:
never give up!!!!
Yes, I agree with you: NEVER GIVE UP!!!!
I'd like to help you, i'm not expert people on this work...
I just read a lot of good indications on this forum.
Good Luck
Thanks man,
I'm trying to find another motherboard,before I start playing with this one.
Maybe you know where to get one for artemis?(arte 200)Or someone with broken screen not willing to repair it?
cheers,
z
Hi all!!
Ever since I got my Sprint Vogue, I have spent God only knows how many hours looking for and gathering information regarding this phone (flashing instructions, unlocking, SuperCID, etc). There are a few sites that have fairly comprehensive guides as to how to do this, but there are very few posts in the Vogue Section here at XDA-Developers.
Having said that, I figured I would create my own "How to Flash Your Vogue"-Thread. This is a multi-step process and I cannot emphasize the importance of following every step down to the "T", that is unless you are looking for a silicone-skinned brick...
Who is this guide for?
*Anyone with a CDMA version of the Touch. [highlight]That means no GSM[/highlight]
*Noobs and Seniors alike.
*People who have trouble flashing their devices.
*Anyone looking for links to more information.
*Curious people in general.
*Anyone willing to get rid of the nasty stock rom and looking for a newer and cleaner OS (notice that I never said more stable, so do not blame me afterwards ).
[highlight]Please keep in mind that there is always a chance of bricking your device with these procedures. I will not be in any way, shape, or form responsible if you damage your device while doing this.[/highlight]
Got your coffee? Alright, let's do this.
Step 1. Preparing the device
As with every phone, you have to make sure that you have the following things done before flashing:
* Battery charged at least 50%.
* All the necessary programs (see next post).
* Instructions handy.
Make sure that you back up all your information (contacts, e-mails, files).... essentially, anything that you would like to keep post-flashing. You can do this via Active Sync/Mobile Device Center or via third party software (PIM Backup is really good)...
You will have to reinstall every last piece of software in your device as it will be hard reset. Some programs may work if installed in a SD card directly, but a lot of them write things to the registry and copy files to the device, which they require to run. Long story short, keep all your cabs and exe files in a safe place so you can restore later if needed.
Step 2. Unlocking the Device (HardSPL)
Unlocking the device is done so that you can flash custom roms in your devices. The unlocker that you are about to download and use was provided by "ImCoKeMaN" at PPCGeeks. If you are interested in the full thread, please click here.
If you have read the above link, you will see two versions of the HardSPL (0.40 and 2.31). Simply use 2.31 as it works fine with most devices.
[highlight]To use this under Windows XP,[/highlight]
1. Connect your device to your computer and make sure it is synced with ActiveSync.
2. Download and extract the contents of the zip file, which is an exe. Let it run to completion. You will be prompted to disconnect and reconnect your device at one point in the process. Do it... don't worry
3. It will look like it is flashing a rom via a RUU. Do not disconnect the device after it is done!!!!!
4. Once it is done flashing, you will see a prompt that says that it will run exitbl. DO NOT DISCONNECT YOUR DEVICE. At this point, open ActiveSync, go to File>Connection Settings> Uncheck "Allow USB Connections". Continue following the on screen instructions and let it finish.
5. Go to bootloader once more to verify that it worked. You should see 2.31 CoKe MFG.
[highlight]To use this under Windows Vista/7 x64 (thanks jitajt),[/highlight]
jitajt said:
connect your device to WMDC (it's not necessary to set up device, just connect without setting up device)
then right click on the 2.31 unlocker and run as administrator
follow the directions, you will get an error about sleep.exe not being compatible with x64 but just hit ok and continue, (you will get about 10 of them)
then just keep following the directions in the command prompt and it will put your phone into bootloader then you have to disconnect and reconnect when it tells you to. and it will flash your phone and reset it. then your done you can close the command prompt and disconnect your phone.
I did it just like above and I have not had any problems.
Do this at your own risk as I am not responsible for your phone
Click to expand...
Click to collapse
Step 3. Flashing your Roms
The time has finally arrived. You sat down patiently through the unlocker and you are now ready to take the leap of faith into what you believe will bring your device to a new level of usefulness (also known as getting rid of that nasty, bloated, stock rom )
The process is relatively simple:
1. Download the RUU package from this post. I am only posting this because some cooks only post the rom nbh files rather than the whole package.
2. Go into the threads and look for whichever rom you prefer. Look at my signature to learn which one I am using. NFSFan (my current one) is by far the best one I have tried so far. You can download it from here
3. Put your device in bootloader mode and connect the device to the computer. [highlight]Once in bootloader, activesync will NOT see the device. If the RUU gives a connection error, try to run it with the devices in regular mode (with ActiveSync connected)[/highlight]
4. Open the Romupdateutility.exe and follow the steps.
5. Once it is done flashing the rom, disconnect it from the computer and hard reset it. To do this, simply hold "Send" + "End Call" +Stylus in the reset hole for about 3 seconds. It will prompt you to erase all the data and restore to factory defaults. Press "Enter", which is the center button in the directional pad. Once it is done, press "Send" to reboot.
Congratulations, you just flashed your first rom for Vogue
Step 4. SuperCID
This step can be skipped if you are not thinking of doing anything as far as your radio (such as flashing radios other than the ones intended for Vogue). This is also used to do other things such as modifying certain important things on your device such as the NV files, which is information that will not be discussed here. However, if you are interested in finding out more, simply google it, there is a ton of information out there.
Anyways, back to SuperCID... here is the procedure (thanks to hpnasik at mobile-files.com for the post)
1. Download the following special rom . This is an Alltel rom with radio 3.37. This was specially prepared to be able to reduce the Security Level of the device to level zero.
2. Download mtty since you will need it. Do not worry if you do not how to use it. You will have a step by step in this guide.
3. Flash the Alltel rom from above.
Now comes the fun part...
4. Disable USB in Connection Settings of Active Sync
5. Boot The Phone holding power button and camera button to enter bootloader.
6. Phone Will Display Serial in Bottom
7. Connect Phone to PC
8. Phone should Display USB instead of Serial in Bottom
9. start mtty.exe
10. Select All Default and Connect to USB in drop down box and Shoot the Following Commands (All Commands are case Sensitive)
11. run command rtask a : After this Command Phone will not Display any thing
12. run command echo_on : even though nothing is shown to screen
13. run command readCID : in Sprint it will display SPCS_001
14. run command writeCID 00000000 : Set CID Value to 00000000 replaces SPCS_001 in Sprint (This make PPC Radio Security Level to Zero)
15. run command readCID : This will Display the Update CID as 00000000
16. run Command retuoR : This will return to Original Boot Loader State
Congratulations, you just SuperCIDed your device. Original thread with the instructions can be found here if you are interested.
Step 5. Flashing your radio.
Now that your device has been SuperCIDed, you will have the opportunity to flash radios that have been ported to this device (ie. there is a version of the 3.42.40 radio for the Titan, which has been ported to the Vogue). There are two ways of doing this:
Way 1: Do it by flashing via RUU (same as with flashing a rom)
Way 2: Flash via microSD card. Simply put whichever radio that you wish to flash in the root of a 2GB or less microSD card formatted to fat32. Rename the radio to VOGUIMG.NBH and put your device in bootloader. The flashing will start by itself.
Way 3 (I know I said two ways...): There are a few stock roms that come with new radios. One of them can be downloaded directly from HTC and it is for the Sprint Touch. This one comes with Radio 3.42.30
The other one is for Bell Mobility and this one comes with Radio 3.42.50.
Why am I giving "Way 3" if the other two options seem much easier?? I have run into the problem where my device would not let me flash other radios than the one that I had. SD card method did not work and the RUU started out fine but quits at 8% rebooting my phone and displaying Error 328 in the RUU on the PC. Anyway, here are the links...
Sprint rom with radio 3.42.30
Bell rom with radio 3.42.50
Verizon Stock Rom
All Shipped Roms (All Carriers) - Thanks conflipper!
All Above Radios zipped
The newer radios perform a little better and give out better GPS signal (faster locks)....
Hang on a sec... did you just say GPS?!?!? But my Vogue does not have a GPS.... It does, just read a little further and be happy
Step 6. Enabling GPS, Returning to Stock, and Carrier Cabs
As I said before, there is a GPS hidden on your device. Now, if you are like me and went straight to the specs of the phone to confirm, you will probably try to call BS on this. Long story short, there are a few custom roms which have this "tweak" already implemented (like the one I am using from NFSFan). If you require some more info, I will post it later...
[highlight]Location must be on or else your GPS will not work. To activate it, go to Settings>Personal>Phone and change the Location setting to ON instead of 911 (thanks for pointing it out, th3lolz)[/highlight]
[highlight]For Verizon Users[/highlight]
br125 said:
For those of you with the official mr1 update from verizon that cannot get their gps working:
My xv6900 came with the official update and I got it working, it involves downgrading to a NON-GPS radio, then back to a gps radio...
go here: http://forum.xda-developers.com/showthread.php?t=533639
now the instructions are going to imply that you must load the unlocker before each flash... bs don't worry about that
1. flash the .40 unlocker
2. flash the non-gps rom (reset before customization)
3. flash the 2.31 unlocker
4. flash the vzw rom (reset before customization)
5. flash any custom rom or android rom
that's it, time consuming, but it works
*ignore the multiple flashing instructions, its completely unnecessary, I've never flashed more than once with no problem ever....
I also suggest keeping the vzw radio, but do as you will, I like the 3.37.38 radio.. ain't broke don't fix it
lastly, just make sure you RESET BEFORE THE CUSTOMIZATIONS RUN...... that is what locks your gps.
good luck!
ps. the verizon radio rom that is in that post is for the "leaked" 3.37.37 radio, I reccomend using the official update from verizon here for the 3.37.38 radio rom instead:
http://www.pcdphones.com/phone_downloads.aspx?bid=95&cid=1&mid=302&carrier=Verizon Wireless
RESET BEFORE CUSTOMIZATIONS
Click to expand...
Click to collapse
[highlight]How to Relock you phone[/highlight]
If, for whatever reason you need to return your phone for repair/replacement, you will need to relock it. To relock your phone, simply run the unlocker 0.40 and flash the stock rom of your carrier.
ftp://up.ppcgeeks.com/Vogue/Users/ImCoKeMaN/Vogue_unlocker.exe
[highlight]Carrier Cabs[/highlight]
Thanks to Codybear for gathering all of the cabs with settings for various carriers. But since the link went down, here is another one courtesy of LMiller1708
https://sites.google.com/site/vogueroms/vogue-files
This information was only gathered by me and I take no credit whatsoever other than trying to put it in a one stop thread. Thanks to the following people
Shadowmite
ImCoKeMaN
mindfrost
NFSFAN
Codybear
joshkoss
and a bunch of people that were involved in developing all this...
Thread sticky'd as requested
Peace,
Josh
ok so im a noob n all at this but for some reason when i go to start the Vogue unlocker it tells me to connect my phone, when its already connected. Ive tried everything my even switched to an xp from vista but still no luck. Please help
dwigginstm said:
ok so im a noob n all at this but for some reason when i go to start the Vogue unlocker it tells me to connect my phone, when its already connected. Ive tried everything my even switched to an xp from vista but still no luck. Please help
Click to expand...
Click to collapse
How exciting!! My first victi...erh patient
Did you put the device in bootloader mode? If you did and it is connected to the PC, you should see USB on the screen of your device. Also, do you have ActiveSync on your XP machine? You will need it for the drivers on this step. Changing USB ports sometimes help as well. And one last thing, do not use a USB hub, go directly through the USB ports in your computer. Good luck!
yes i have activesync installed xp, and yes it changes from serial to usb in bootloader mode. But once i connect it to the pc while in bootloader mode my computer recognizes just activesync doesnt, only when its on and not in bootloader mode will activesync recognize it...
yes i have activesync set up with the phone and pc, but when i put the phone in bootloader mode and connect it the pc recognizes it but not activesync. is there another program i can unlock the phone with?
dwigginstm said:
yes i have activesync installed xp, and yes it changes from serial to usb in bootloader mode. But once i connect it to the pc while in bootloader mode my computer recognizes just activesync doesnt, only when its on and not in bootloader mode will activesync recognize it...
Click to expand...
Click to collapse
Do not worry about ActiveSync. While you are in bootloader, the device is not running WM, which is why your computer only sees it as a USB device. This is perfectly fine. ActiveSync will not recognize it.
Please, follow the instructions in my post for unlocking. Read it thoroughly and try to understand it, else you will end up bricking your device.
ok but when i begin the unlocking exe it tell me to connect the device to activesync, althought the only way activesync will notice it is if i take it out of bootmode. your help is appriciated
dwigginstm said:
ok but when i begin the unlocking exe it tell me to connect the device to activesync, althought the only way activesync will notice it is if i take it out of bootmode. your help is appriciated
Click to expand...
Click to collapse
that is a message in the RUU. do not pay attention to it. good luck...
so i finally got the unlocker to start and it begins the ten minute process and stops then show a 262 error code ive done this over and over again
Let's go from the top. I just saw the message that you were talking about. The unlocker does ask for ActiveSync as you pointed out and it is asking you to connect the device to the computer. Then it asks for you to press any key when that is done. So, try that and you should see the word "initializing" with a dotted line getting longer for about 20 seconds. Do that.
The RUU will start up afterwards. The prompt will tell you that it is going to flash a new SPL, and if I am not mistaken that is where you are getting stuck.
Just out of curiosity, which version of the Vogue do you have? (Alltel, Bell, Verizon, Sprint, US Cellular)?
no internet
i just flashes my cell for the first time in with sprint NFSFAN's WM6.5 1.00 FINAL ROM worked great but for some reason my internet doesnt work i downloaded NFSFAN Sprint Provisioning but i dont know how to use it. It has a cople files SPRINT~1.000 and 000DUMMY and setup.xls
thanks in advance
terrancextc said:
i just flashes my cell for the first time in with sprint NFSFAN's WM6.5 1.00 FINAL ROM worked great but for some reason my internet doesnt work i downloaded NFSFAN Sprint Provisioning but i dont know how to use it. It has a cople files SPRINT~1.000 and 000DUMMY and setup.xls
thanks in advance
Click to expand...
Click to collapse
You downloaded a cab. Simply put it in your SD card and run it by tapping on it. Don't unzip it...
Unlocker is not 64 bit compatible... grrr....
Tested on Windows 7:
- start installing HTC Sync, the software which comes with your phone (and can also be downloaded from HTC web site).
- it begins with telling you it needs to install Adobe AIR, something else, and the drivers... let it continue at that stage.
- once the previous step is done and installer asks if you want to start installation of HTC Sync software -- select [Cancel]
This way the drivers needed for adb and fastboot get installed while the rest of the (not so useful) HTC software is not installed at all.
You realize that everyone on this forum knows that, don't you?
qktb said:
Tested on Windows 7:
- start installing HTC Sync, the software which comes with your phone (and can also be downloaded from HTC web site).
- it begins with telling you it needs to install Adobe AIR, something else, and the drivers... let it continue at that stage.
- once the previous step is done and installer asks if you want to start installation of HTC Sync software -- select [Cancel]
This way the drivers needed for adb and fastboot get installed while the rest of the (not so useful) HTC software is not installed at all.
Click to expand...
Click to collapse
actually ur wrong, u need different drivers for fastboot
ADB & Fastboot Guide
abaaaabbbb63 said:
You realize that everyone on this forum knows that, don't you?
Click to expand...
Click to collapse
1. There is a lot of info distributed among lots of guides, signatures, stickies, etc. Probably everything has been discussed and described somewhere some time ago. Maybe I'm slow, but it took me a while to find and figure out what is needed for what. I find short posts with quick and specific answers to specific problems/challenges quite useful.
2. Keep in mind that there are people using Google search who view xda forums in the middle of some long thread with lots of comments, trouble reports, etc. Not registered users. Maybe a short brief description will help someone?
3. I knew about stand-alone driver sets or "install/uninstall HTC Sync" way of installing the drivers, but someone may save some time knowing that it is enough just to cancel the installation after pre-requisites are installed.
Still if you think this thread is useless I will not cry and have no hard feelings if it is deleted.
jmcclue said:
actually ur wrong, u need different drivers for fastboot
Click to expand...
Click to collapse
For me both adb and fastboot work fine with the method described. There was nothing HTC-related installed earlier on the PC, it is a new laptop.
Edit: actually you are right and I am right (I guess): different drivers are needed and used for fastboot operation, but all of them are installed with the process described, no further action is needed when using fastboot later on. Windows just says "Installing drivers..." on the first use.
I am writing this because I couldn't seem to find a guide to solve my issue of my Galaxy Nexus being completely bricked. It was literally dead, or so I thought. The first part of this guide will tell you how to recover from the following situation:
Before we begin, here are the names of the programs and files used:
Odin3
Android ADK
CF-Root-GGN_YAKJU_ICL53F-v5.1
Stock Galaxy Nexus ROM
OMAP
Situation 1:
The first situation is where your screen has gone completely black. You can't boot into anything and nothing is displayed on the screen. Your computer no longer recognises the device. It is literally a brick. If you are in this situation, please follow the solution 1 and 2 else skip to situation 2.
Solution to situation 1:
I was googling everywhere for a solution to this and it appeared that it was not a common problem and those who did face the problem simply returned their phone on warranty. It is now an old phone but I still like it (will be upgrading to nexus 5 in the next few weeks). I didn't want to waste such a good phone and just have it sit there so I researched.
My solution to this problem is omap. I would post a link but unfortunately I do not have the permissions (for the download link I will be uploading later).
Please note that I do not take any credit for any program used in this guide and I am simply putting together several other guides so that future users who have this problem can access them all in one place.
Here is the step by step guide:
1) Open OMAPFlash. Navigate to usb_drv_windows. *Right click on omap_winusb.inf and click install*.
2) Navigate to usb_drv_android. *Right click on android_winusb.inf and click install*.
*Note: On Windows 8 (8.1), you will have to allow all certificates to be installed.
3) Double click on the omap4460_tuna_hs_pro.bat and run it accordingly. You will have to disconnect the device and remove battery. Connect the device and then count to 5. Re-insert the battery.
4)Omap will now start doing its thing and you will be given situation 2.
Situation 2:
This situation is where you have a phone connected to a yellow exclamation mark which is connected to a computer. Mind my ASCII Art, but here is what it looks like: [] - - /_\ - - [ ]. You can't do anything with this either but ODIN (google it) will pick it up. This is a good thing. You won't be able to boot into recovery mode or download mode which makes it hard to flash a ROM to it or fastboot it. You will need CF-Root-GGN_YAKJU_ICL53F-v5.1 (Google it). Here is the step by step guide:
Solution To Situation 2
1) Open ODIN3. Select the CF-Root-GGN_YAKJU_ICL53F-v5.1 as the PDA file. If your phone is not being recognised (should say added! in the log), simply disconnect device, remove battery, reconnect device and then place battery back in and hold down the power + vol up + vol down buttons.
2) Press start. The log will start filling up and it should say DONE! You now have bootloader.
3) Now you will need to find the stock ROM for the galaxy nexus (google it). Now you will need to extract that the contents into your adb file (from the android sdk installation which hopefully you have,
4) Put your device into bootloader mode. Run the fastboot flash-all batch file that should be included with the custom ROM.
5) Your phone will now start doing stuff and constantly rebooting in and out of bootloader mode.
6) You should now have the stock ROM installed.
Again, I am sorry that I cannot post links but I do not have permissions due to lack of posts. I know this is an old phone but this guide may still be useful to someone. Also, feel free to ask any questions or point out any mistakes I have made.
no need that android adk. setup correctly adb & fastboot just enough. i think this type of threads already here..
* yeah.. but no sticky guide. maybe good to go. better make ' how to prevent gnex from bricks'
omap flash.exe ~
http://forum.xda-developers.com/galaxy-nexus/general/bricked-gnex-brought-to-life-t1760787
odin ~
http://forum.xda-developers.com/galaxy-nexus/general/guide-restore-to-stock-unbrick-galaxy-t2065470
I probably already know the answer to this but I want to make sure: can this procedure be applied to the Verizon Toro?
Update: Phone isn't responding to this fix... It was a long shot maybe in a week or two it'll turn on...
I'll write up a tutorial for us Toro kids... Thank you guys!
Sent from my VS980 4G using Tapatalk
There once was a way to install android at
http://kdroid.org/
(Website is permanently down as of September 21, 2022)
this is a fork of a project that began in 2017 and stalled before mid-2019, it had been abandoned for long and it ran an ancient version of android(4.x)
Now, you can install this Android os (although a bit modified) on a Kindle.
It is not recent (released half a year ago) and pretty isolated on the internet.
And I want to bring such a guide to daylight, because I think it deserves attention.
(By the way, this is a work in progress, I apologize for the lengthy delays)
Here is the link:
{Mod edit: Link removed}
(Google drive link is coming)
Bear in mind while the system is very stable, I am not responsible for any issues caused by you using this (obviously uncertified) system
Detailed instructions are available in the attachments section.
Kindle 8 version is based on Android 5.1
All others are based on Android 4.4
I would say battery life is decent but keep in mind to not install resource-gobbling apps e.g. Minecraft or whatever
Supported models:
Kindle 7/Kindle Basic 2 /KT2 ）
Kindle Paperwhite 2 （ Kindle Paperwhite 6 gen）
Kindle Paperwhite 3 （ Kindle Paperwhite 7 gen）
Kindle Voyage
Kindle Oasis 1
Kindle 8 gen/Kindle Basic 3 /KT3
KindleXMigu (China Mobile x migu books domestic version)
Newer models are not supported due to bootloader beig locked. Jailbreaking does not unlock your bootloader, and while Alpine linux or other light distros might run on the kindle by a container, Android would not really work. There will not be any significant development for newer models of the Kindle unlesss there is sufficient demand (from you guys)
For Kindle 7, paperwhite 2, 3(except 32gig Japan version) and voyage you could choose to keep the original Kindle OS
Spoiler: (over)simplified instructions. Please use flash guide below instead if not sure.
First root/jailbreak your Kindle and install KUAL
Install fastboot driver on PC, and disable signature check if needed
The driver name is wrong and should be something like adb setup 1.4.2 with an Android logo
Put main-htmlviewer. tar.gz from the uboot folder into Kual (the names might be different)
In KUAL you will see something like FlashAndroid.
Make sure you have enough battery power in your Kindle, and tap the button.
The Kindle will reboot and enter fastboot mode. The status bar of the Kindle loading will get stuck. Don't worry. Everything is fine here.
Without admin privileges, run start.exe
Enter 8 when a list of weird letters appear.
Your Kindle should now be running Android! Have fun!
Installation Guide Version 2.1 Is now available.
These are the instructions made into videos by the original author.
Oasis1, thisand this
Please let me know if the links are dead.
Extremely sorry for the delay,
Apparently you have to register this app called QQ,
Log in and apply for the forum,
And then download the zip.
Long story short I was too bad at Chinese and they thought I was some sort of troll or child.
However, the owner of the forum DID post a link to a Chinese website called baidu disk (something like that)
With so little memory and storage space, I doubt GMS will even work. However, I encourage you to try to find out!
UPDATE:
the project manager is in touch with me and we are writing and translating an entire comprehensive guide for all models supported. GMS does worl but it would drain battery life so badly it would be useless to even install.
Hello. I can't download the files from Baidu. Can you please link them here, or upload them to Google Drive?
It would be very appreciated. Thank you!
Unfortunately my Google drive is full, and I could not download the baidu disk files myself. This is being sorted out.
you may chat with me to find an alternaltive way if needed
Meanwhile, you can go to this telegram channel to download the files needed:
{Mod edit: Link removed}
(Please do not censor this mods)
Disclaimer: the files on this channel has minor issues, as this project is still is in development.
We need your help!
@Ygjsz and Molly needs help fixing the open source Gralloc so it can refresh the screen in the correct waveform!
Please contact me if you are willing to contribute to this project!
these are all the links for the Android 5.1-based source code, provided by the author, Molly
https://github.com/MollySophia/android_hardware_imx
https://github.com/MollySophia/android_device_amazon_kindle
https://github.com/MollySophia/android_kernel_amazon_kindle
https://github.com/MollySophia/twrp_device_amazon_kindle
https://github.com/MollySophia/imx6_android_u-boot_kindle
Thank you. I'm going to see if I can compile the source.
@Nicknackpaddywack101
I've sanitised the thread from references to Telegram! Regarding social media links please observe that as an exemption from the last bullet of rule no. 5 of the XDA Forum Rules, we grant only developers the privilege to share references to their social media in their own development threads and if thorough support is provided in the thread. These conditions obviously don't apply to your posts, threads or you. Additional information is also available here:
Telegram Chat Channels - Way Forward
WhatsApp/Telegram Groups and Channels - Going Forward Hello XDA family! Just notifying all members that posting certain links to Telegram and other sites like WhatsApp is now allowed on XDA. What does that mean? We will allow links to messages...
forum.xda-developers.com
Additionally, Telegram is not accepted as filehost as a registration is required that violates rule no. 11 of the XDA Forum Rules. Please refrain for sharing of social media references unless within your own development threads and do not drag members away from XDA to social media! Please read my announcement as a friendly warning.
Regards
Oswald Boelcke
Senior Moderator
Nice, evolution, maybe )
oldman20 said:
Nice, evolution, maybe )
Click to expand...
Click to collapse
? Can you explain more?
Nicknackpaddywack101 said:
? Can you explain more?
Click to expand...
Click to collapse
Didnt you success project?
I did not for now.. :/
Trying to flash to a Kindle PW2 6.th gen running 5.12.2.2
Im running windows 11
I ran into a problem after step 2.5:
If the Kindle’s screen flashes and the Kindle restarts, wait until the Kindle loading bar stops
moving.
Your PC should indicate that something is being unplugged and plugged in multiple times.( still In
the loading screen)
DO NOT touch the power button while the Kindle restarts.
Click to expand...
Click to collapse
did so but have the folowing situation:
1- The Kinde starts rebooting and gets mounted for a periode of time. I would be able to copy files to the kindle.
2- Then it unmounts, the boot process goes on and goes to the "USB Drive Mode"
3- The device gets mounted and unmounted (at least windows plays the "plugin- plugout- sounds) in a never endling loop.
When I open de windows device manager Kindle shows up with the exclamation mark. There seems to be no valid driver for the device.
4- After about about a minute the Kindle reboots and runs throug the descibed steps
I guess the device fastboot drivers are not installed correctly.
I will try if intsalling the android sdk chances anything
Any suggestions?
The Kindle has been charged to 100% but im a little afraid, that it may constantly loose power and may die (?) The indicator LED is green while in state 1 and changes to orange while in state 2 and 3. does this mean its beeing charged at any time?
I would be happy for any suggestions
I solved it
i missed to manually add the driver.
after doing so. the bat ran fine. when it told me to do so i longpressed the power button to reboot.
now its running android :]
Thank you for your tutorial. I would suggest to describe the steps a little more detailed to make it noob proof :]
snoerme said:
I solved it
i missed to manually add the driver.
View attachment 5820195
after doing so. the bat ran fine. when it told me to do so i longpressed the power button to reboot.
now its running android :]
Thank you for your tutorial. I would suggest to describe the steps a little more detailed to make it noob proof :]
Click to expand...
Click to collapse
Whats your experience!?
it runs fine, but the possibilitys are very limited for now because i hardly find any any app that can be run.
there are no gapps installed, and im not shure wheter there is something like twrp available for the pw2.
there's a browser, a file manager and an ebook reader preinstalled as well as a launcher with some basic settings. wifi works.
I gave it a try because i was looking for a solution to display a calender that can sync with multiple google accounts. maybe someone can suggest, where to find old android kitkat apps that fit my needs.
forgot to say, that that its rooted with supersu.
i found out that apkmirror lets me filter my search for android versions.
i downloaded some apps and they all seem to work:
catLog
Calculator
Droid Info
Open Gapps app installs and runs fine but toasts "Connection to server failed" after i selected the pico package for 4.4
would have been too easy to believe though ^^
snoerme said:
forgot to say, that that its rooted with supersu.
i found out that apkmirror lets me filter my search for android versions.
i downloaded some apps and they all seem to work:
catLog
Calculator
Droid Info
Open Gapps app installs and runs fine but toasts "Connection to server failed" after i selected the pico package for 4.4
would have been too easy to believe though ^^
Click to expand...
Click to collapse
Sadly my device is Kindle Oasis 2, which not support
snoerme said:
forgot to say, that that its rooted with supersu.
i found out that apkmirror lets me filter my search for android versions.
i downloaded some apps and they all seem to work:
catLog
Calculator
Droid Info
Open Gapps app installs and runs fine but toasts "Connection to server failed" after i selected the pico package for 4.4
would have been too easy to believe though ^^
Click to expand...
Click to collapse
I guess it will also use TWRP recovery to install it. (because it's only supported one)
If this can run. It will not work.
Install GApps Manually
groups.google.com
I find this tutorial work, but it requires some workaround.
"adb root" will not work. You will need "adb shell" to remount /system.
After copied you will need to fix copied file permission.
/system don't have enough disk for pico. You will need to remove something.
In my case, its PW2. I don't think it has enough ram to run it.
snoerme said:
I solved it
i missed to manually add the driver.
View attachment 5820195
after doing so. the bat ran fine. when it told me to do so i longpressed the power button to reboot.
now its running android :]
Thank you for your tutorial. I would suggest to describe the steps a little more detailed to make it noob proof :]
Click to expand...
Click to collapse
There is a detailed tutorial in the attachments section. Thanks for letting me know and I will update the post.