Develop Bugs

*Assistance aka, HELP* Android HTC TYTNII Kaiser - polymod_2.1 (Tattoo)

Hi there,
For those who take the time to read through this,
I'm a HTC TYTNII (Kaiser) user, and I have just installed Android on my phone's SD card (2gb, unpartitioned) and I boot it using HARET.exe
It works and I can do the usual and send sms'es and calendar stuff and web and market. And, as expected, it is somewhat slow in some areas.
The problem is, my mic doesn't work during calls. The camera doesn't work, the pictures are green data lines (what?what?) The mp3 player or media player doesn't work. The only time sound does work is during a call, but even then only on my side (receiver doesn't hear anything). And I am just about figuring out how the keys around/on the D-Pad work. (greenphone is Phone, redphone is power, left/right is volume, ok is back, windowskey is something like a options key, internet explorer is also a options key, etc.)
- -
So, Can aybody help me with this:
Mic problems (not working. calls or recording)
D-Pad Keys problems (don't know what they are)
Camera Problems (not taking pictures, just green data)
No file explorer to install apps. (how to upload apps on sdcard or from market)
Market browsing works, but cant download. (just says 'starting download' forever)
Can't brows SDCard (or any files for that matter)
Music can't play. (media player with slide album cover stuff, no play)
Can somebody please post up a definite link or site, where I can get working stable Kaiser Android (TYTNII) install files. (nothing fancy like themed or modified with grafiti or windows mobile features, simple Android 2.2)

*Tail
PS, not sure about the Radio, or whatever. I have "Radio Version: 1.27.15.32"
Does it need updating or new files? What does it effect?

ehhh.... read the forum.... READ
here You have 'how to'.. http://forum.xda-developers.com/showthread.php?t=680518
here NBH file (as You know, without this You can't install Android rom...) http://forum.xda-developers.com/showthread.php?t=660158
here is stable Android 2.1 I recommend http://forum.xda-developers.com/showthread.php?t=688880
Radio must be 1.70.18.02 or 1.70.19.09 ...
polymod_2.1 is Enclair Android, not Tattoo.

Thanks!
Yeah, about reading... I get very frustrated when I go through 50 pages of forum, and end up having 6 pages, all about the same thing, but with different file versions. Then I'm unsure of what to do.
Thanks again, I'll try these

You can also check out my thread in this forum (can't link it due to new user restrictions) which at the time of this posting is 5th from the stickies in the index.
I had various issues with my eclair (incubus's) and it was solved by upgrading using the official WM6.1 release, which upgraded my radio. Upping to the most recent radio (1.7x...) didn't help.
Also a point of order: all eclair builds have non-functional cameras and most have bluetooth issues (some can be fixed with patches). If you need a working camera and BT, you might want to try Myn's Warm Donut which is older but is also stable... And slow.
Incubus's Super Eclair is the fastest I have tried so far though it is buggy on my kaiser.
HTC_TYTNII_KAISER said:
Hi there,
Mic problems (not working. calls or recording)
D-Pad Keys problems (don't know what they are)
Camera Problems (not taking pictures, just green data)
No file explorer to install apps. (how to upload apps on sdcard or from market)
Market browsing works, but cant download. (just says 'starting download' forever)
Can't brows SDCard (or any files for that matter)
Music can't play. (media player with slide album cover stuff, no play)
Can somebody please post up a definite link or site, where I can get working stable Kaiser Android (TYTNII) install files. (nothing fancy like themed or modified with grafiti or windows mobile features, simple Android 2.2)
Click to expand...
Click to collapse
- Mine didn't either. Might have been fixed with the radio upgrade though I haven't checked it.
- Mine work fine... Can you explain a little more?
- Universal to eclair builds, fall back to donut if this is a deal-breaker.
- You need to get yourself one since android doesn't come with a free, standard. Search for "andexplorer" on your phone's browser and install it directly from the web, then you can grab all the packages you want and manually install them.
- Does your other wifi work?
- Andexplorer.
- Likely need a radio upgrade
Redundant, but hopefully it helps more than "go do some searching" or "go read through this 300 page thread".

Mr fosi refers to this thread : http://forum.xda-developers.com/showthread.php?t=690693&page=2
You will have to upgrade your radio, from experience on the forum I can tell you that anything lower than version 1.65.x.x will almost certainly cause a number of problems.
You will also have issues if running winmo 6.0, if you are using haret, you should go get at least a stock ROM that is winmo 6.1 and radio 1.65.x.x, yes you will lose all your data if you flash a new rom, so back up anything you really cannot live without.
And at the moment the highest version of Android available for kaiser is 2.1, 2.2 will take a little time to get to us here

again,
Thank you all,
You have been most helpful.
Up till now, I have been trying to find ways to refrain from overwriting WinMobile. (not that I prefer it, it's just I have a butload of stuff on it, and I dnt want to lose them)
@ mazz8y
Thanks for the innitial help
@ mr_fosi
Very helpfull, thanks!
@ zenity
Thank you too. But do you think it's better to overwrite? Or SDcard method?
PS, What can be used to backup everything of my current phone system? (WinMobile, calendar, contacts, messages, etc.)
I have diffuculty connecting my TYTNII to my pc via usb cable. Software related?

HTC_TYTNII_KAISER said:
Thank you all,
Up till now, I have been trying to find ways to refrain from overwriting WinMobile. (not that I prefer it, it's just I have a butload of stuff on it, and I dnt want to lose them)
Click to expand...
Click to collapse
Same as me. Plus, I do stuff for free on windows that I can't currently do for free under android... Like read my .txt and .doc books, play .wmv files, open and edit .xls files.... Etc.
HTC_TYTNII_KAISER said:
Thank you all,@ mr_fosi
Very helpfull, thanks!
Click to expand...
Click to collapse
No probs. Best way yo pay back is to pay forward.
HTC_TYTNII_KAISER said:
Thank you all,
@ zenity
Thank you too. But do you think it's better to overwrite? Or SDcard method?
Click to expand...
Click to collapse
I know this wasn't addressed to me but I'll weigh in: SD is great for versatility or "trying things out" but it isn't so good for speed or battery life. Replacing windows isn't a huge deal since you can put it right back but once you flash it off, you're somewhat committed to the android model.
Personally, I don't see going straight android right now b/c it would cost me an arm and a leg to buy apps to do what I already do on windows for free. Even then I wouldn't cover everything, just the most critical issues.
HTC_TYTNII_KAISER said:
Thank you all,
PS, What can be used to backup everything of my current phone system? (WinMobile, calendar, contacts, messages, etc.)
I have diffuculty connecting my TYTNII to my pc via usb cable. Software related?
Click to expand...
Click to collapse
Dunno about soft/hardware but the best thing to use might be PIM backup, which you can find with a quick search. I'd link it, but I can't. I don't actually use my kaiser as a phone but rather as a PDA/mobile PC so I can't help you with phone-related data. I generally use the Windows Mobile Device Center to keep all my contact, calender, notes, etc. data synced then keep everything else (like backups of installed software) on my SD. You can sync without a cable if you do it via BT. I bought a $0.25 (free shipping!) Hong Kong BT adapter for my lappy and it works great.

HTC_TYTNII_KAISER said:
@ zenity
Thank you too. But do you think it's better to overwrite? Or SDcard method?
Click to expand...
Click to collapse
If you refer to running Android, I'd recommend SD card method at first, that way you learn to install and use android with the safety net of Winmo available if things go wrong.
Haret is slower, but safer.
HTC_TYTNII_KAISER said:
PS, What can be used to backup everything of my current phone system? (WinMobile, calendar, contacts, messages, etc.)
I have diffuculty connecting my TYTNII to my pc via usb cable. Software related?
Click to expand...
Click to collapse
I have used SPB Backup a number of times for this, it will back up pretty much everything, and can backup to SD card.

zenity said:
Haret is slower, but safer.
Click to expand...
Click to collapse
It depends on what build you use (I never saw a difference, difficult to measure).

Hey, I'm gonna do this now:
"Ok that's one old radio, go here : cant link, get the 1.71.09.01 linked at the bottom of post #3, it's an nbh file, so just rename it to KAISimg.nbh, put it on SD and flash the same as the Nand nbh, it will not affect anything, just upgrades the radio."
But,
Are you refering to
can;t link page
post num #1
"Quote:Originally Posted by kletiz
I can't seem to get past step 5. I'm holding down Power and Camera at the same time and then briefly pressing the reset button. All it does it goes to the bootloader screen and then resets. Any suggestions? Its probably something simple...
Make sure your SD card is formatted FAT32, and that the NBH file is named KAISimg.nbh, and that it is on SD root, not in a folder."
When used for just updating/adding a new Radio (1.71.09.01),
Is it neccisarry to do the whole "NBH Editor" thing? Or can I just throw it in the SD root and then power+cam stylus tap reset flash thing.
So should I go from step 1 to 5 or what?
Sorry if I'm being a real bother, but I can't risk bricking my phone. I have no backup phone to use, or way of keeping contacts and calendar things.
EDIT: I have now! saw the references in your posts!

HTC_TYTNII_KAISER said:
Hey, I'm gonna do this now:
"Ok that's one old radio, go here : cant link, get the 1.71.09.01 linked at the bottom of post #3, it's an nbh file, so just rename it to KAISimg.nbh, put it on SD and flash the same as the Nand nbh, it will not affect anything, just upgrades the radio."
Click to expand...
Click to collapse
Respectfully, I wouldn't do that. Read further down the thread and you will see that a less-new radio may work better, unless you are already using WM6.1.
HTC_TYTNII_KAISER said:
Hey, I'm gonna do this now:
"Quote:Originally Posted by kletiz
When used for just updating/adding a new Radio (1.71.09.01),
Is it neccisarry to do the whole "NBH Editor" thing? Or can I just throw it in the SD root and then power+cam stylus tap reset flash thing.
Click to expand...
Click to collapse
Just throwing it (properly named) into the root of the SD, then booting to bootloader worked perfectly for me. Try the simple before the complex.
The radio update won't brick it, but it may change the behavior of the audio systems. Worse comes to worse and you'll need to go back to your old radio, which you can d/l beforehand if you are worried.
Be sure you put on a HardSPL before you try upping the radio. I used the prog and SPL found here in the zipfile in the OP: forum.xda-developers.com/showthread.php?t=334679 to put on (removed the http to get around the link restrictions).
Before you do any of this, boot into the bootloader mode: phone is off, press and hold the power and camera buttons resulting in the tricolor screen. Once there, report the version and whatnot displayed at the top left of the screen.

Ok I'm assuming you managed to flash a new radio, however I do think you'll also have to upgrade winmo to 6.1, which will mean backing up everything and reflashing with a stock ROM.
Best to get one from here : http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs, I'd get the HTC WM6.1 ROM at the top of the page, not the AT&T one, ( nothing against AT&T just prefer the HTC one and it has a 1.70 radio ).
Get a hold of SPB Backup from somewhere, backup everything you need to SD card, then you should be able to upgrade using the same method as the radio upgrade, that is rename RUU_Signed.nbh to KAISimg.nbh and put it on SD card.
You should not need HardSPL to flash Stock ROMS, however it is a good idea to get HardSPL anyway, you'll need it for flashing the Android NBH if you decide to go Nand.

zenity said:
... I'd get the HTC WM6.1 ROM at the top of the page, not the AT&T one, ( nothing against AT&T just prefer the HTC one and it has a 1.70 radio ).
Click to expand...
Click to collapse
I didn't know that... But then wouldn't he/I need the keyboard fix? Plus, that radio didn't fix the android audio on my device.
zenity said:
... then you should be able to upgrade using the same method as the radio upgrade, that is rename RUU_Signed.nbh to KAISimg.nbh and put it on SD card.
Click to expand...
Click to collapse
So you can upgrade ROMs, not just radios that way? Good to know.
zenity said:
You should not need HardSPL to flash Stock ROMS, however it is a good idea to get HardSPL anyway, you'll need it for flashing the Android NBH if you decide to go Nand.
Click to expand...
Click to collapse
It's also needed if he wants to try any cooked WM ROMs, ja?
zenity: Have you tried any of the WM6.5 kaiser ROMs? Is there any real reason to try any of the cooked WM6.1 ROMs in your opinion?
I rather like the base 6.1 and I don't use any phone features so it seems like there isn't much reason to use any cooked 6.1 ROMs.

@ mr Fosi
Kay, I tried the cam+powa keys thing, and I see the TriCol Gradient for a slpit second, then it flicks to a white screen with the small blue words "loading..." Then it stays there, nothing further... That's bad right? What's up
I just checked, I have:
Windows Mobile(R) 6 Professional
CE OS 5.2.1620 (Build 18125.0.4.2)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Not my pic, just close to this)
Ok, total safety n00b here,
So how exactly do I update the Radio, step by step?
I've WinMo 6 Pro (Build 18125.0.4.2) and downloaded Radio "KAIS_Radinly_1.70.19.09.zip"
Whats next? (And what of white screen blue text loading thing?)

HTC_TYTNII_KAISER said:
@ mr Fosi
Kay, I tried the cam+powa keys thing, and I see the TriCol Gradient for a slpit second, then it flicks to a white screen with the small blue words "loading..." Then it stays there, nothing further... That's bad right? What's up
Whats next? (And what of white screen blue text loading thing?)
Click to expand...
Click to collapse
Make sure your SD Card is formatted to FAT32. SDCard on FAT16 has been the reason behind flashing problems for some.

xPreSiDenT said:
Make sure your SD Card is formatted to FAT32. SDCard on FAT16 has been the reason behind flashing problems for some.
Click to expand...
Click to collapse
Hey, my SD is formatted FAT32, (lol, didn't know FAT16 was still in use)
It just stops at loading..., what is the average time it stops?

HTC_TYTNII_KAISER said:
@ mr Fosi
Kay, I tried the cam+powa keys thing, and I see the TriCol Gradient for a slpit second, then it flicks to a white screen with the small blue words "loading..." Then it stays there, nothing further... That's bad right? What's up
Click to expand...
Click to collapse
You were trying to update your radio only, yes? This is exactly what happened to me when I tried installing the 1.70 radio without first installing a HardSPL. It won't cause any damage to your phone (as I am sure you have discovered) but the stock SPL won't let you upgrade the radio in this way.
Instead, either install a HardSPL such as the one on thread I pseudo-linked in post #12 or grab an official AT&T WM6.1 update and apply it. The official update won't give you the 1.70 radio but it will give you (what in my opinion is) the next best thing: radio 1.65.21.18. I suggest you try the official update first, since the 1.70 radio broke the audio in WM6 and didn't fix the audio in android on my Tilt.
I found a list of official AT&T Tilt/Kaiser roms here: wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs. I am using ver. 3.57.502.2 right now and I am very happy with it. It's nicer than the stock WM6.0 and the new radio fixed the audio and some of the settings crashes in Android.
HTC_TYTNII_KAISER said:
Ok, total safety n00b here,
So how exactly do I update the Radio, step by step?
I've WinMo 6 Pro (Build 18125.0.4.2) and downloaded Radio "KAIS_Radinly_1.70.19.09.zip"
Whats next? (And what of white screen blue text loading thing?)
Click to expand...
Click to collapse
I am also a bit skittish about bricking my device and I am a fan of keeping things simple, so may I suggest you do what I did? Grab the official WM6.1 v. 3.57.502.2 and install it. Forget the HardSPL for now, forget the radio-only upgrade. If you decide you want to replace windows later or want to use some cooked WM ROMs, you can worry about HardSPL then. Just apply the official WM6.1 update and see if it does what you need.
The step-by-step procedure is easy, though you should fix your USB connectivity issues:
- Pull out the SD & SIM cards.
- Connect your Tilt to a PC and allow Activesync/WM Device Center to connect and fully sync it.
- Once the connection is idle (syncing all done), run (on the PC) the "RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.18_Ship.exe" that you d/l from that list of official releases.
- Follow the on-screen instructions.
- Once your device is done being flashed, it resets itself then boots into WM and arrives at the "Tap screen to setup your device", do a hard reset.
- Let it reboot and do the setup.
- As soon as you get past the calender primer and the "setup password" dialog, you will see the home screen for an instant before a dialog pops up and says "setting up your device in 3 sec". Before that 3-sec dialog pops up, do a soft reset. This will keep the AT&T bloatware from installing. If you miss the window, the soft reset will be have like a hard reset and you'll go through the setup again. Just make sure you hit it before that 3-sec dialog box pops up. If you want that AT&T stuff, let it go without the soft reset.
- All done! Go ahead and pop your SD card back in and copy back all the stuff you backed up before the update.
A few questions for you:
- What version of windows are you using on your PC?
- What connectivity software are you using on the PC-end?
- Can you describe the USB connectivity issues you are having?

Apologies people, have not had time to sit down and experiment with my phone, real life caught up with me again. Sorry,
mr_fosi said:
A few questions for you:
- What version of windows are you using on your PC?
- What connectivity software are you using on the PC-end?
- Can you describe the USB connectivity issues you are having?
Click to expand...
Click to collapse
I'm using Windows XP pro SP2
Connectivity software? That's a laugh... I got 2 discs with my tytn2, a HTC/WinMo Getting Started disc and a Application disc (which only has Sprite backup and Spb GPRS Monitor) No Htc phone kit or anything or activesynch whatever.
The only connection problem I have is the normal USB cable to the small (htc style) cable connection. But that could be coz of the software
Hope this info helps

[Q] Who provides a professional service to upgrade my Kaiser

Hey all,
I own an unlocked ATT Tilt 1 (Kaiser 8925). It is currently running windows mobile which is extremely slow. I have read all over the internet that you can put the Android 2.2 OS on this phone and have seen youtube videos on this topic also.
Ideally I need to be able to buy apps from the android marketplace.
Since I'm not a phone hacker I'd like to find a professional cel phone service company that can do this for me.
I searched extensively on Google and can't seem to find one. So who can do this and what is the normal charge for something like this.
Just trying make my old phone useful in wifi mode.
Any advice would be great.
Regards Henry

I don't think there is a company that provides such a service especially if we take in to account that kaiser/tilt is a 3 year old device and the android port is not official. There are plenty of topics in the forum describing how to replace winmo with Android. You don't have to be a hacker to run Android on your phone. Just read the stickies and you wil be able to flash ityourself in no time

There are phone dealers out there (in the USA anyway), that will do this for a fee on the Kaiser, but trust me, with what has gone into the development of this, almost anyone can do it. Save yourself the money and try it yourself. The worst I've heard about is a mis-flashed phone needing some master reset.

The question is who?
I live here in the Orlando area and have called a number of cel phone companies.
I was treated like King Gidorah Three Headed Space Monster. They didn't have a clue this could be done.

Henrykjr said:
I live here in the Orlando area and have called a number of cel phone companies.
I was treated like King Gidorah Three Headed Space Monster. They didn't have a clue this could be done.
Click to expand...
Click to collapse
Listen HenrykJR there are about dozens of android builds on this forum + many different versions of two kernels, not all of those will work correctly for you. You might experience different issues with one setup but the other will work correctly for you. So even if there was a company that could flash it for you, you might end up with an unstable device. Also how could a company gain knowledge on flashing android builds to a phone that was originally shipped with windows mobile??? You seem to be looking for Nessy....in woods.
Your best bet now is to find someone in the forums to help you flash your device....maybe even use skype to show you how to do it. It really isn't that hard.

Hehe, i don´t think you´ll find a Company that will do it for you. Maybe you find some guys that do it for Money (me to ). But if you spend a little time with reading through this forum you could do it yourself and save the money.
Preparing:
1.) You need a SD card (mandatory for android on Kaiser). And you need a Google Mail Account for syncing your contacts etc. and access the android market.
2.) You have to "unlock" your Phone (with HSPL/HardSPL). Only after that you are able to flash things (Cusom WinMo ROMs, Radio, Android) to your Kaiser. So read through this guide and follow step 1-4.
3.) Now you have an unlocked phone an you should be able to flash everything. And the first thing you flash should be the latest "radio". The "radio" for Kaiser is similar to the BIOS for your PC. Like the subsystem and responsible for GSM chipset etc... So look & read in this Radio-Thread, download the latest Radio (it is 1.71.09.01) an follow the guide "Flashing Radio from microSD"
4.) Now your Phone is up-to-date and ready for flashing Android (or WinMo custom roms). YOU NEVER HAVE TO DO THE STEPS 1-3 AGAIN! Your Phone is now completely prepared!
Flashing Android:
For Android on Kaiser you always need 2 Parts. The Kernel (this part initialize the hardware so its similar to "driver" on PC) and the Built (the Android OS itself). But Both should work together so you´ll may find in some kernel suggestions in Built-threads because not ever kernel work with every built. For your beginning i whould suggest you some things:
First the kernel:
DZO is the most popular (the father of android on Kaiser) Kernel-Developer for Kaiser. So go to his repository and download "voguimg-240x320-2.6.32-froyo-09-10-10_23.nbh". Because Vouge and kaiser have almost the same hardware we all could use this kernel. But everyone have to modify this kernel to make phone related optimizations. You can do thy by hand (not recommended for you) or with a tool called "Atools". This tool is writthen in "Python" so mac and linux user could use it too. But you need to install Python. But that is all described in the Atools thread. Read through it and follow the guide.
Modifing Kernel:
We will only modify the madatory things. Not more at the moment...
So run Atools, klick on the "folder" Button and load the "voguimg-240x320-2.6.32-froyo-09-10-10_23.nbh".
Device: "Kaiser" should be checked
Resolution: 240x320 should be checked (native resolution of Kaiser display). Everything else will give blurry optic.
Version: "Froyo" should be checked, because we will flash a Froyo built (thats android 2.2). If you want to flash an older built like a Donut one (1.6) you have to modify & flash your kernel again.
Panel Type: Try "auto" or "1" first. But if you have a fuzzy screen or artifacts you have to try out which paneltype fits best for your device. HTC has built in 3 different displays in the Kaiser and the only way to find out which one is builtin is trial & error.
Keymap: Depends on which hardware keyboard layout you have. Here in Germeny i have to use "qwertz".
We leave the other options as they are an klick on the "Disk" button to save our modificated kernel now. it save it as "KAISIMG.nbh".
Now we need the Built:
I suggest "Fat Free Froyo" at the moment. Fast, stable, an looks good. So go to this thread and download "ODEX DOWNLOAD RLS5 ALL LANG-ODEX" on the bottom of the post.
then unzip/unrar this file...
Flashing your first Android:
1.) You should have a fat32 formatted SD card
2.) put the Kernel (the modified KAISIMG.nbh) to the root of SD card
3.) Create a folder named "andboot" on SD card
4.) Put the unzipped file (androidinstall.tar or .tgz) in the folder "andboot"
5.) Remove SIMcard and any cables from phone and put the SD card in your phone. Battery should be 50% carged or more...
6.) go to bootloader-mode (press and hold camera button and powerbutton). the KAISIMG should be loaded and it will show you "press powerbutton to update" or something similar. Do that... Now a progressbar will appear. When it is at 100% wait a few seconds an then pull the battery. Wait 10 seconds an insert it again. Voila! You flashed your first android kernel!
7.) Now we have to install android itself. So Power on the phone. In the moment when you see small white text on black background you have to press and hold the d-pad button. This one in the middle. Now you get in the install menu.
8.) Leave the options "System on nand" and "DATA on nand" as it is. Navigate to "install system" an press dpad. It ask "format system" and "format data". Both "YES". after this procedure you enter the menu again. navigate to "quit".
9.) Yeah! The first Bootup of Android! The first bootup takes longer as the following ones because now the system prepares for bootup and do a lot of optimisations. Even if you enter the lockscreen you should give it 10 minutes time to finish this optimization process in backround.
10.) Finish! You have flashed your first android completely! Now you can play around and make your settings. Remember: You have to sign in to your google account befor you can access the market or syncronize your contacts etc.!
Sounds more complicated as it is. Try it!
And if you´ll dig in deeper in this stuff you have to read here! Especially the Stickies/Refs/Tutorials! We´ve all done that!
have fun!

Henrykjr said:
Hey all,
I own an unlocked ATT Tilt 1 (Kaiser 8925). It is currently running windows mobile which is extremely slow. I have read all over the internet that you can put the Android 2.2 OS on this phone and have seen youtube videos on this topic also.
Ideally I need to be able to buy apps from the android marketplace.
Since I'm not a phone hacker I'd like to find a professional cel phone service company that can do this for me.
I searched extensively on Google and can't seem to find one. So who can do this and what is the normal charge for something like this.
Just trying make my old phone useful in wifi mode.
Any advice would be great.
Regards Henry
Click to expand...
Click to collapse
Brother, You can do it yourself, I can assure you. Regarding any ambiguity, you can contact me through PM. (I can guide you complete on voice over skype / msn). Its a TIDEOUS job but EASY to do since there is no MEANS OF BRICKING your kaiser (unless you flash something else than what u have do to install android).
I am here to help you in this community. And you can do this thing yourself.
Your device is At&t Tilt. The bad thing about installing android is getting a RIGHT kernel that suits your LCD type and enables wifi in the android build u install. (maybe in 1st try, maybe takes almost 10 tries like it happened for me)

Cubot X15 MTK6735, 5.5 FHD, 2.5D Glass, 4G LTE, OTG, SmartWake

First Look Video
Full Review
Welcome to another "First Look" on a china phone. In this video we will have a look at the 5.5" Cubot X15. A very stylish chinaphone in good quality. In the video I also compare the Design with the LeTV S1, so check it out
Cubot X15 MTK6735, 5.5 FHD, 2.5D Glass, 4G LTE, OTG, SmartWake
The manufacturer Cubot are not exactly known for visually beautiful smartphones. But the new model called Cubot X15 is a whole new story. It is built very sturdy and has a very solid aluminium frame, so there is no way to bend it. The backcover is made of plastic, but this can not be opened, so you can not remove the battery. This is a dual sim dual standby smart phone. In general, the smartphone looks very nice and cool and almost like something from LeTV. Nevertheless, it is quite heavy in the hand, because it also include a large battery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Specifications:
- 5.5 inch 2.5D FullHD Screen, 1920x1080 pixels
- MTK6735 64bit Quad Core, 1.3GHz
- Mali-T720 GPU
- Android 5.1 OS
- 2GB RAM + 16GB ROM
- Camera: Rear 16.0MP, Front 8.0MP
- OTG, HotKnot, Bluetooth 4.0, GPS/AGPS
- Smart Wake, Air Gestures
- MicroSD card support
- Dual SIM dual standby, Micro SIM, Nano SIM
- Network 2G/3G/4G:
- 2G: GSM 850/900/1800/1900MHz
- 3G: WCDMA 900/1900/2100MHz
- 4G: LTE 800/1800/2100/2600MHz
Source: http://notebookitalia.it

Great device, How about battery life and screen on time?
I am really looking forward to it. I am about to order a unit for myself. http://www.cubotmall.com/cubot-x15-4g-lte-mobile-phone.html , It is the official website? Anyone have any experience with CubotMall?

I'm looking to purchase that device, any owners out there.
How's the batter life?
Is it rootable?

randomjoe13 said:
I'm looking to purchase that device, any owners out there.
How's the batter life?
Is it rootable?
Click to expand...
Click to collapse
I'm still waiting for mine, it is not released yet.

s7yler said:
I'm still waiting for mine, it is not released yet.
Click to expand...
Click to collapse
According to that site it is available:
http://www.gearbest.com/cell-phones/pp_218613.html?wid=4 and this coupon gives you $26 off: X15GB

randomjoe13 said:
According to that site it is available:
http://www.gearbest.com/cell-phones/pp_218613.html?wid=4 and this coupon gives you $26 off: X15GB
Click to expand...
Click to collapse
Not available yet, also not at Gearbest, but I believe it will be in a few days. The shops say stock even days before they actually have real stock, experienced that many times.

UPDATE: I just got my X15 and so far I really like it! I have now added my "First Look" video to post #1

Anyone got this yet? Any root access? I hear I can't install nova on it? What's that about?!

Phone amazing. No root though. Someone help?
Snapchat lenses were working and stopped suddenly too.

Any at all got root access?

The Cubot X15 looks so beautiful! But it does not support waterproof?

Zunera M said:
The Cubot X15 looks so beautiful! But it does not support waterproof?
Click to expand...
Click to collapse
It is not waterproof

I have had this phone for a week now and its actually really good. The screen is quite responsive there seems to be no lag on even when there is a load on it, the brightness control and auto brightness is quit reasonable and in my opinion better than my previous phone the s4. The shut down and reboot times are very fast even when booting for the first time. Battery life is really good, when just normally using it no games just the occasional looking stuff up on google, using facebook all day and texting and calling it last be 61 hours. Gaming on it and heavy used produced an up time of 37 hours. The speaker shocked me since there is a grill for a second speaker but there is only one on the bottom, but sound quality is great. Call quality is pretty good people who normally used sound mumbled come in more clearly and i can actually make out what they are saying. Gaming performance is very good, hardly any lag from actual graphics or processing only lag for me came when my wifi was being bogged by my roommate. The screen itself is fairly water resistant but not water proof and i dont plan on testing that any further. The only con i really have found so far is that i cant root it whether it is my own ignorance on this type of phone or there isnt a reliable method out yet it still upsets me. My personal overall rating would have to be 8.5/10 I would definitely recommend this phone to people whom are on a budget and want a nice phone

Still no root access anyone? Or even a Snapchat fix? That's the only reason I want root, sad I know. No lenses on Snapchat is doing my head in

McMCC in the russian forum 4pda rooted his Cubot X15.
He used Pack-Flashtool-v5.1528.00.000.rar what seems to be the flash-tool of mediatek.
Maybe someone can try if he reaches to root his phone with these tools.
Sorry I can not post links yet.

That's good to know. I literally have no idea how to do that but thanks for giving me hope.

A Full Review video has now also been added to post #1

Finally got a Successful ROOT!
So after rooting I installed Nova and deleted the stock launcher and it improved responsiveness tenfold. I also started ripping out other apps that I know I'll never use like hotknot, Launcher, and have installed 3C Toolbox which after setting up TRIM and turning on all maintenance on boot has really helped. Droidoptimizer is awesome as well.

Everything you need to RooT
Alright, So this is everything that I managed to find,compile,tweak, and finally get to work on my Cubot x15 which should work for every other cubot x15. I'll tell you exactly how I managed to get root working and provide a link with the working cwm and drivers and the stock rom and a way to flash back to it. I used the stock 5.1 x15 scatter file to map out CWM and it works for me so far. Sorry I'm not too much of a writer but I'll try my best.
1. Every thing you need plus probably some you dont, https:// www.dropbox.com /sh/4iskxmmzxvj48z9/AACIs5Vm3Q_2yxGMIqktKadGa?dl=0
2. Now this is going to be how I did it step by step, if you know a better way or can see how i'm setting it up then help us if you know a faster way. I installed ADB-setup-1.4.2.exe first, hit yes on the 3 things that it asks. now these drivers won't detect the x15 but it installs all the ADB where it needs to go, mainly in C:\ADB and users\.android so if you know how to do it you can skip this part but if not I would install it.
3.Okay, so on your cubot go to settings, about phone, and tap on build 7 times to enable developer options. In developer options turn on USB debugging and OEM unlocking. Now OEM unlocking is going to wipe your phone back to stock, backup what ever you can like pictures, music, and so fourth, if you have a microSD card in your phone it won't wipe that so migrate what you can to your SD. Now this is the part that I got stuck on for a while trying every MTK tool and adb command so I'll save you some time. After you turn OEM unlocking on, power off your phone and then turn it back on while holding VOL + or up and power together, this should bring you into to a black screen with the choice to boot into Recovery/FastBoot//Normal, volume + changes choices and Vol - selects. Well need to manually put it into fastboot mode after the next step. so go to normal for now and reboot.
4. So download Nicks Cubot x15 root TooLs, there are the cubot drivers that we need in adb_fastboot_utils, what i did was unrar'd that folder into C:\ADB and replaced that adb drivers that we installed in the last step with the new ones we need for the cubot, it works pretty well. Install them by replacing the other ADB drivers but if it doesn't take then you can right click on your computer, go to manage, device manager, click in the window where you don't select anything , like under Universal Serial Bus controller when it's closed, you do this so that the action tab will then let you select add legacy hardware. Go to Action, Add Legacy Hardware, click on next, select install the hardware that I manually select from a list, Next, show all devices highlighted, Next, Have Disk, then browse to C:\ADB and find the folder, I'm using windows 8 so I ended up in C:\adb\usb_driver_mtk_win8 and click the .inf file. If windows gives you **** about not being signed and fails then you have to reboot while holding shift, go to advanced options and reboot without driver enforcement, i think it's number 7. if you do have to do that just repeat the device driver install steps and it should work. Now, after you get all this installed you can test it by opening CMD and typing adb devices. Your phone should show up but it will say unauthorized, if not make sure USB debugging is turned on in developer options and that your phone is plugged in via USB cable. if you get the unauthorized message open your lock screen and your phone should be asking you to authorize your computer, check always remember computer and authorize.
4. So now for the fun part. If you did it correctly you can now see your phone by typing adb devices in CMD prompt. If you can then make sure you saved what you wanted onto your sdcard and go to developer options and tick OEM unlocking again. now you should still have your ADB CMD prompt window open with your device being seen, if thats the case type, cd C:\adb, which should change your command directory to C:\ADB, after you switch directories type, adb reboot bootloader, your phone should reset to a black screen with some options, VOL + changes options and VOL - selects, if you have the option, select fastboot, if not then type fastboot devices. If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine but if you do see your device type, fastboot oem unlock. Now go to your phone and it will prompt you to make sure you want to unlock your bootloader, VOL + to accept or VOL - to reboot. hit VOL + and CMD prompt will let you know when it's finished. After it's finished. Leave the CMD prompt open and your phone in Fastboot mode. and read the next step.
5. Alright so your phone should be in fastboot mode, now in my included root tool kit I have included recovery images, recovery.img is the stock one and Cwm_recovery.img is the one we want to flash. So copy cwm_recovery.img into C:\ADB if you installed the adb drivers in step 2 or the cwm recovery to where ever your sdk tools are. RENAME cwm_recovery.img to just recovery.img, if you're lazy just select rename and delete cwm_. So it should be sitting in C:\ADB\Recovery.img along with fastboot and adb that you copied.
6. So after moving the new cwm_recovery.img that you renamed to recovery.img into your c:\adb folder you're almost done, type fastboot flash recovery recovery.img and after a couple of seconds Fastboot will flash the image and give you a success/failure notification. If successful, you're all set. To check out the new recovery image you have to reboot by typing fastboot reboot or just holding the power button down. Now hold VOL + and power to reboot to the options screen with Recovery, Fastboot, Normal. VOL + until you highlight Recovery and then press VOL -. You should boot into your new CWM recovery. I have included SuperSu.Zip, BusyBox.Zip, and Xposed Framework.Zip. I flashed all of these but not at the same time. I did SuperSu first and rebooted to see if it would boot and it did. SuperSu rooted the phone enough to where I installed busybox.apk but you can restart and flash busybox.zip. Now with Xposed after I flashed it, it took a minute to boot and it started optimizing android apps, it restarted 4 times or so before completing optimization so don't freak out, it will optimize them all and then boot. You should now have a fully rooted Cubot x15 complete with xposed framework.
If you have any questions or if I wasn't clear enough on a certain part please feel free to ask and I'll try my best to help. I'll even reflash my phone if you get stuck and need help, we'll figure it out. Any ways, I hope this helps you guys and it has been working stable for me so far.

Hello, thank you for your detailled instructions, but i can not open the dropbox link. so i could not get the cwm_recovery.img. Please shre it once more. Thanks
Chris

Android tablet, how to disable kiosk mode or install new firmware

I am new to the android programming world. I own an iQR70 device from MLS that is using -if I read well- the kiosk mode for its own application called MAIC (something like Amazon's Alexa virtual assistant).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The real pain with this device is that the application is buggy does not get any updates and overall does not work properly.
So, my questions are, a) is there any way to disable the kiosk mode and work with it as a normal tablet? or desperately b) Can I install a compatible firmware? I don't care for the data inside.

You can check for update. Look for android version of tablet. You can check their site for any upgrade of software.
You can flash other firmware. Find compatible firmware as per your model.
You can disable apps same as you do on android mobile.

My tablet currently Is dead boot and I am trying to find the test points. Anyway, I have no access to the android os to disable apps. The virtual assistant is the only app I can use, all others are forbidden.

Hi sdancer,
I got the same device and it's stuck in bootloop as well, after I experimented a bit too much. Stock recovery ist not working (when I select it in the boot menu it just reboots again), I can only get into Fastboot mode, but the PC won't recognize the device at all, because I guess I don't have the necessary drivers, USB connection never worked.
Did you manage to get it back on? And does your PC recognize your device?

zeetotheuno said:
Hi sdancer,
I got the same device and it's stuck in bootloop as well, after I experimented a bit too much. Stock recovery ist not working (when I select it in the boot menu it just reboots again), I can only get into Fastboot mode, but the PC won't recognize the device at all, because I guess I don't have the necessary drivers, USB connection never worked.
Did you manage to get it back on? And does your PC recognize your device?
Click to expand...
Click to collapse
Can you send commands under fastboot from your pc; if the drivers are the problem then try to fix them. In my case I deleted the Preload partition so I can not even power up the device. The only solution in my case, is the hardware reset using kolo connection pin shorted with ground and immediately flash from a stock Rom or a previously saved backup. I didn't find time to try it yet.

sdancer said:
Can you send commands under fastboot from your pc; if the drivers are the problem then try to fix them. In my case I deleted the Preload partition so I can not even power up the device. The only solution in my case, is the hardware reset using kolo connection pin shorted with ground and immediately flash from a stock Rom or a previously saved backup. I didn't find time to try it yet.
Click to expand...
Click to collapse
No, I can't send any commands, unfortunately. I can't finx the drivers either, because I never had them. The MTK drivers I installed did never work. I could never connect it to the PC before, because it was never recognized. Did your PC recognize device at all? Or does it recognize the other one you have, which is working?
I opened MAIC and tried to find the test spot, but there is really NOTHING written on the spots (No GND, no Kcolo, just nothing at all). I tried connecting some of the spots, but it didn't work.
If you try it and find out, would you be so kind to share?
By the way, I was able to get into the developer options by chance. When you press the small sun (swipe down on the main screen, and tap on the small sun on the right side, where you set the display brightness, several times)
Usually a prompt will pop up and ask for a password (which I couldn't find anywhere, not even their support would tell me)
But I was lucky once and got into these settings when there was some kind of bug in one of the previous versions. But I couldn't flash anything onto it, because as I said, my computer wouldn't recognize the device.

zeetotheuno said:
No, I can't send any commands, unfortunately. I can't finx the drivers either, because I never had them. The MTK drivers I installed did never work. I could never connect it to the PC before, because it was never recognized. Did your PC recognize device at all? Or does it recognize the other one you have, which is working?
I opened MAIC and tried to find the test spot, but there is really NOTHING written on the spots (No GND, no Kcolo, just nothing at all). I tried connecting some of the spots, but it didn't work.
If you try it and find out, would you be so kind to share?
By the way, I was able to get into the developer options by chance. When you press the small sun (swipe down on the main screen, and tap on the small sun on the right side, where you set the display brightness, several times)
Usually a prompt will pop up and ask for a password (which I couldn't find anywhere, not even their support would tell me)
But I was lucky once and got into these settings when there was some kind of bug in one of the previous versions. But I couldn't flash anything onto it, because as I said, my computer wouldn't recognize the device.
Click to expand...
Click to collapse
Hi, the developer mode is very essential to use the adb (Android debug bridge) and finally disable the kiosk mode. Can you explain how to enable it, because I am not sure if understand well.
My device is dead boot, does not power up currently, but I have another one that works. Before that, yes it connected with my windows, that's how I flashed it and finally bricked it. I have the drivers and they works just fine. In you case you don't have dead boot device, cos you can power it on and use fast boot.
So you don't need hardware reset. Just fix the drivers, if you need them, I can send them to you.
PCB does not have any indication of kolo pin joint. I didn't find anything either, but I am gonna use the mediatek pinout diagram I found, and proceed with test & trial method.

sdancer said:
Hi, the developer mode is very essential to use the adb (Android debug bridge) and finally disable the kiosk mode. Can you explain how to enable it, because I am not sure if understand well.
Click to expand...
Click to collapse
Well, basically just try this, (for the one that still works):
- You just let it boot normally until you see the MAIC woman on the main screen.
- Swipe down from the top of the screen, so you can get to this menu, you know, where you can access "Home", "Music", "Video Call" etc.
- You will see the brightness adjustment bar with a big sun and a small sun. Tap the sun on the right side of the bar about 9 times
- Now you'll see a message pop up, which asks you for a password
And this is where I got stuck for a long time. And usually you can't get past this point I guess.
But one day, when they updated the software to V 4.01 I just could access the developer options and enable ADB and stuff. I have no idea how that worked, it must have been a bug within the version. After another update of the MAIC software (V 4.02), I couldn't access it anymore either.
Maybe you're lucky and you'll be able to get into it too, if you didn't install the latest update yet.
What I did was, I installed a launcher (I was able to use the devices browser and access the apk) and then I could switch between Kiosk mode and the "normal" android display. If you could manage to install any launcher (I used Evie Launcher and it worked great) you can use it like a tablet (it's slow as hell, though).
sdancer said:
My device is dead boot, does not power up currently, but I have another one that works. Before that, yes it connected with my windows, that's how I flashed it and finally bricked it. I have the drivers and they works just fine. In you case you don't have dead boot device, cos you can power it on and use fast boot.
So you don't need hardware reset. Just fix the drivers, if you need them, I can send them to you.
Click to expand...
Click to collapse
That would be soooo great, if you could share the drivers! It would help me a lot. Because like you, I would try flashing a stock ROM, too, and maybe we'll find a way to enable ADB with a modified ROM.
sdancer said:
PCB does not have any indication of kolo pin joint. I didn't find anything either, but I am gonna use the mediatek pinout diagram I found, and proceed with test & trial method.
Click to expand...
Click to collapse
Well, let me know, if you find something! I gave up already, because I really didn't find the right spots. On the small PCB on the left, if you unscrew it and turn it around, there are several more gold points, btw. Maybe you'll find something there. And on the small board (where the Buttons for Power, Volume + and Volume - are located) there are some golden points too.

zeetotheuno said:
Well, basically just try this, (for the one that still works):
- You just let it boot normally until you see the MAIC woman on the main screen.
- Swipe down from the top of the screen, so you can get to this menu, you know, where you can access "Home", "Music", "Video Call" etc.
- You will see the brightness adjustment bar with a big sun and a small sun. Tap the sun on the right side of the bar about 9 times
- Now you'll see a message pop up, which asks you for a password
And this is where I got stuck for a long time. And usually you can't get past this point I guess.
But one day, when they updated the software to V 4.01 I just could access the developer options and enable ADB and stuff. I have no idea how that worked, it must have been a bug within the version. After another update of the MAIC software (V 4.02), I couldn't access it anymore either.
Maybe you're lucky and you'll be able to get into it too, if you didn't install the latest update yet.
What I did was, I installed a launcher (I was able to use the devices browser and access the apk) and then I could switch between Kiosk mode and the "normal" android display. If you could manage to install any launcher (I used Evie Launcher and it worked great) you can use it like a tablet (it's slow as hell, though).
That would be soooo great, if you could share the drivers! It would help me a lot. Because like you, I would try flashing a stock ROM, too, and maybe we'll find a way to enable ADB with a modified ROM.
Well, let me know, if you find something! I gave up already, because I really didn't find the right spots. On the small PCB on the left, if you unscrew it and turn it around, there are several more gold points, btw. Maybe you'll find something there. And on the small board (where the Buttons for Power, Volume + and Volume - are located) there are some golden points too.
Click to expand...
Click to collapse
No problem at all, I will attach them (drivers) on Monday when I return back to my office. I will attach you also screenshots from my device manager to know how windows recognize them.
This is all you need in your case, don't bother with the hardware reset.

sdancer said:
No problem at all, I will attach them (drivers) on Monday when I return back to my office. I will attach you also screenshots from my device manager to know how windows recognize them.
This is all you need in your case, don't bother with the hardware reset.
Click to expand...
Click to collapse
That's awesome! Thank you in advance.
Yeah, I guess the hardware reset really takes some time and a lot of trial and error.
But if you manage to do it, let me know, I'm just curious in general, if that's possible with this device.

To Flash your device,
1) Install the drivers
2) Press Download from SP Flash Tool
2) Connect USB
3) Connect the power outlet from your device (in this case) or connect the battery
****WARNING: DONT FORMAT THE PRELOAD or you will get a DEAD BOOT device, use ONLY DOWNLOAD and not download+format
AutoInstall
=================
MediaTek_Preloader_USB_VCOM_drivers.exe
File on MEGA
mega.nz
Manual Install
=================
MediaTek_Preloader_USB_VCOM_Drivers_Setup_Signed.zip
File on MEGA
mega.nz
MediaTek_Preloader_USB_VCOM_Drivers.zip
File on MEGA
mega.nz

Hey @sdancer, thank you for the drivers. But I must do something wrong, because it's still not detected. It's not showing in my device manager and nothing happens in SP Flashtool.
I tried the automatic install and the manual install, but still nothing :/
Could you maybe explain how exactly you installed them? Maybe I'm making a mistake there.

1) Check the USB cable and make sure it works fine for data transfers (some cables are only for charging and does not contain the data wires inside)
2) Download the drivers https://mega.nz/file/ePITwCbA#DvF-SAOA8_nI0vFReV_fR1JuDJa_1us_SDnQKUstoZ4
3) Follow the instructions I recorded for you at

sdancer said:
1) Check the USB cable and make sure it works fine for data transfers (some cables are only for charging and does not contain the data wires inside)
2) Download the drivers https://mega.nz/file/ePITwCbA#DvF-SAOA8_nI0vFReV_fR1JuDJa_1us_SDnQKUstoZ4
3) Follow the instructions I recorded for you at
Click to expand...
Click to collapse
Hi again, sorry it took a while to reply. So, I tried, and it does find the device now, but only as "Unknown device" and not as "Android Device". I tried several drivers but it won't connect, when I try SP Flashtool.
Really tough thing, this MAIC, haha.

zeetotheuno said:
Hi again, sorry it took a while to reply. So, I tried, and it does find the device now, but only as "Unknown device" and not as "Android Device". I tried several drivers but it won't connect, when I try SP Flashtool.
Really tough thing, this MAIC, haha.
Click to expand...
Click to collapse
Hi
I suppose that this is a driver's problem, you should try to fix it someway.

Hello good people! I did a factory reset because this device was not working good and it was really buggy, I did this before when i had problem with the device, but now I'm stuck at location selection and can't pass it! Please take a look at my pictures, to clear the situation.
I'm seeking for help for months now, so, if anyone can help me, I will be really grateful
Thank you, Marko

Marko121212 said:
Hello good people! I did a factory reset because this device was not working good and it was really buggy, I did this before when i had problem with the device, but now I'm stuck at location selection and can't pass it! Please take a look at my pictures, to clear the situation.
I'm seeking for help for months now, so, if anyone can help me, I will be really grateful
Thank you, Marko
Click to expand...
Click to collapse
Any idea, Any fix?

paulos2951 said:
Any idea, Any fix?
Click to expand...
Click to collapse
I have no idea bro :/ Hoping that someone will help me

Marko121212 said:
Hello good people! I did a factory reset because this device was not working good and it was really buggy, I did this before when i had problem with the device, but now I'm stuck at location selection and can't pass it! Please take a look at my pictures, to clear the situation.
I'm seeking for help for months now, so, if anyone can help me, I will be really grateful
Thank you, Marko
Click to expand...
Click to collapse
I have the same problem with you
If you find a solution please send me a message !

Jim-Kyritsis said:
I have the same problem with you
If you find a solution please send me a message !
Click to expand...
Click to collapse
Hi friend! Are you Greek? Is there a way to contact MLS in Greece?

Question Android Beta to Factory Reset mucked up, plus a bunch of troubleshooting I've already tried

Okay. The android beta program was messing with an app I use regularly so I backed up my phone on google 1 and all that fun stuff then did the opt out and just ran stuff like it was supposed to. Then, it got stuck in fastboot mode and said that the installation failed. If this wasn't already obvious I'm not good at talking tech but I am decent at troubleshooting things, so I tried. Today I learned what fastboot and adb are, what sideloading is, stuff like lineageos and twrp if. If that's what that one was called, today is a blur. Okay let me be more specific.
It seems like what I need to do is sideload the right OTA image, but I can't find the one I need. The last two I tried, one being the very wrong one and one being (copied from official source):
12.1.0 (SQ3A.220705.003, Jul 2022)Linke66e2df393d5a0f885f62d2de086dcd80cdcf8eb28d567f4582ff67756876170
But this one also wasn't new enough? It says: error: recovery: update package is older than the current build, expected a build newer than the timestamp 1657306786 but package has timestamp 1654117437 and downgrade not allowed.
I've tried the flashing tool (my phone shows up but has a connection issue I couldn't fix), the google rescue mode tool (my phone connected but the browser tool just looped til the phone timed out), I've tried sideloading the twrp apk and such which didn't work due to "error: closed" which I also couldn't fix, but I'm pretty sure all these problems are caused by not having developer options and debugging and those things turned...whichever way they need to be.
If this is important, I'm in Canada, using Telus, the phone is still fairly new and was working perfectly I just had to opt in and then out of the android beta. Kicking myself for that now. If I need to be more specific I'll try but for now, can I unbrick my phone without taking it somewhere to be unbricked for me? I also don't have an SD card to use to do it that way. Thank you.

Try This link for help.

lilyhollow said:
Okay. The android beta program was messing with an app I use regularly so I backed up my phone on google 1 and all that fun stuff then did the opt out and just ran stuff like it was supposed to. Then, it got stuck in fastboot mode and said that the installation failed. If this wasn't already obvious I'm not good at talking tech but I am decent at troubleshooting things, so I tried. Today I learned what fastboot and adb are, what sideloading is, stuff like lineageos and twrp if. If that's what that one was called, today is a blur. Okay let me be more specific.
It seems like what I need to do is sideload the right OTA image, but I can't find the one I need. The last two I tried, one being the very wrong one and one being (copied from official source):
12.1.0 (SQ3A.220705.003, Jul 2022)Linke66e2df393d5a0f885f62d2de086dcd80cdcf8eb28d567f4582ff67756876170
But this one also wasn't new enough? It says: error: recovery: update package is older than the current build, expected a build newer than the timestamp 1657306786 but package has timestamp 1654117437 and downgrade not allowed.
I've tried the flashing tool (my phone shows up but has a connection issue I couldn't fix), the google rescue mode tool (my phone connected but the browser tool just looped til the phone timed out), I've tried sideloading the twrp apk and such which didn't work due to "error: closed" which I also couldn't fix, but I'm pretty sure all these problems are caused by not having developer options and debugging and those things turned...whichever way they need to be.
If this is important, I'm in Canada, using Telus, the phone is still fairly new and was working perfectly I just had to opt in and then out of the android beta. Kicking myself for that now. If I need to be more specific I'll try but for now, can I unbrick my phone without taking it somewhere to be unbricked for me? I also don't have an SD card to use to do it that way. Thank you.
Click to expand...
Click to collapse
what was the error you got in Android Flash Tool?

jcp2 said:
what was the error you got in Android Flash Tool?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I checked with all the troubleshooting tips for connection issues but nothing changed the status. Sometimes it would say already in use when I had the cmd open but then I use kill-server to free it up and it changes to this.

Is your bootloader unlocked? If it isn't (and if Telus is like the US phone carriers), then I don't think you would be able to revert back to Android 12. You will have to wait for Android 13 to officially launch and you can then manually flash the full image (as it seems that you cannot sideload the OTA). And you would have to manually flash the latest full Android 13 beta build for the time being.
Regardless, right now you should try looking into "platform-tools" here on XDA. Then, see if you can use adb to view your phone over USB connection with the stock Google USB cable that came with the phone (most random aftermarket cables work fine, however, a few do not seem to work). You would need USB Debugging enabled to do this, however, the phone may still respond since you had it fall into fastboot mode before (and you would essentially be using adb to put your phone into fastboot mode).
Leave a reply if you can put your phone into fastboot mode/if you can use adb. We can go further from there with what I know about this stuff.

NippleSauce said:
Is your bootloader unlocked? If it isn't (and if Telus is like the US phone carriers), then I don't think you would be able to revert back to Android 12. You will have to wait for Android 13 to officially launch and you can then manually flash the full image (as it seems that you cannot sideload the OTA). And you would have to manually flash the latest full Android 13 beta build for the time being.
Regardless, right now you should try looking into "platform-tools" here on XDA. Then, see if you can use adb to view your phone over USB connection with the stock Google USB cable that came with the phone (most random aftermarket cables work fine, however, a few do not seem to work). You would need USB Debugging enabled to do this, however, the phone may still respond since you had it fall into fastboot mode before (and you would essentially be using adb to put your phone into fastboot mode).
Leave a reply if you can put your phone into fastboot mode/if you can use adb. We can go further from there with what I know about this stuff.
Click to expand...
Click to collapse
Bootloader is locked. It's permanently stuck in fastboot mode, except when I switch to recovery or rescue, and then if I reboot the phone it goes into fastboot. When I use adb and use "adb devices" my device shows up as [devicenumber] sideload. Other adb commands won't work due to "error: closed" which I assumed was because debugging was off. Only thing I got to work so far was sideloading OTA, and you see how that went. But I do have platform-tools and adb and fastboot set up. So that's something. My USB cord is aftermarket but does seem to work.

are you using These drivers? for windows. which version of windows are you running? I think @NippleSauce is correct in that if you don't have usb debugging enabled (you don't) you'll have to wait for A13 final. Or, if you're in your 30 day return window.....take it back to Telus.

Sorry, I've been eating and lifting weights at almost the same time LOL. I also just got the Pixel Buds Pro in the mail (a day before the official release) and they are freaking amazing.
Anyway, since the phone keeps going into fastboot, perhaps we can move forward. What does the screen say on it when in fastboot? There are two different fastboot menus: regular "fastboot" and "fastboot d".
Feel free to post a screenshot if you have something to take a picture of the display with. We'll move forward from there once I'm done lifting =).

NippleSauce said:
Sorry, I've been eating and lifting weights at almost the same time LOL. I also just got the Pixel Buds Pro in the mail (a day before the official release) and they are freaking amazing.
Anyway, since the phone keeps going into fastboot, perhaps we can move forward. What does the screen say on it when in fastboot? There are two different fastboot menus: regular "fastboot" and "fastboot d".
Feel free to post a screenshot if you have something to take a picture of the display with. We'll move forward from there once I'm done lifting =).
Click to expand...
Click to collapse
how are those compared to the pixel buds a?

DespairFactor said:
how are those compared to the pixel buds a?
Click to expand...
Click to collapse
Holy shirtless cow with nine udders good. I'm really liking them. The 11mm drivers really amp up the quality and separation in the sound. I think they're quite close in sound quality to my Sennheiser True Wireless 3's - so I think the price makes it a good deal on today's market. But the thing that makes them such a good deal is that the transparency mode is awesome and is clear and audible to the point where you can't even tell via the audio that you're wearing earbuds. And on top of that, the noise cancellation is some scientific voodoo with its strength for specific sounds. Some light (and semi-enjoyable) sounds pass right through; like me typing on my keyboard or clicking my computer mouse. But other sounds that are generally more noticeable such as people speaking or audio from cellphones is completely gone. It's pretty weird but is very good!
And to top it off, I am also pretty poor in hearing after an sTBI a few years ago. Audio was important to me before the incident, and therefore has become more important to me now. But since my left ear hears sound in a way that makes the sound that goes to my brain sound like people speaking in Charlie Brown, I guess take my opinions with a grain of salt lol.

lilyhollow said:
Okay. The android beta program was messing with an app I use regularly so I backed up my phone on google 1 and all that fun stuff then did the opt out and just ran stuff like it was supposed to. Then, it got stuck in fastboot mode and said that the installation failed. If this wasn't already obvious I'm not good at talking tech but I am decent at troubleshooting things, so I tried. Today I learned what fastboot and adb are, what sideloading is, stuff like lineageos and twrp if. If that's what that one was called, today is a blur. Okay let me be more specific.
It seems like what I need to do is sideload the right OTA image, but I can't find the one I need. The last two I tried, one being the very wrong one and one being (copied from official source):
12.1.0 (SQ3A.220705.003, Jul 2022)Linke66e2df393d5a0f885f62d2de086dcd80cdcf8eb28d567f4582ff67756876170
But this one also wasn't new enough? It says: error: recovery: update package is older than the current build, expected a build newer than the timestamp 1657306786 but package has timestamp 1654117437 and downgrade not allowed.
I've tried the flashing tool (my phone shows up but has a connection issue I couldn't fix), the google rescue mode tool (my phone connected but the browser tool just looped til the phone timed out), I've tried sideloading the twrp apk and such which didn't work due to "error: closed" which I also couldn't fix, but I'm pretty sure all these problems are caused by not having developer options and debugging and those things turned...whichever way they need to be.
If this is important, I'm in Canada, using Telus, the phone is still fairly new and was working perfectly I just had to opt in and then out of the android beta. Kicking myself for that now. If I need to be more specific I'll try but for now, can I unbrick my phone without taking it somewhere to be unbricked for me? I also don't have an SD card to use to do it that way. Thank you.
Click to expand...
Click to collapse
I opted out of the A13 beta and ran into the sane issue as my bootloader is locked. I was able to get back to A12.
I Googled it and found that you need to use the volume buttons to scroll to recovery and select by pressing the power button. You will then see a screen that says no command, hold the power button and tap volume up and you will be in recovery mode. Scroll down and select install from ADB. You will need to place the most recent A13 OTA zip in platform tools which is what I use for all of my ADB stuff or whatever you use for ADB installation. DO NOT CHANGE THE FILE NAME. Once you have selected install from ADB on your device, type adb install (file name.zip), if you don't include.zip behind the file name, it will error out.
Once you hit enter, your device will say verifying file and you will see the percentage on the pc screen in adb. Once it completes the installation, reboot your device and skip through the setup. Once you skio through setup and get to the home screen, go into settings and go to where you check for updates, it should say update available,if not do a manual check. Once you are prompted about an update, select to download and install. It will install A12 with all the warnings about it wiping your device. Once this install completes and you restart, you will be back on A12.

Thank you everyone! Someone helped me out over telegram after I posted this and we worked through it, realized part of the problem was my cord, and then mostly fixed it the way truckerdewd said, except once android 13 was loaded, I used the Android Flash tool to set it back to 12 and it worked. I'm typing this from a working phone and very happy about it. <3
On a side note how are those fancy new ear buds comfort wise? I have a lot of trouble with pain from ear buds and only use really comfy over ear headphones that I like but I'm desperate for ear buds I don't hate.

lilyhollow said:
Thank you everyone! Someone helped me out over telegram after I posted this and we worked through it, realized part of the problem was my cord, and then mostly fixed it the way truckerdewd said, except once android 13 was loaded, I used the Android Flash tool to set it back to 12 and it worked. I'm typing this from a working phone and very happy about it. <3
On a side note how are those fancy new ear buds comfort wise? I have a lot of trouble with pain from ear buds and only use really comfy over ear headphones that I like but I'm desperate for ear buds I don't hate.
Click to expand...
Click to collapse
I got these Razer Chroma Earbads and they are super comfy and sound great. I got the ones that light up.
https://www.amazon.com/Razer-Hammerhead-Wireless-Bluetooth-Earbuds/dp/B099LZ2BGB/ref=mp_s_a_1_3?crid=V3S5O8UC9983&keywords=razer+chroma+earbuds&qid=1658996631&sprefix=Razer+chroma+ear%2Caps%2C152&sr=8-3

NippleSauce said:
Holy shirtless cow with nine udders good. I'm really liking them. The 11mm drivers really amp up the quality and separation in the sound. I think they're quite close in sound quality to my Sennheiser True Wireless 3's - so I think the price makes it a good deal on today's market. But the thing that makes them such a good deal is that the transparency mode is awesome and is clear and audible to the point where you can't even tell via the audio that you're wearing earbuds. And on top of that, the noise cancellation is some scientific voodoo with its strength for specific sounds. Some light (and semi-enjoyable) sounds pass right through; like me typing on my keyboard or clicking my computer mouse. But other sounds that are generally more noticeable such as people speaking or audio from cellphones is completely gone. It's pretty weird but is very good!
And to top it off, I am also pretty poor in hearing after an sTBI a few years ago. Audio was important to me before the incident, and therefore has become more important to me now. But since my left ear hears sound in a way that makes the sound that goes to my brain sound like people speaking in Charlie Brown, I guess take my opinions with a grain of salt lol.
Click to expand...
Click to collapse
I got my pair coming via amazon today