Yo guys! I have Sonyericsson Xperia X10,and I wanna ask a question.... : is it possible to flash other phones' rom such as Htc, samsung, motorola,etc? ? Thx!
yes you can, and absolutely with the same OS
Drivers probably wont work at all...probably will bootloop
Sent from my Droid using XDA App
what do mean by that? Drivers dont work? What kind of Drivers?
*throws an anti troll grenade*
read windows for dummys.
thats an easy way to put it,
same reason you cant put WindowsXP on a phone. the drivers wont work.
if you put a rom for a phone with a touch screen, on a regular smart phone it wont work.
if you put a rom for a 5000 CPU in a device with a 7500 CPU it probably wont work.
you don't sew your leg onto your arm joint and wonder why it doesnt work.
Computers are picky things. they have to be told what is where and how to use it. or you get a critical error, or at best, something working but barely.
which mean... I cannot -3- sosad, I wanna try HTC sense
well thats where rom cooking comes in, basically, its like theres something you like from one salad, like the olives. but you only have a basic salad with just lettuce and tomatoes.
with rom cooking you basically take the olives from the other salad and put them on your salad.
you can move apps possibly, images and themes. but if the screen resolution doesnt match guess what? no go, mobile doesnt stretch like windows XP.
since you are a beginner, your best bet is to learn your phone first.
get all the device information. get some tools, and back your phone up.
or at least learn how to hard reset it back to factory state. and add apps, or mess with the registry (this is how most of us learned about Windows, and every other OS.)
learn how to reinstall an OS, than you can go and eff it up. try to fix it, and if you can reset back to factory state.
I know all of them, and My phone would restart every 90 secs before (coz I installed Busybox Twice and messed up the system ) , I can deal with it. About the resolution of the screen, many phones have the same of Xperia X10 , so...... Can you directly tell me, Is it possible or not ( meaning that cant even install it ) ?
Without modifying you CAN'T just put a ROM from a different device on yours.
NOBODY EXPLAINED WHY..
ok i will tell u..
to get others rom to work for ur device, first look which device is the rom made for..
then google for that phone's hardware specs.. if the chipset & other general specs of that phone match yours then WALA!!!! u can use the rom!!!!! for sure!!!
will it b anything wrong if suddenly out phone out of battery while flashing the rom??
Thx dude.... I will try it later!!
scopio said:
will it b anything wrong if suddenly out phone out of battery while flashing the rom??
Click to expand...
Click to collapse
nooo..
BIOS EQUIVALENT to custom recovery mode.. it wont harm ur phone but u will have to flash rom again..
Yes I agree with zeemar007.
Most likely the ROM would have to be ported (or hacked in pure tech terms) to make it compatible with a different phone/model. Especially if the hardware specs are different than the phone the ROM has originally been designed for.
there will be a bootloop
Okay. Ignore the title, I couldn't think of anything to put. In short, I want to know about roms, about clockworkmod, cyanogen mod, and stuff like that. What they do, how to put them on, and I pretty much wanna know about the general stuff you do past rooting your phone. And I know that the section says No Noobs, but technically, I'm a newb, as far as I know i'm not annoying anyone or being completely nooblike.
Mainly with cyanogen. I read the instructions, and they seem too, I dont know, simplistic. I'd prefer exact details. Like, after I have clockwork mod installed, and I flash cyanogen, can i restore all the stuff I had on it? And once cyanogen is on there, is it already rooted, or must i root again? And if someone would explain to me how clockworkmod works in the first place. And how would I flash cyanogen? I thought it'd be through clockworkmod, but if I wipe everything and factory reset, wouldn't clockworkmod be gone?
My phone is a Samsung Galaxy S (Vibrant or not vibrant, I dont even know) It's a GT-i9000M. Running android 2.2.1, Rooted, I have clockworkmod installed, but still no idea what to do past that point. Also, my Kies isn't telling me about any 3.x upgrade, so how would i go about manually installing a new version of android? I know it has to do with Odin, but whenever i tried i ended up not doing anything.
And one last thing about MetaMorph. Where could i find themes for it? And do i need to have a certain Rom running in order to use metamorph themes?
I'm mainly used to iPhones and such, where there isnt really much to do besides jailbreaking and such, and moving on to android phones is pretty intense. XD So much more to do with Android phones.
Well uh, thats about all i can think of at the moment. Also please post anything you feel that a (somewhat) newb to android modding should know.
Sorry for all the questions, and to those that help me, I love you. <3
And if any moderators deem this thread as against the 'No Noobs' rule, at least send me a message telling me you deleted it, or else I'll end up looking endlessly through the forums for my thread. I've done that before, not fun. LOL (Couldn't find a 'My Threads' thingy on the forum i was using.
Gutana said:
Okay. Ignore the title, I couldn't think of anything to put. In short, I want to know about roms, about clockworkmod, cyanogen mod, and stuff like that. What they do, how to put them on, and I pretty much wanna know about the general stuff you do past rooting your phone. And I know that the section says No Noobs, but technically, I'm a newb, as far as I know i'm not annoying anyone or being completely nooblike.
Mainly with cyanogen. I read the instructions, and they seem too, I dont know, simplistic. I'd prefer exact details. Like, after I have clockwork mod installed, and I flash cyanogen, can i restore all the stuff I had on it? And once cyanogen is on there, is it already rooted, or must i root again? And if someone would explain to me how clockworkmod works in the first place. And how would I flash cyanogen? I thought it'd be through clockworkmod, but if I wipe everything and factory reset, wouldn't clockworkmod be gone?
My phone is a Samsung Galaxy S (Vibrant or not vibrant, I dont even know) It's a GT-i9000M. Running android 2.2.1, Rooted, I have clockworkmod installed, but still no idea what to do past that point. Also, my Kies isn't telling me about any 3.x upgrade, so how would i go about manually installing a new version of android? I know it has to do with Odin, but whenever i tried i ended up not doing anything.
And one last thing about MetaMorph. Where could i find themes for it? And do i need to have a certain Rom running in order to use metamorph themes?
I'm mainly used to iPhones and such, where there isnt really much to do besides jailbreaking and such, and moving on to android phones is pretty intense. XD So much more to do with Android phones.
Well uh, thats about all i can think of at the moment. Also please post anything you feel that a (somewhat) newb to android modding should know.
Sorry for all the questions, and to those that help me, I love you. <3
And if any moderators deem this thread as against the 'No Noobs' rule, at least send me a message telling me you deleted it, or else I'll end up looking endlessly through the forums for my thread. I've done that before, not fun. LOL (Couldn't find a 'My Threads' thingy on the forum i was using.
Click to expand...
Click to collapse
Well, I guess to first start off, here's a few pointers:
1. don't put the title in 1337 (people will most likely not click on it, thus no help)
2. you're right about this being the wrong thread. You should post this under the Samsung Galaxy S section (google your model number and you'll see it instantly) and should probably try the Q&A moreso than a general area (but it doesn't really matter all too much)
3. no matter how nooblike you may or may not be, you're still a noob XD
Now that we've gotten past the anally parts and all (hate doing that, but gotta =P), let's talk about what you came here for: answers.
Let's start with some definitions:
ROMs - these are the (usually modded) softwares that you flash to your phone. Depending on which phone you have, you can only flash ROMs made for your phone. Of course, if you have root/custom recovery, you can also install custom ROMs.
ClockWorkMod (CWM) is a recovery system made in order to allow people more features while they're in recovery mode. Of course, this is one of a few out there, but people stick to CWM cause of its huge support plus it's popularity. When you think of CWM, think of custom features being installed in (almost) one step (modding files and such will be taken care of for you, so you don't have to do it yourself). You can usually also fix a bricked system this way by reflashing either the entire ROM or the boot.img/other files (we'll get to this in a second)
CyanogenMod (CM) is an example of a very popular custom rom. They have a great team and usually is available for most devices, which in turn makes them so popular. It is widely supported and has a lot of extra features like updating to the latest OS and features not previously available on your phone. It's skinned, but usually follows the stock Android look for the OS in which they've skinned.
lol The reason why the instructions look so simple is because they've taken out all the hard work and all the stuff where you can possibly screw up your phone, so that they don't get a million messages saying "OMG MY PHONE BRICKED WHAT HAPPENED" and stuff like that. Protects them, makes it easier for you. If you had made a backup before you flashed CM (usually you only have to back up whats on the phone if it has internal and external memory, but back up your sd card always just in case. never hurt to), then yes. If you backed it up with your previous ROM, then you'll probably need to revert to get it back. If you didn't, chances are whatever you didn't backup and didn't sync, is safe to say gone. You can try recovering it using a recovery software on the computer like i detailed here for another person, but of course you'd skip the whole trying to save the phone part and just start with mounting the phone to your computer and running the software.
CM is a custom rom, and so most (if not all) custom roms have root preinstalled (besides, who wouldn't want root?!) As for CWM, it works by being (usually) flashed into the recovery partition of your phone. The nice thing about the phone is that it's split up into parts: boot, recovery, system, and some other ones i can't think of off the top of my head. Those three are important, as if you get a softbrick, you might still be able to recover all your data simply by using CWM/fastboot (a dev-tool used to flash/unlock, but only available in certain phones, as it is disabled usually) to reflash the boot.img (one requires command line, whereas CWM only needs you to flash a created/pre-made package). Also, since they're in separate partitions, even if your system and boot.img doesn't work, you can probably still access recovery (unless you screwed up really REALLY bad, and in that case I can't help >.<)
Observant you are =] Yes, if you were to flash CM, your CWM will be gone (i don't understand why most people don't just bake it into the ROM in the first place) but, not all is lost. Just go back into the Android Market and redownload ROM Manager. Of course you'll need to open it up and flash the same exact recovery again (annoying, isn't it?) but unless you know how to mod zip/img files and edit the script, you'll just have to make do with that. If you do, you could just (usually) take out the recovery partition and just leave the one you have already in there (but its usually safer and better to just redownload/reflash it as annoying as it is). But yes, you would use CWM to flash it. It's as simple as "Install from SD Card" which is why custom recoveries like CWM are popular. So simple
At this point, I would look into a few things. One is skinning your phone (though you probably can't do too much if you don't want to touch system files). If you find a psuedo-rom (slightly modded) that themes it, that's your best bet. Another is gaining access to certain features in apps you didn't have before (i.e. androidLost, LBE Privacy Guard, titanium backup) and of course more control by the ability to control your system files (if you know what you're doing, of course). Lastly, you can use stuff like MetaMorph to theme out certain sections of your rom (provided that they give you one compatible with your phone model/rom), minus having to flash it and having more fine-tuned controlled. Usually, Metamorph will run on all ROMs, but it doesn't guarantee that there'll be stuff for every ROM. Also, want themes? google it (google is your best friend!)
Kies won't tell you that you have an upgrade because it is ROM-dependent. It looks for their official ROM and says "Hey, this guy has our ROM. Check for an update". Think of owning a custom rom like being kicked out of your family. You won't get anymore updates from them XD. However, if you're looking to get the latest updates, check out the Samsung Galaxy S Dev threads. They will usually have another method of loading in the new ROM into your phone. And if you want to stick with ROM Manager, shell out for premium and they'll include "Check for Updates" in ROM Manager, along with several other functions (though you can check for free via computer/browser ). Mostly, manually updating the software requires the "Install from SD Card" feature in CWM/other recoveries, so you don't have much to worry about.
Odin is, as you stated, most likely your best bet. Not too many people repackage official ROMs into easy-to-flash zips. Odin is the Samsung equivalent to Motorola's RSD Lite from what I googled (i have motorola, so no exp. on odin >.<) It's mostly like a dev tool allowing you to flash/re-flash phones and is also usually your one-way ticket out of a semi/full brick (assuming you didn't mess up the hardware and you can get into download mode). It's the flashing tool that can access the core system of the phone even without root and allows you to reflash OFFICIAL ROMs. Should you use Odin (should be your last resort), you WILL lose root and all your data. No questions asked. Its like reinstalling everything to the state in which you got it in when you bought the phone. Word of advice: BACK UP OFTEN! (did i forget to mention Titanium Backup? )
Yeah, the transition from Apple to Android is so different and had I not had experience with my PSP, i'd be dying with the information overload. However, just read a lot of stuff on the forums (*cough*general android forums*cough*) and you should be just fine. We have an excellent community here that will try our best to fix whatever problems you encounter (note the key word: try. we're not gods XD) You'll get the hang of it soon enough.
Oh, well, I don't want to keep you for much longer, but since you mentioned something that any noob should know, it's definitely ADB (Android Debugging Bridge). This is where you'll probably spend a lot of time, as people's fixes usually involve shell (terminal for your phone). If anything, get acquainted with it, as it might save your butt in the future/unlock a few extra features for you ;D .
Well, that's all i can think of, and honestly, after typing this thing up for about an hour now, I think I'm going to grab me some breakfast Good luck to you and welcome to the Android commmunity! (and next time, remember to post in the right place! XD)
~jojojohnson7410
P.S. PM me if you need anything. =]
Observant you are =] Yes, if you were to flash CM, your CWM will be gone (i don't understand why most people don't just bake it into the ROM in the first place) but, not all is lost. Just go back into the Android Market and redownload ROM Manager. Of course you'll need to open it up and flash the same exact recovery again (annoying, isn't it?) but unless you know how to mod zip/img files and edit the script, you'll just have to make do with that. If you do, you could just (usually) take out the recovery partition and just leave the one you have already in there (but its usually safer and better to just redownload/reflash it as annoying as it is). But yes, you would use CWM to flash it. It's as simple as "Install from SD Card" which is why custom recoveries like CWM are popular. So simple
Click to expand...
Click to collapse
Just to nit-pick a bit. CWM is part of the recovery partition, and unless the Galaxy S is different from every other android device, flashing will not remove it. ROM Manager and CWM are two different things. ROM manager will allow you to download the roms, which will then instruct CWM to flash the rom (when it reboots).
jojojohnson7410 said:
Well, I guess to first start off, here's a few pointers:
1. don't put the title in 1337 (people will most likely not click on it, thus no help)
2. you're right about this being the wrong thread. You should post this under the Samsung Galaxy S section (google your model number and you'll see it instantly) and should probably try the Q&A moreso than a general area (but it doesn't really matter all too much)
3. no matter how nooblike you may or may not be, you're still a noob XD
Now that we've gotten past the anally parts and all (hate doing that, but gotta =P), let's talk about what you came here for: answers.
Let's start with some definitions:
ROMs - these are the (usually modded) softwares that you flash to your phone. Depending on which phone you have, you can only flash ROMs made for your phone. Of course, if you have root/custom recovery, you can also install custom ROMs.
ClockWorkMod (CWM) is a recovery system made in order to allow people more features while they're in recovery mode. Of course, this is one of a few out there, but people stick to CWM cause of its huge support plus it's popularity. When you think of CWM, think of custom features being installed in (almost) one step (modding files and such will be taken care of for you, so you don't have to do it yourself). You can usually also fix a bricked system this way by reflashing either the entire ROM or the boot.img/other files (we'll get to this in a second)
CyanogenMod (CM) is an example of a very popular custom rom. They have a great team and usually is available for most devices, which in turn makes them so popular. It is widely supported and has a lot of extra features like updating to the latest OS and features not previously available on your phone. It's skinned, but usually follows the stock Android look for the OS in which they've skinned.
lol The reason why the instructions look so simple is because they've taken out all the hard work and all the stuff where you can possibly screw up your phone, so that they don't get a million messages saying "OMG MY PHONE BRICKED WHAT HAPPENED" and stuff like that. Protects them, makes it easier for you. If you had made a backup before you flashed CM (usually you only have to back up whats on the phone if it has internal and external memory, but back up your sd card always just in case. never hurt to), then yes. If you backed it up with your previous ROM, then you'll probably need to revert to get it back. If you didn't, chances are whatever you didn't backup and didn't sync, is safe to say gone. You can try recovering it using a recovery software on the computer like i detailed here for another person, but of course you'd skip the whole trying to save the phone part and just start with mounting the phone to your computer and running the software.
CM is a custom rom, and so most (if not all) custom roms have root preinstalled (besides, who wouldn't want root?!) As for CWM, it works by being (usually) flashed into the recovery partition of your phone. The nice thing about the phone is that it's split up into parts: boot, recovery, system, and some other ones i can't think of off the top of my head. Those three are important, as if you get a softbrick, you might still be able to recover all your data simply by using CWM/fastboot (a dev-tool used to flash/unlock, but only available in certain phones, as it is disabled usually) to reflash the boot.img (one requires command line, whereas CWM only needs you to flash a created/pre-made package). Also, since they're in separate partitions, even if your system and boot.img doesn't work, you can probably still access recovery (unless you screwed up really REALLY bad, and in that case I can't help >.<)
Observant you are =] Yes, if you were to flash CM, your CWM will be gone (i don't understand why most people don't just bake it into the ROM in the first place) but, not all is lost. Just go back into the Android Market and redownload ROM Manager. Of course you'll need to open it up and flash the same exact recovery again (annoying, isn't it?) but unless you know how to mod zip/img files and edit the script, you'll just have to make do with that. If you do, you could just (usually) take out the recovery partition and just leave the one you have already in there (but its usually safer and better to just redownload/reflash it as annoying as it is). But yes, you would use CWM to flash it. It's as simple as "Install from SD Card" which is why custom recoveries like CWM are popular. So simple
At this point, I would look into a few things. One is skinning your phone (though you probably can't do too much if you don't want to touch system files). If you find a psuedo-rom (slightly modded) that themes it, that's your best bet. Another is gaining access to certain features in apps you didn't have before (i.e. androidLost, LBE Privacy Guard, titanium backup) and of course more control by the ability to control your system files (if you know what you're doing, of course). Lastly, you can use stuff like MetaMorph to theme out certain sections of your rom (provided that they give you one compatible with your phone model/rom), minus having to flash it and having more fine-tuned controlled. Usually, Metamorph will run on all ROMs, but it doesn't guarantee that there'll be stuff for every ROM. Also, want themes? google it (google is your best friend!)
Kies won't tell you that you have an upgrade because it is ROM-dependent. It looks for their official ROM and says "Hey, this guy has our ROM. Check for an update". Think of owning a custom rom like being kicked out of your family. You won't get anymore updates from them XD. However, if you're looking to get the latest updates, check out the Samsung Galaxy S Dev threads. They will usually have another method of loading in the new ROM into your phone. And if you want to stick with ROM Manager, shell out for premium and they'll include "Check for Updates" in ROM Manager, along with several other functions (though you can check for free via computer/browser ). Mostly, manually updating the software requires the "Install from SD Card" feature in CWM/other recoveries, so you don't have much to worry about.
Odin is, as you stated, most likely your best bet. Not too many people repackage official ROMs into easy-to-flash zips. Odin is the Samsung equivalent to Motorola's RSD Lite from what I googled (i have motorola, so no exp. on odin >.<) It's mostly like a dev tool allowing you to flash/re-flash phones and is also usually your one-way ticket out of a semi/full brick (assuming you didn't mess up the hardware and you can get into download mode). It's the flashing tool that can access the core system of the phone even without root and allows you to reflash OFFICIAL ROMs. Should you use Odin (should be your last resort), you WILL lose root and all your data. No questions asked. Its like reinstalling everything to the state in which you got it in when you bought the phone. Word of advice: BACK UP OFTEN! (did i forget to mention Titanium Backup? )
Yeah, the transition from Apple to Android is so different and had I not had experience with my PSP, i'd be dying with the information overload. However, just read a lot of stuff on the forums (*cough*general android forums*cough*) and you should be just fine. We have an excellent community here that will try our best to fix whatever problems you encounter (note the key word: try. we're not gods XD) You'll get the hang of it soon enough.
Oh, well, I don't want to keep you for much longer, but since you mentioned something that any noob should know, it's definitely ADB (Android Debugging Bridge). This is where you'll probably spend a lot of time, as people's fixes usually involve shell (terminal for your phone). If anything, get acquainted with it, as it might save your butt in the future/unlock a few extra features for you ;D .
Well, that's all i can think of, and honestly, after typing this thing up for about an hour now, I think I'm going to grab me some breakfast Good luck to you and welcome to the Android commmunity! (and next time, remember to post in the right place! XD)
~jojojohnson7410
P.S. PM me if you need anything. =]
Click to expand...
Click to collapse
Wow, thanks a lot. I still have a question or two, bear with me.
Well for one, is flashing roms made for different firmwares alright, or no? Since I have 2.2, and im assuming the latest cyanogen is made for 3.x, would I have to upgrade my firmware to the corresponding firmware.
And about Clockwork, if my phone bricks, I'd have to restore using odin, right? But if the phone still works, i can just root and cwm and restore it using rom manager?
And uh, I'm not sure if this is a problem or im just doing something wrong, but in RomManager, i click Backup Current ROM, and it goes into recovery mode, and theres no new options, there's just like, format, factory reset, clear cache, reboot, but nothing involving rom manager. And when i check for the recovery file in my sd card, it's not. Wut do.
WoZZeR999 said:
Just to nit-pick a bit. CWM is part of the recovery partition, and unless the Galaxy S is different from every other android device, flashing will not remove it. ROM Manager and CWM are two different things. ROM manager will allow you to download the roms, which will then instruct CWM to flash the rom (when it reboots).
Click to expand...
Click to collapse
lol true true that would be my mistake. XD Nice catch
~jojojohnson7410
Gutana said:
Wow, thanks a lot. I still have a question or two, bear with me.
Well for one, is flashing roms made for different firmwares alright, or no? Since I have 2.2, and im assuming the latest cyanogen is made for 3.x, would I have to upgrade my firmware to the corresponding firmware.
Click to expand...
Click to collapse
No, you wouldn't have to upgrade to the latest firmware to get the ROM installed. So long as the ROM is confirmed to work for your device, you can flash any ROM you want (which is convenient in my case since I have an Atrix 4G and it was oh-so-lonely without some Gingerbread XD)
Gutana said:
And about Clockwork, if my phone bricks, I'd have to restore using odin, right? But if the phone still works, i can just root and cwm and restore it using rom manager?
Click to expand...
Click to collapse
Well, the thing is, you really only need that usually if you're on a stock rom or some official version and either you want to flash a new stock ROM from Samsung or you want to pull your phone out of a brick. Most of the time, however, even if you bricked it, so long as you can get into the recovery menu, you'll be alright. Just re-flash the ROM that you want (or in my case yesterday when I was dealing with an Inspire, I had to use a different ROM to unbrick the phone. I don't know why this happen, but it was being nit-picky >.<)
Gutana said:
And uh, I'm not sure if this is a problem or im just doing something wrong, but in RomManager, i click Backup Current ROM, and it goes into recovery mode, and theres no new options, there's just like, format, factory reset, clear cache, reboot, but nothing involving rom manager. And when i check for the recovery file in my sd card, it's not. Wut do.
Click to expand...
Click to collapse
lol nooo this is not a problem at all. See, like the guy above me posted, the Recovery Menu is completely separate from anything in the ROM. It's located in the recovery partition rather than the system and the boot partitions, so they usually don't touch the recovery. ROM Manager is just a means of providing GUI to CWM so then you can either flash the CWM to your phone or help download ROMS into your SD card. Stuff like backup and everything needs you to boot into recovery as you can't be backing up the system while your system is mounted on, so they send you to CWM. From there, there's an option called "backup and restore". In this place, you can choose where to save the backup. And since the backup is made by CWM, it will be recognized by CWM if you want to restore it. I think it saves it in a zip file, but im not 100% positive, so take that one with a grain of salt.
Hope this answers the questions! Let me know if you need more help (or just PM me. I check that regularly )
~jojojohnson7410
jojojohnson7410 said:
No, you wouldn't have to upgrade to the latest firmware to get the ROM installed. So long as the ROM is confirmed to work for your device, you can flash any ROM you want (which is convenient in my case since I have an Atrix 4G and it was oh-so-lonely without some Gingerbread XD)
Well, the thing is, you really only need that usually if you're on a stock rom or some official version and either you want to flash a new stock ROM from Samsung or you want to pull your phone out of a brick. Most of the time, however, even if you bricked it, so long as you can get into the recovery menu, you'll be alright. Just re-flash the ROM that you want (or in my case yesterday when I was dealing with an Inspire, I had to use a different ROM to unbrick the phone. I don't know why this happen, but it was being nit-picky >.<)
lol nooo this is not a problem at all. See, like the guy above me posted, the Recovery Menu is completely separate from anything in the ROM. It's located in the recovery partition rather than the system and the boot partitions, so they usually don't touch the recovery. ROM Manager is just a means of providing GUI to CWM so then you can either flash the CWM to your phone or help download ROMS into your SD card. Stuff like backup and everything needs you to boot into recovery as you can't be backing up the system while your system is mounted on, so they send you to CWM. From there, there's an option called "backup and restore". In this place, you can choose where to save the backup. And since the backup is made by CWM, it will be recognized by CWM if you want to restore it. I think it saves it in a zip file, but im not 100% positive, so take that one with a grain of salt.
Hope this answers the questions! Let me know if you need more help (or just PM me. I check that regularly )
~jojojohnson7410
Click to expand...
Click to collapse
But theres no backup and restore options, its jut the recovery options you'd get if you were on a brand new phone.
I have a Wacom Cintiq Companion Hybrid ( DTH-A1300L ) android version needs help in so many ways. I bought it because I really need one for one of my jobs, yet can't really afford the crazy overpriced insanity that is a new Wacom so the reason it was so cheap was "can't connect to the Play Store. I know, hella foolish, I thought I could fix it by rooting it, but this thing is like level 10 as there is so little info as no one wanted to touch them it seems. I did find one guy on this forum that at one point rooted I am fair to average at rooting and the understanding of all that surrounds it. I have happily and successfully rooted my phones and tablet but I am no pro and fairly good at having gaping invisible holes in my info or logic when it comes to things like this.
Most frustrating is this thing is stuck on android 4 . 1 . 1 for no good reason I can imagine. It has dev tools installed after factory data reset but no google apps. (It arrived factory data reset)
I tried the relevant framework and store and the delete the cache trick to no avail. It can not update and can not even get to the Play Store.
Sooo the bad news is; no Google apps. No updates offered and stuck on some weird what looks like not stock version of 4 .1 .1 Jellybean.
When I plug it into my PC via USB it does not even show up in device manager.
The good news is I rooted it. Checked with root checker (unfortunately for now its Kingroot)
1. I have no idea how to make a back up from here. (no USB connection to PC issue)
or
2. what rom will work as my device is not listed on any of them. It would be great to find the stock rom as I am afraid this things cool and weird cintiq mode, pen function like abilities may be disabled or rendered useless with just any android rom.
Is there anyway to somehow find the stock OS on my device through boot loader? A place to find my stock or like rom. A clever work around?
Thanks in advance. for any who take up the challenge and offer any help or thoughts.
Cheers
Anyone know
What clockwork or custom recovery should I use?
Duende101 said:
I have a Wacom Cintiq Companion Hybrid ( DTH-A1300L ) android version needs help in so many ways. I bought it because I really need one for one of my jobs, yet can't really afford the crazy overpriced insanity that is a new Wacom so the reason it was so cheap was "can't connect to the Play Store. I know, hella foolish, I thought I could fix it by rooting it, but this thing is like level 10 as there is so little info as no one wanted to touch them it seems. I did find one guy on this forum that at one point rooted I am fair to average at rooting and the understanding of all that surrounds it. I have happily and successfully rooted my phones and tablet but I am no pro and fairly good at having gaping invisible holes in my info or logic when it comes to things like this.
Most frustrating is this thing is stuck on android 4 . 1 . 1 for no good reason I can imagine. It has dev tools installed after factory data reset but no google apps. (It arrived factory data reset)
I tried the relevant framework and store and the delete the cache trick to no avail. It can not update and can not even get to the Play Store.
Sooo the bad news is; no Google apps. No updates offered and stuck on some weird what looks like not stock version of 4 .1 .1 Jellybean.
When I plug it into my PC via USB it does not even show up in device manager.
The good news is I rooted it. Checked with root checker (unfortunately for now its Kingroot)
1. I have no idea how to make a back up from here. (no USB connection to PC issue)
or
2. what rom will work as my device is not listed on any of them. It would be great to find the stock rom as I am afraid this things cool and weird cintiq mode, pen function like abilities may be disabled or rendered useless with just any android rom.
Is there anyway to somehow find the stock OS on my device through boot loader? A place to find my stock or like rom. A clever work around?
Thanks in advance. for any who take up the challenge and offer any help or thoughts.
Cheers
Anyone know
What clockwork or custom recovery should I use?
Click to expand...
Click to collapse
Greetings and welcome to assist. If you have root yoy can try installing gapps through flashify it may work. For custom rom there is an excellent guide here
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
and for custom recovery an excellent guide here
https://forum.xda-developers.com/android/software/guide-how-to-compile-twrp-source-step-t3404024
Good luck
Sawdoctor
sawdoctor said:
Greetings and welcome to assist. If you have root yoy can try installing gapps through flashify it may work. For custom rom there is an excellent guide here
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
and for custom recovery an excellent guide here
https://forum.xda-developers.com/android/software/guide-how-to-compile-twrp-source-step-t3404024
Good luck
Sawdoctor
Click to expand...
Click to collapse
Thanks, I will see what I can find out and report back. Also editing from device to check date
sawdoctor said:
Greetings and welcome to assist. If you have root yoy can try installing gapps through flashify it may work. For custom rom there is an excellent guide here
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
and for custom recovery an excellent guide here
https://forum.xda-developers.com/android/software/guide-how-to-compile-twrp-source-step-t3404024
Good luck
Sawdoctor
Click to expand...
Click to collapse
Excuse my noobness. Flashify looks good, I installed it, but don't I need some image from somewhere either the stock OS or a new one for it to work? Not sure how to get Gapps from there.
It did I think, find something, a "restore kernel" and "stock recovery" I am unsure did it find my stock kernel and recovery and or ROM and I should boot from that? ( again apologies a-lot of new info and its getting a bit swirly) In otherwords since my device is not listed any where and at this point any working Android version will do, I am wrong to try and reboot from this? These devices are supposed to come stock on 4.2.2, so I am hoping perhaps incorrectly it will go back to that? That would be ideal at this point.
So I can work again whatever works.
Also I a bit concerned about the "date" I posted from on one of these. I think I posted from the Wacom. Perhaps the problem in deeper than I thought as that is Linux time 0?
I think it self corrected but originally it said I posted on Jan 1 1970...
As for custom ROM, I probably wont be able to make my own custom ROM, even though I would love to take to the time to learn, for now I have too many art and work related deadlines.
I was hoping for one that already existed that would work with my device.
Perhaps I misunderstood something about how all this works? Also I do not have Unbuntu. I should as I support an open internet, but WINE really does not run the Adobe products I need for work so
I am stuck with Windows.
Duende101 said:
Excuse my noobness. Flashify looks good, I installed it, but don't I need some image from somewhere either the stock OS or a new one for it to work? Not sure how to get Gapps from there.
It did I think, find something, a "restore kernel" and "stock recovery" I am unsure did it find my stock kernel and recovery and or ROM and I should boot from that? ( again apologies a-lot of new info and its getting a bit swirly) In otherwords since my device is not listed any where and at this point any working Android version will do, I am wrong to try and reboot from this? These devices are supposed to come stock on 4.2.2, so I am hoping perhaps incorrectly it will go back to that? That would be ideal at this point.
So I can work again whatever works.
Also I a bit concerned about the "date" I posted from on one of these. I think I posted from the Wacom. Perhaps the problem in deeper than I thought as that is Linux time 0?
I think it self corrected but originally it said I posted on Jan 1 1970...
As for custom ROM, I probably wont be able to make my own custom ROM, even though I would love to take to the time to learn, for now I have too many art and work related deadlines.
I was hoping for one that already existed that would work with my device.
Perhaps I misunderstood something about how all this works? Also I do not have Unbuntu. I should as I support an open internet, but WINE really does not run the Adobe products I need for work so
I am stuck with Windows.
Click to expand...
Click to collapse
If you just want to be able to install apps from the playstore then this is a simple alternative
https://www.xda-developers.com/unshackle-your-device-from-the-google-play-store-with-apkupdater/
If your phone is rooted then flashify can flash zips like gapps without the need for a custom recovery. If you are serious about trying to make your own rom/recovery then use a virtualbox in windows. http://www.osboxes.org/ has plenty of prebuilt virtual linux machines that will run on windows
Regards
Sawdoctor
I appreciate all your help. I got the "google of every kind from Gapps on has stopped" is over, which was intense as it popped up every few seconds, I somehow got that to quit by reloading the proper one from the APK Pure app which was an odd work around but nothing else was working. Still have this unsettling bare bones screen and none of the stock apps as well as it being stuck in 4.1.1. This device was made for 4.2. and I assume it was on here at one point.
I wonder if that alone could cause hardware issues. I thought about taking out the battery, until I realized that thing is inaccessible as a thing can be without wrecking the industrial glues and taking the entire thing apart which sounds
like an accident waiting to happen and possible making things worse. I imagine that is last case scenario.
Like I said I would love to make my stock reload, at this point that would be great as this thing seems unstable and no trick makes the play store work or allow me to sign into the device with my google email.
I think you are saying to make my own recovery/ROM of my own device I need to do the virtual box thing. Correct? Or is that for writing your own custom ROM? I can try that; make my own recovery that is, as it is not on CWM or TWRPs supported devices list so I have no choice and all in all would prefer the thing to load as if it was fresh out of the box not this 4.1. One serious hiccup I have found trying to use my PC is my device is not recognized as a storage device or otherwise. Not sure if this is due to the weird settings of Cintiq mode or simply because the thing is in a very weird state of 4.1.1. So that may make making changes via computer impossible. I am not the type to give up. Thanks again Saw
Here also is a sum up I added to a the just basic question of Can you find the Stock from a recovery device. Basically is there any way to return a device to stock with no ROMs available to do so, as in extract if from the device itself.
Additional backstory if helpful.
"I have a Wacom Cintiq Hybrid running Android 4.1 that is ( now ) rooted..
This is a very bad thing. The Real Stock ROM has palm rejection and all the drivers to make it work as a tool. So stock is the ideal but it is clearly not stock as my device supposedly came in the
box running 4.2 and with software and drivers to make it work properly with the pen. This has nothing. No software and the smallest amount of apps possible. Worse this is no custom ROM its on ( I think) as it would be the worst one ever and it was not rooted on arrival. I have no idea what happened before I got it. I may have made the mistake of rooting it really as I found out to my dismay there is no ROM support. So back to square one. I bought it ( very cheap for one of these ) "stuck and unable to go to the play store" and I did not realize until I got it, on a version of Android it was not meant for. Wacom is totally and woefully unhelpful in every way. They seem to want to quietly put this device behind them at the expense literally of their customers."
Picked up an AT&T Radiant Core for cheap at a store around me. I don't intend to use it with AT&T, it was just such a low price that I figured I'd get it and see if I can break into it just for fun. It's an MTK6739 chipset phone, so in theory it should be easy to pull partitions from this thing with something like SPFT (or Miracle Box, if you paid for it) and do a dirty port of TWRP to get root privileges on it. But this is harder than it seems.
I need an auth file to do anything with SPFT. Apparently this has to do with some kind of "secure boot" mechanism that MediaTeks sometimes have now. There's no stock firmware for this device online from what I can find, nor for the generic version of the device, the Tinno U304AA (AT&T just rebranded it). If I had a stock firmware image, maybe I could risk wiping the partitions and reflashing the stock firmware to get rid of the secure boot stuff.
I saw a guide for how to access the bootloader on the Tinno U304AA generic version, but on the AT&T version of the phone there's no option in the boot select menu (Vol. UP + Power) to get to the bootloader to run a fastboot oem unlock. All the AT&T version has is recovery and normal boot. I'm not sure what I can do to maybe reset this to get the other options. Maybe if I had the stock firmware for the generic version of the phone I could overwrite it and get access to those other options.
Either way, just posting this up for anyone else that got one of these and wants to collaborate/contribute. Maybe with enough collective brainpower we can make something happen.
UPDATE: found a stock system image dump, thank you to @lopestom for directing me to this. This guy's been the MediaTek king for as long as I can remember.
It appears to be a dtbo and system partition dump. It also has the vendor partition and a (partial?) boot image dump. Not sure if things like the full boot and recovery images are stored somewhere in here, I didn't look too deeply into it yet. I have no idea how whoever this is managed to pull these partitions... they either got root access somehow, or they found a proper Download Agent and Auth file to pull it all. Either one of these would be awesome. I reached out to the user to ask them how they did it, we will see what they say if they want to share how they did it.
https://git.rip/dumps/att/u304aa
jasonmerc said:
Picked up an AT&T Radiant Core for cheap at a store around me. I don't intend to use it with AT&T, it was just such a low price that I figured I'd get it and see if I can break into it just for fun. It's an MTK6739 chipset phone, so in theory it should be easy to pull partitions from this thing with something like SPFT (or Miracle Box, if you paid for it) and do a dirty port of TWRP to get root privileges on it. But this is harder than it seems.
I need an auth file to do anything with SPFT. Apparently this has to do with some kind of "secure boot" mechanism that MediaTeks sometimes have now. There's no stock firmware for this device online from what I can find, nor for the generic version of the device, the Tinno U304AA (AT&T just rebranded it). If I had a stock firmware image, maybe I could risk wiping the partitions and reflashing the stock firmware to get rid of the secure boot stuff.
I saw a guide for how to access the bootloader on the Tinno U304AA generic version, but on the AT&T version of the phone there's no option in the boot select menu (Vol. UP + Power) to get to the bootloader to run a fastboot oem unlock. All the AT&T version has is recovery and normal boot. I'm not sure what I can do to maybe reset this to get the other options. Maybe if I had the stock firmware for the generic version of the phone I could overwrite it and get access to those other options.
Either way, just posting this up for anyone else that got one of these and wants to collaborate/contribute. Maybe with enough collective brainpower we can make something happen.
Click to expand...
Click to collapse
OMG! So excited to see this here! My Mom gave my nephew this phone and niece has one. So I've been trying my best to get the thing to at least be a decent phone! I installed a launcher on it, changed the icons and wallpaper and made it look good at least. It will be nice to have someone to talk to about this. The thing has been beyond frustrating! First off though how did you get the computer to recognize it? I can't get Windows or Linux to recognize it and couldn't find any drivers. If you managed that much you got further than I did. I haven't tried with my nieces though. It might just be his phone. She's 13 so it took awhile to pry it from her long enough to find out what kind it was, but I'm willing to try to get it from her once again if the phone can be improved.
sjjtnj said:
OMG! So excited to see this here! My Mom gave my nephew this phone and niece has one. So I've been trying my best to get the thing to at least be a decent phone! I installed a launcher on it, changed the icons and wallpaper and made it look good at least. It will be nice to have someone to talk to about this. The thing has been beyond frustrating! First off though how did you get the computer to recognize it? I can't get Windows or Linux to recognize it and couldn't find any drivers. If you managed that much you got further than I did. I haven't tried with my nieces though. It might just be his phone. She's 13 so it took awhile to pry it from her long enough to find out what kind it was, but I'm willing to try to get it from her once again if the phone can be improved.
Click to expand...
Click to collapse
Linux should just work, plug in the thing and the "drivers" if you will should be there already. Check the phone's settings for USB Debugging in the Developer Options if there's further trouble.
Don't get me wrong too, this phone is, was, and will always be a piece of junk. There's no getting around a screen this bad and 1GB of RAM. I'm actively trying to find a Download Agent and Auth File combo to get this thing to work with SPFT so I can try to port a custom recovery to get us Magisk root permissions at least. Root will make the phone slightly better, but it will still be junk. Unless we can get kernel source for it as well to mess with things like clock speeds and CPU governors (which LEGALLY we are supposed to be guaranteed, but good luck convincing a Chinese company to give it to you) everything we do, if we CAN do anything, will be like deodorant on a turd. It'll smell a little better, but it's still a turd.
jasonmerc said:
Linux should just work, plug in the thing and the "drivers" if you will should be there already. Check the phone's settings for USB Debugging in the Developer Options if there's further trouble.
Don't get me wrong too, this phone is, was, and will always be a piece of junk. There's no getting around a screen this bad and 1GB of RAM. I'm actively trying to find a Download Agent and Auth File combo to get this thing to work with SPFT so I can try to port a custom recovery to get us Magisk root permissions at least. Root will make the phone slightly better, but it will still be junk. Unless we can get kernel source for it as well to mess with things like clock speeds and CPU governors (which LEGALLY we are supposed to be guaranteed, but good luck convincing a Chinese company to give it to you) everything we do, if we CAN do anything, will be like deodorant on a turd. It'll smell a little better, but it's still a turd.
Click to expand...
Click to collapse
Right, I'm considering giving him my current phone when I get a new one. It doesn't seem like I'm going to be able to unlock and root it so I want a phone I can. Mainly for space personally. He's young so he doesn't need it rooted, but I'm thinking if I can root it then I might be able to use it to root my phone. Speaking of rooting I think I found a way to root this phone. It took me a couple days to get the phone since he said he couldn't find it, but I have it now. It just needs to charge, but the battery sucks so it takes forever. I did find out that it does have a decent recovery. I had booted it into recovery and then I was messing around with the keys after the little passed out green guy popped up and suddenly it loaded stock recovery. It had an option to mount the system and flash with adb and everything. The only problem is I kept booting it by messing with keys. So I honestly don't know which ones worked. I kept booting into it last night by messing with them, but now I can't seem to get it to boot into the right recovery now that I'm trying to figure out the right key combination. I will figure it out though (eventually) and let you know what you have to click, but if you get the chance just mess with it and hopefully you'll find it like I did.
Also I was looking up the phones variants and downloaded a couple stock roms that I felt had all the right specs I'm going to try to flash one if I can get it plugged in. I downloaded custom twrp image's for them as well, and even found one twrp that I was able to download in the app. If you used it then you know that it takes you to a download page if you are downloading the wrong twrp.img. So the fact it let me download it in the app meant it tricked twrp into thinking it was that phone. So I'm going to try that stock rom first. Maybe we'll be able to change it to another model. It really needs something flashed, because it's a mess. I thought he messed it up, but after reading what you said maybe it's just the phone. He's young so it doesn't matter as much to him, but I feel bad for my niece. I really need to look into at least getting her another phone. I'm going to work on it later today and see what I can do. First I got to get it to work on the computer, but I may be able to root it without the computer. I'll keep you updated with my progress.
any luck with this?
Yeh, is there a status update?
Sorry, I got a concussion and haven't been able to do much, but really I'm stuck because I can't get it to connect to the computer at all. Not in Windows or Linux. I think he's messed it up beyond repair at this point. The offline root gave me an error around the mounting of the system, but that can be done if you can get the recovery to show up. It's one of the options. I was trying this method. HERE see if you can get it plugged in and to work. Also, Kingoroot gets to 90% on the apk alone. So the computer app might do the trick. Then you can switch it to su. Really a rooted phone can get a lot done with apps like flashify and flashfire that we can't do right now. If you can get even a temp root let me know and I'll tell you what I found out about the apps to unlock the bootloader, flash TWRP, Flash Magisk, then flash ROMs. If you want to try the variant route I was trying then just do a search on google. Some sound just as bad, but other similar phones seem better. You can pick which one you want to try. The phone I have got to a point that it kept deleting applications and stuff on the phone and has trouble with the sd card. So I don't have the stuff I had saved on it anymore. I'm giving him my current phone when I get a new one. It's too messed up to salvage. I hope you have more luck.
sjjtnj said:
Sorry, I got a concussion and haven't been able to do much, but really I'm stuck because I can't get it to connect to the computer at all. Not in Windows or Linux. I think he's messed it up beyond repair at this point. The offline root gave me an error around the mounting of the system, but that can be done if you can get the recovery to show up. It's one of the options. I was trying this method. HERE see if you can get it plugged in and to work. Also, Kingoroot gets to 90% on the apk alone. So the computer app might do the trick. Then you can switch it to su. Really a rooted phone can get a lot done with apps like flashify and flashfire that we can't do right now. If you can get even a temp root let me know and I'll tell you what I found out about the apps to unlock the bootloader, flash TWRP, Flash Magisk, then flash ROMs. If you want to try the variant route I was trying then just do a search on google. Some sound just as bad, but other similar phones seem better. You can pick which one you want to try. The phone I have got to a point that it kept deleting applications and stuff on the phone and has trouble with the sd card. So I don't have the stuff I had saved on it anymore. I'm giving him my current phone when I get a new one. It's too messed up to salvage. I hope you have more luck.
Click to expand...
Click to collapse
I need to unlock my phone U304AA
Ok boys and girls, in case anyone is still wondering here is how to root this sucker.
https://drive.google.com/file/d/1--Ul1ae73zcejNuJ1a7ftq5sTo2VP8Ya/view?usp=drivesdk
Comes with two files. Mtksu amd magisk be sure to use the magisk version included in the zip. Install mtksu then wmagisk, open mtksu and install the top magisk option. Reboot then open magisk hit install when it asks. Now open mtksu scroll to the bottom and hit activate and reboot again. Should be good too go at this point. Oh yeah be sure to click apply at boot in mtksu. Not sure if this had been posted before or not. Now, to find a way to unlock bootloader and install twrp.
Thank you, I tried Mtksu on mine and it didn't work, but it might've been the phone. I don't have one of these anymore, but I hope you all the best of luck. For the bootloader and Twrp try Flashfire or flashify.
MTK bypass method released by some smart dudes out there. I will test if we can use SPFT on this phone now. Stay tuned. This could mean root & recovery in a matter of minutes.
EDIT: It ALMOST works. Technically it bypassed the auth file as advertised. The only thing left now is finding a compatible preloader/scatter file to use.
Used a modified Moto E6 Play scatter file to pull images from the device. Tried flashing over stuff and got an error. Long story short my U304AA is now permanently bricked, so I'm tapping out of this project here
I do have recovery and boot images that (supposedly) work if anyone else wants to try and take over Keep in mind these were pulled with a scatter file from a DIFFERENT phone that's of the same chipset, so not everything is guaranteed to work. For example, the preloader was pulled with the specified parameters but I do NOT know if it's functional
Because I'm tapping out, and because nobody else seems to have anything on this, I'm uploading everything I can. Some pulls are too big to upload and some just won't work for some reason, but use whatever you'd like for anything you can. Hope I did something helpful
I have searched in Google Search and the tutorials forum but not found a tutorial
_____________
Sent from my website: https://topsanphamhay.com/kem-chong-nang-danh-cho-da-dau-mun.html - https://topsanphamhay.com/kem-chong-nang-innisfree-perfect-uv-protection-cream-co-tot-khong.html - https://topsanphamhay.com/kem-chong...ifying-face-fluid-dry-touch-co-tot-khong.html using Iphone X
Well AT&T is giving away lots of Radiant Core devices because of their 3G shutdown: https://www.xda-developers.com/att-3g-shutdown-free-phone/
My wife and I just got one, so now I have two of these but I'm not sure I trust AT&T enough to use the "free" phone that they sent.
It would be great if someone can pickup this project, especially since so many phones are now flooding the market.
I just got 3 of these "free" from AT&T. In fact I don't really need them, I just happen to have phones with an IMEI number that AT&T cannot decipher, so they sent me new phones just in case I can't use 4G.
Anyway, I'm trying to use mine as spare Google assistants scattered around the house, but because they run that crappy Android Go, the Go version of Assistant won't listen to me until I long-press the home button. I would also like to use them when I travel as a spare.
These things are essentially throw-away, so I'm OK to risk bricking one of them.
What I really want to do is install a real version of Android on here, has anyone managed to crack this yet?
I personally have been writing and reading using this tool https://github.com/bkerler/mtkclient, which is much simpler than the others
Its a little rough around the edges, but it certainly works
My final problem is disabling secure boot (I already have a boot.img patched with magisk)
It appears that fastboot is simply not a mode for booting on this model, so I was wondering if anyone knows how to disable AVB by hand with just partition images
kayshinonome said:
I personally have been writing and reading using this tool https://github.com/bkerler/mtkclient, which is much simpler than the others
Its a little rough around the edges, but it certainly works
My final problem is disabling secure boot (I already have a boot.img patched with magisk)
It appears that fastboot is simply not a mode for booting on this model, so I was wondering if anyone knows how to disable AVB by hand with just partition images
Click to expand...
Click to collapse
if it's possible to downgrade the firmware to before the october 2019 patch, it might be possible to mtk-su the device: https://www.att.com/device-support/article/wireless/KM1376142/ATT/ATTU304AA
might be another alternative to trying to disable avb on a locked bootloader
luridphantom said:
if it's possible to downgrade the firmware to before the october 2019 patch, it might be possible to mtk-su the device: https://www.att.com/device-support/article/wireless/KM1376142/ATT/ATTU304AA
might be another alternative to trying to disable avb on a locked bootloader
Click to expand...
Click to collapse
Not possible to do, already tried before when I didn't brick it
KJ7LNW said:
Well AT&T is giving away lots of Radiant Core devices because of their 3G shutdown: https://www.xda-developers.com/att-3g-shutdown-free-phone/
Click to expand...
Click to collapse
Just got mine from this. I'd like to install something like NixOS mobile, but I've never used an android phone before. Will that be possible on this phone? If so, is there a good guide for newbs like myself?