Related
Every since i updated to the latest rom via the HTC website, i noticed my phone info now says T-Mobile_LEO, what's up with that? NORMAL or what?
Plus SPB Backup also recognises it as not the same device i made a backup on although it is, even if i backup using the same rom it thinks it's different.
Other then this weird thing the entire phone works flawless, was just curious as to whats up.
Thanks for any input.
mine does this too because the energy rom im using based on a rom for the tmous..... must be the same sort of issue.
its nothing to worry about, shouldn't cause you any problems.
I wouldn't advise restoring your backup from an old rom to a new rom anyway in case there are any incompatibility issues....
Just tried to restore my backup from SPB Backup which was made on this phone and when i get to the restore part it states the phone is different from the one which i made the backup ?? Anyone with any ideas what's up here ?
Why does it say it's T-Mobile_Leo in the first place as the rom update was downloaded from HTC's own website.
Anyone else had this same problem ??
I backed up everything and now i can't restore it properly.
121man said:
Just tried to restore my backup from SPB Backup which was made on this phone and when i get to the restore part it states the phone is different from the one which i made the backup ?? Anyone with any ideas what's up here ?
Why does it say it's T-Mobile_Leo in the first place as the rom update was downloaded from HTC's own website.
Anyone else had this same problem ??
I backed up everything and now i can't restore it properly.
Click to expand...
Click to collapse
First, you should only use SPB Backup to restore to the SAME ROM as was backed up. Otherwise you will have trouble. Not might, will.
You have to select the Force ROM Upgrade mode, and then just before the restore, check the options and select ROM upgrade. Then it should work.
Hi there,
Well, I just got my HD2 back from repairs, where they replaced the mainboard. The ROM seems to be the same, 3.14, but the phone ID is showing as T-Mobile_LEO. When I restored using SPB backup, it said the ROM was different though. What is going on here?
Thanks,
David
I can't figure it out either, exact same thing but my one happened with the rom update.
Weird.
Do some of you guys use Swype?
If yes, the naming of your device is "normal", Swype wouldn´t run with the "normal" naming.
Afaik, the Swype cab installs a certain file into the Windows folder.
If you remove it, the name would be normal, but Swype won´t run correctly.
Ahh. I use swype, I did not know it actually renames the device.
That actually makes sense.
Thanks for this finally cleared up now.
Brilliant.
Find myself in an odd predicament I may not be able to solve.
The LCD digitizer on my Fascinate went out, taking the screen with it. When it had started happening, I was using Powerwashed GB rom, on Clockwork Mod 3.0x. I had a previous backup, and made another one as well, and both worked fine when restoring to that phone.
I received the replacement, and assumed it'd be as simple as re-ODINing clockwork Mod, and then restoring the backup. Neither worked. So, I had a lot of my apps back up with Titanium, no problem, but I lost my version of Swype. I was one of I guess the lucky few who managed to grab the full version of the Nexus S Swype release before it got pulled. It exists in those backups, but I can't restore them, and the release isn't readily available anymore.
I've looked into extracting the .img files and finding both the Swype.apk and libswypecore.3.25.91.30637.so files to manually readd them, but seem to be at a brick wall as far as getting into them.
Any solutions, or am I just kicking a dead horse?
t_buzz said:
Find myself in an odd predicament I may not be able to solve.
The LCD digitizer on my Fascinate went out, taking the screen with it. When it had started happening, I was using Powerwashed GB rom, on Clockwork Mod 3.0x. I had a previous backup, and made another one as well, and both worked fine when restoring to that phone.
I received the replacement, and assumed it'd be as simple as re-ODINing clockwork Mod, and then restoring the backup. Neither worked. So, I had a lot of my apps back up with Titanium, no problem, but I lost my version of Swype. I was one of I guess the lucky few who managed to grab the full version of the Nexus S Swype release before it got pulled. It exists in those backups, but I can't restore them, and the release isn't readily available anymore.
I've looked into extracting the .img files and finding both the Swype.apk and libswypecore.3.25.91.30637.so files to manually readd them, but seem to be at a brick wall as far as getting into them.
Any solutions, or am I just kicking a dead horse?
Click to expand...
Click to collapse
there is a special nexus s version of swype?
I found no Swype on CM7/vanilla gingerbread, so I signed up for the swype beta at swype's website and I got the latest [which was way newer than what my Stock rom has] beta, and it works great.
When i would restore from a nandroid back up i would always flash the rom first.
Try flashing Power washed again then restore nandroid.
Titanium now supports extracting apps from cwm backups.
Sent from my SCH-I500
Domush, thank you for that, got it up and running.
mvmacd, the Nexus S version contains a Sprint skin for Swype that is, in my opinion, the best keyboard I've ever used.
Going to try rooting my P1000L Galaxy Tab, I want to back it up first, what is the best way to do this? Being completely new at this, I want to have my Tab fully backed up so I can restore in case something goes wrong.
Short question, Whats the best way to fully back up my Galaxy Tab?
Thanks in advance for any help on this.
BajaCapt said:
Going to try rooting my P1000L Galaxy Tab, I want to back it up first, what is the best way to do this? Being completely new at this, I want to have my Tab fully backed up so I can restore in case something goes wrong.
Short question, Whats the best way to fully back up my Galaxy Tab?
Thanks in advance for any help on this.
Click to expand...
Click to collapse
IF you have CWM then make a full nandroid backup else , install TitaniumBAckup from market and backup all.
Do note that Titanium backup does not backs ur system files
Thank you for your response, it gave me a direction for reading into.
I dont have CWM installed and to be honest I did not even know what it was, I did a search a read a bit on it and it sounds very good, I assume I must have a rooted ROM to install it right? So I think I will try purchasing Titanium BackUp, I see there is a free version, I wonder if I should get the paid version, got to read on that.
While researching CWM I read that all Android devices ship with a recovery console, albeit with limited functions, this is good to know, if worst comes to worst and me as a newb to this make a mistake I could recover with the stock recovery console right?
Thanks again for your help, I do hate being a newb, I do learn fast and I am fairly good with all electronics,PCs, laptops etc, I will learn Android dammit lol
bala_gamer said:
IF you have CWM then make a full nandroid backup else , install TitaniumBAckup from market and backup all.
Do note that Titanium backup does not backs ur system files
Click to expand...
Click to collapse
As it turns out I cannot use either one, CWM or Titanium BackUp, they both require root Looks like I am back to where I started, I need to root GB 2.3.6 which to a newb is a bit of a pain...
Hello,
It would be great if someone could help me out.
I have spent the whole day trying to find out if it is possible to create a flashable rom from an already running and setup android device.
I have found many tutorials on how to create roms from scratch, but can't seem to find a way to do it from an already running android device.
I already have an android device setup with all the apps, settings and files I want in the rom. I wondered if there was a way to use my Windows system to create a flashable rom from this device which I can then use to setup/flash new devices.
I hope that makes sense.
Thanks for your time.
Hi there, i am curious as well if this is possible.
I have to set up about 1600 Samsung S5 mini phone's for a customer. Almost al the setting, apps en stuf are identical so i would also like to create a flashable rom / image from one phone so we can install it to the other 1599 phones
Thanx in advance.
steefzz said:
Hi there, i am curious as well if this is possible.
I have to set up about 1600 Samsung S5 mini phone's for a customer. Almost al the setting, apps en stuf are identical so i would also like to create a flashable rom / image from one phone so we can install it to the other 1599 phones
Thanx in advance.
Click to expand...
Click to collapse
Hi,
From what I have read online if you are wanting to do this for a phone you can do a nandroid backup. I have just found a number of guides on how to do this with phones. If you search this forum for nandroid backup you will find them. Hope that helps you steefzz.
I am actually trying to clone TV box with all apks installed and configured. I can see how I can package apks into a rom, but they won't have all addons and settings saved. This is why I was hoping for a way to clone the entire device to restore onto future devices.
Ideally i don't even want to have to power up the devices, I would like to plug them into my PC apply the cloned rom and that's it.
If anyone has an idea of how to do that without having to pre-install any recovery or software onto the devices, or even power them up before hand ( they are already rooted) that would be great.
Thanks again.
sym0n said:
Hi,
From what I have read online if you are wanting to do this for a phone you can do a nandroid backup. I have just found a number of guides on how to do this with phones. If you search this forum for nandroid backup you will find them. Hope that helps you steefzz.
I am actually trying to clone TV box with all apks installed and configured. I can see how I can package apks into a rom, but they won't have all addons and settings saved. This is why I was hoping for a way to clone the entire device to restore onto future devices.
Ideally i don't even want to have to power up the devices, I would like to plug them into my PC apply the cloned rom and that's it.
If anyone has an idea of how to do that without having to pre-install any recovery or software onto the devices, or even power them up before hand ( they are already rooted) that would be great.
Thanks again.
Click to expand...
Click to collapse
Hi,
Thanks for your reply.
With a nandroid backup it wil indeed kind of work out how i want, however when i want to restore a backup to the phone, the backup has to be in \TWRP\BACKUPS\<PhonIdNr>
The Phone Id number is unique and before i can restore a backup, i first have to make a small backup to create these folders.
Also i am expected to write a manual so that other collegaes can also do this procedure. For me it's no problem (i'm using custom roms for about 5 years now with different brands) however most of my collegeas are not known with these methods to restore a nandroid.
So i was experimenting with the creation of a own made custom rom . For now it partially worked. I managed to make a flashable zipfile. However it only work is i dont install the /data folder. If i only install the /system folder it works fine, only i have to maken al bunch of manual setting. When i also install the /data folder the phone is stuck at boot logo, when i then full wipe i, it will boot again.
So i actually would like to maken a flashable zip or an Odin flashable tar that also contains (some) /data.
Is this even possible?
As you know TWRP on our phones allows us to instantly switch between ROMs, backup, etc. instantly. It's like an image based backup for our android devices. And exceptionally handy when wanting to try out different ROMS (Firmware here I guess). I have TWRP recovery installed and I was able to get it to see my nandroid online TWRP backup. I had to run a backup in twrp to see the directory it wanted as It would not let me specify the directory. Turns out it is /mnt/external_sd/TWRP/BACKUPS/n70 for my device when choosing the external option. So I went ahead and confirmed the format of that backup is the same as the online nandroid TWRP backup and it is (mtd.win, ext4.win) so I went ahead and moved boot, cache, data, kernel, and system to that n70 directory. Beautiful TWRP recovery sees them! Making progress, I think. (See pic)
Then I go to restore this and I am met with "Unable to wipe data using function call". FAIL! Anyone have any idea what I may be able to do to make this work? I did check permissions of the TWRP backup directory to ensure all was well and it was. Perhaps TWRP doesn't have access to write to /data? I doubt that, perhaps this is an easy fix and TWRP can actually work well on these devices?
NOTE, you cannot backup from TWRP recovery as it shows /data as 0MB. Which may be part of the reason I get an error during TWRP restores?
Dave
Lets hope one of the dev's pick this up as this would be a great addition to help make life easier!
I agree. I couldn't even decompile the recovery. I fail!!
Dave
so nobody has any desire for this to work?
I pushed for having a working TWRP when these units first came out. The issue is none of the ROM makers have had the desire to move to this type of system for releasing ROMs, so all updates to the ROM force you to flash back the factory recovery to update you ROM, which makes it a PIA anytime you want to update.
fortunately the flash back to stock recovery is easy but twrp is so nice im surprised they aren't wanting to move to it. The backup/restore functionality is amazing as well.
Dave
I would love for them to goto this style of updating as it would make upgrades so much easier as well as could use things like Aroma Installer to keep me from having to nuke half the apps I do not use with Titanium Backup. For example the only stock apps I use are Bluetooth and Radio. And most of the other crap found in the latest roms, I kill as well as I do not use them.
I am so down for this! Would definitely donate to make it happen. Promise. Ask @Malaysk
as would I.
I also like to pay with PayPal ready
TT_Vert said:
As you know TWRP on our phones allows us to instantly switch between ROMs, backup, etc. instantly. It's like an image based backup for our android devices. And exceptionally handy when wanting to try out different ROMS (Firmware here I guess). I have TWRP recovery installed and I was able to get it to see my nandroid online TWRP backup. I had to run a backup in twrp to see the directory it wanted as It would not let me specify the directory. Turns out it is /mnt/external_sd/TWRP/BACKUPS/n70 for my device when choosing the external option. So I went ahead and confirmed the format of that backup is the same as the online nandroid TWRP backup and it is (mtd.win, ext4.win) so I went ahead and moved boot, cache, data, kernel, and system to that n70 directory. Beautiful TWRP recovery sees them! Making progress, I think. (See pic)
Then I go to restore this and I am met with "Unable to wipe data using function call". FAIL! Anyone have any idea what I may be able to do to make this work? I did check permissions of the TWRP backup directory to ensure all was well and it was. Perhaps TWRP doesn't have access to write to /data? I doubt that, perhaps this is an easy fix and TWRP can actually work well on these devices?
NOTE, you cannot backup from TWRP recovery as it shows /data as 0MB. Which may be part of the reason I get an error during TWRP restores?
Dave
Click to expand...
Click to collapse
AFAIK its already been done, a year or 2 ago.
If I remember correctly it was working but it wasnt compatible with the way the MTCB updates work or something, did you search the original thread ?
Whilst I use TWRP on my phone I never tried it on my head unit or saw the need for it personally.
@Dees_Troy or @Captain_Throwback are the only guys I know capable of doing it. Maybe if they could give a hand. I have attached the 800x480 5.1 recovery if they would be so kind.
The wiki says its "now working perfectly" and gives a link to TWRP for Rockchip devices in a Freaktab post from 2014.
As I said earlier I m sure there was some reason why not many people use it, possibly to do with not being able to flash the MCU in TWRP or something.
Has anyone actually searched the original thread yet ? (theres only 11 pages to read through if you search "TWRP").
typos1 said:
The wiki says its "now working perfectly" and gives a link to TWRP for Rockchip devices in a Freaktab post from 2014.
As I said earlier I m sure there was some reason why not many people use it, possibly to do with not being able to flash the MCU in TWRP or something.
Has anyone actually searched the original thread yet ? (theres only 11 pages to read through if you search "TWRP").
Click to expand...
Click to collapse
Can you link me to the wiki? the only one i could find was the huifei one with no info re twrp
are you referring to http://freaktab.com/forum/main-category/freaktab-downloads/11780-twrp-2-7-0-0-for-rockchip-s
cos they are plagued with issues and use the kitkat base
When I use it it backs up a 0MB apps daa folder each time. You could always very quickly swap back to stock recovery for flashing of ROM'/MCU. It never worked for me properly and I don't see any indication anyone actually backed up and restored w/ TWRP. I provided the screen shots of what error was generating while backing up somewhere. It certainly does not restore an online nandroid TWRP backup either.r.
Dave
TT_Vert said:
When I use it it backs up a 0MB apps daa folder each time. You could always very quickly swap back to stock recovery for flashing of ROM'/MCU. It never worked for me properly and I don't see any indication anyone actually backed up and restored w/ TWRP. I provided the screen shots of what error was generating while backing up somewhere. It certainly does not restore an online nandroid TWRP backup either.r.
Dave
Click to expand...
Click to collapse
miffymiffy said:
Can you link me to the wiki? the only one i could find was the huifei one with no info re twrp
are you referring to http://freaktab.com/forum/main-category/freaktab-downloads/11780-twrp-2-7-0-0-for-rockchip-s
cos they are plagued with issues and use the kitkat base
Click to expand...
Click to collapse
http://forum.xda-developers.com/wiki/Hui_Fei_Type (under "Recovery)
That looks like the page from Freaktab @miffymiffy
Have either of you read all the posts on TWRP in the original thread to get a handle on the TWRP situation for MTCB head units ?
look like somebody also looking for TWRP on Joying HU. I'm also looking on it but seem to be not so much people interested on it. I dont mind that TWRP wont update the MCU but most important it can backup the whole rom & can restore back the rom exactly what it left previously.
does the below TWRP link work for RK3188 1024x600(seem like for RK3088 CPU)
http://huifei.fs-fileserver.de/content/firmware/KK 4.4.4 Dualcore Coudu Rooted /TWRP/1024x600/
lysiong said:
look like somebody also looking for TWRP on Joying HU. I'm also looking on it but seem to be not so much people interested on it. I dont mind that TWRP wont update the MCU but most important it can backup the whole rom & can restore back the rom exactly what it left previously.
does the below TWRP link work for RK3188 1024x600(seem like for RK3088 CPU)
http://huifei.fs-fileserver.de/content/firmware/KK 4.4.4 Dualcore Coudu Rooted /TWRP/1024x600/
Click to expand...
Click to collapse
Dont know sorry, but TWRP will be the same for ALL MTCB and MTCC hedunits, plus there are no "Joying" headunits, Joying are sellers only, they sell Joyous and other MTCB, MTCC and MTCD headunits.
lysiong said:
look like somebody also looking for TWRP on Joying HU. I'm also looking on it but seem to be not so much people interested on it. I dont mind that TWRP wont update the MCU but most important it can backup the whole rom & can restore back the rom exactly what it left previously.
does the below TWRP link work for RK3188 1024x600(seem like for RK3088 CPU)
http://huifei.fs-fileserver.de/content/firmware/KK 4.4.4 Dualcore Coudu Rooted /TWRP/1024x600/
Click to expand...
Click to collapse
just try it, totally not working , blank screen come out when boot into recovery :crying:. Lucky still can restore back previous working recovery.