Database Info

[Q] A new rooted dummy need help.

Hi all,
I'm so sorry if I sound really stupid and newbie. But I have facing trouble with my HTC Desire.
Ok story start a few weeks ago when I first rooted my Desire by reading magazine which not tooo detail descript, and lack of the knowage myself. I somehow rooted and flashed to Cyanogen 7. I don't like it and I want to switch it back to the original. And I messed it up quickly and don't know what to do.
Then I flashed another one which I don't know what it is and it seems like the original ROM.
But then I realised that the input method have problem. See I'm from Hong Kong and need the handwriting to input traditional Chinese words. But it appear disappear sometime and it's back when I restore system from Titanium Backup.
Now I believe the system I have is pretty mess-up and I'm very reglad.
I found this thread from the forum and it seems like the stock rooted ROM from Hong Kong that keeps the hand-writing input in it? But the download link of the Radio is dead. What should I do?
I'm really need help, anyhelp would be great.
Sorry for asking stupid questions but I'm really learning how to deal with it.
I've attached the screen capture for the messy ROM I'm using

http://forum.xda-developers.com/showthread.php?t=773997
this is the thread I mentioned,
and I want to flash the "2.29.405.5" ROM
Thanks very much for any help
Philip

i can only give you an advice, in the future, when you want to change the rom, the first thing you have to do is make a backup from the recovery, so you can restore the old one anytime you want.
i learnt it by making a few mistakes... good luck!

[Q] HMJ37.TB_epad version to root/prime, any way back ?

Hello,
I have a brand new TF101, but the version is not US nor WW nor anything that I could find on the Asus web site. It's an HMJ37.TB_epad rom. Probably related to the fact that I'm in Belgium, we never do things like other people
Now I want to root it, but there is no "stock" TB firmware that I could find to nvflash back if something goes wrong and/or I need to send it for repair. I did find a thread where a method to backup my own device with nvflash is described. But apparently noone tried to reflash a complete backup to see if it works, and it is also clearly said that some partitions are encrypted, so not reflashable as is. So it seems that I basically have no way back if I root. Am I misinterpreting something ? Is there some other source for stock roms with a TB variant ?
Also, I'd like to try Prime, but I read that it's for US or WW models only, so I don't know if it would work... remember that I currently have no way back if things go wrong, so I'd like to be sure
I would be very gratefull if anyone could help...
Thanks,
--
Rémi

You'll need a stock TB SKU ROM to unroot and send it back for any service. As for using Prime WW/US, both will work just fine. The hardware is all the same.

find stock TB firmware
thanks for your answer, at least I know I can try Prime
Any idea where I could find a stock TB firmware ?

Did you try asus website?

yes, even the Belgian website has all the localised roms (I guess they all come from the same source), but not TB.
I'll ask my distributor, but as they are just that (distributors) I guess they won't be able to help...

asus answers :-(
Hi,
just for the record in case someone has the same problem:
I contacted Asus support, which told me "the TB version is not yet availlable, please be patient until it is on our web site".
With a bit more poking (ETA? will it really happen?), they added "no ETA, we will tell you when we know".
So no ETA, even informal, and no confirmation that it is indeed planned or even in the making...
A bit disappointed after reading so many (justified) praises for a device which will always recover from whatever one flashes to it. For some unknown reason, we Belgian must stay out of it :-(

I'm in a similar situation; i have the Japanese version which comes with a Japanese keyboard. so using a different region will mess up the keyboard configuration. there is also a secondary program called fskaren which is like a helper for entering kanji characters (instead of a native IME like most other languages)
Like the Belgium model, there is no JP rom out yet (we're still on 3.0.1; but im not sure if Gingerbreak is patched on this version) So when I flashed prime on my transformer (1.5 with nvflash), it not only "broke" the kb (changed it to US format, so i couldnt enter japanese, the kana and font size buttons didnt work as well as some remaped keys like the @ key would show a "[") but it also ended up messing up the recovery partition.
CWM worked fine but when I tried to NVFlash it to a stock WW there was a problem: it deleted CWM fine but it couldnt fully flash the recovery partition (if i did the vol - then vol+ at boot it would give me the android with a ! symbol, I could only do a hard reset if i had the ww firmware loaded on an Sd card. i tried a bunch of combinations for stock ww for 3.0.1 and 3.1 and there was never a time where i could do a hard reset without having the renamed eee_update file on SD.
So a word of warning to people with different version hardware; be careful what you flash, especially if your hardware is noticably different from the "common" versions.
Luckily I was able to get an exchange (from the store) and now i:m waiting for the files to be released or an update so that I can root (i'm assuming that the "pure root" method will work (and I can forgo the CMW part and keep my original recovery partition since ill need FSkaren for japanese)
However, without CMW, i cant make system backups, are there any simple ways to build an NVFlash backup?
There was a link on Modaco for a gui version of nvflash but it didnt work for me (it showed no errors, the progress bar just goes to 100 but no files were created).
I read the thread with the script for doing a backup, would someone like to explain how that one works? (Im assuming through adb but there are some details about restoration that I cant understand)
Id really like to be able to make a recovery for the JP version as I have found that there are quite a few people here who had flashed prime and found that the keyboard functionality had been borked (id like to be able to help them and im sure that it would be useful for building a repository for all the international versions out there.
does anyone want to write a tutorial?
Sent from my Transformer TF101 using Tapatalk

hi, thanks for your answer.
Our situations are a bit different because the TB 3.1 rom does exist, my transformer is running it. My problem is just that I cant find it as a standalone flashable download, and I cant find a reliable way to backup my current rom as a whole.
Now Belgium has indeed its own keyboard layout, that must be the reason for the custom rom, and apparently I would loose it by flashing prime or any custom rom... crap... keyboard layout should just be a config file :-(
Anyway, I wont touch that beast until I have a reliable way to come back, and will keep this thread informed of my findings if any.
Thanks,
--
Rèmi

The Keyboard layout is partially a configuration file for the JP version. A few Japanese people have remapped the keyboard so it matches when running Prime, but since there is no Japanese IME (except voice) our versions need a soft keyboard which runs together with the dock (when you want to type in Japanese). So even with the keyboard settings files in the right place, we would still need the software to add work it.
As for backing up, take a look at this:
http://forum.xda-developers.com/showthread.php?t=1129308
I haven't had time to try it (I need to learn how to use it properly first, someone mentioned a possibility of bricking on restore) but it looks like it can be a solution.

kisaten said:
As for backing up, take a look at this:
http://forum.xda-developers.com/showthread.php?t=1129308
I haven't had time to try it (I need to learn how to use it properly first, someone mentioned a possibility of bricking on restore) but it looks like it can be a solution.
Click to expand...
Click to collapse
yep that's the thread that I saw to make my own backup. The problem is that noone tried the restore part
Furthermore, they clearly say that some partitions are encrypted and should not be restored, but apparently they don't know which ones for sure... so although promising, not an option right now.

on the same HMJ37.TB boat
hello rhaaa,
I'm just posting to tell you we are on the same belgian boat
So I thank you for having created the topic, I hope you (and other belgian buyers) can keep us updated about this flash issue. Of course, I'll do the same if I have some fresh info.
By the way, did you do the recent OTA? I'm still on the 8.4.4.5.2-20110603 build.
regards from Brussels,
oliwek

i rooted yesterday BEFORE i read this thread. Have done only root + installed CWM
was going to install a custom rom but might hold off a bit more... Although the fact that i am now rooted will probably stop me from getting new OTA updates?
if I feel lucky, i might install a new rom anyway and hope an original one has surfaced by the time I will actually need it
BUT: does flashing to eg prime rom will make it so that my azerty dock will be in qwerty mode?

Belgium always does things differently in regard to Android, rumor is it's legally regulated somehow.
I will abstain from rooting until the original TB SKU comes out. Keep us posted, if anyone comes across a TB SKU! Cheers!

belblade said:
Does flashing to eg prime rom will make it so that my azerty dock will be in qwerty mode?
Click to expand...
Click to collapse
I also would like to know if using a WW firmware, or a custom ROM, creates regional issues with a belgian AZERTY keyboard/dock.... any experience to share?

belblade said:
i rooted yesterday BEFORE i read this thread. Have done only root + installed CWM
was going to install a custom rom but might hold off a bit more... Although the fact that i am now rooted will probably stop me from getting new OTA updates?
if I feel lucky, i might install a new rom anyway and hope an original one has surfaced by the time I will actually need it
BUT: does flashing to eg prime rom will make it so that my azerty dock will be in qwerty mode?
Click to expand...
Click to collapse
Could you give me details about the process you did follow? Did you root the last OTA firmware? what is the build?
thank you
edit : sorry for the double post
kovla said:
Belgium always does things differently in regard to Android, rumor is it's legally regulated somehow.
I will abstain from rooting until the original TB SKU comes out. Keep us posted, if anyone comes across a TB SKU! Cheers!
Click to expand...
Click to collapse
for people reading dutch, I suppose this is related : http://www.sigridschrijft.be/index.php/geen-youtube-app-in-belgie-door-rechtzaak-sabam/
(no youtube app on different android devices for the belgian market)

i used the topic : [ROM] Transformer 3.1 pure root and worked like a charm
don't remember the exact version but is the one before .11...
still debating on which rom i will try first might wait for prime 1.6 ...

thanks for the details

now that we have some belgians united: has anyone of you been able to install youtube ? i just can't figurer it out.. Not available in the market. Have gotten an apk from somewhere but that didn't install and have tried market access with different codes and that didn't work either...
any help is appreciated !

try with this file attached (works on 3.1 but not on 3.0, or so I have heard)
edit : sorry, you already probably did try with this file, but are you on android 3.1? what is the error message if this doesn't work?
you could try to use alogcat before retrying to install, to get a detailed log
edit : by the way, I wonder if you change your localisation in Android for Netherland or France, or if you use a public proxy to get an IP located abroad, you wouldn't then find youtube for tablet on the market.... You could find several google apps you couldn't find in Europe if you used an american IP through public proxy, so this could work...
see for example this : http://forum.xda-developers.com/showthread.php?t=1072655&page=9
Belgian will get youtube on their tablet when using it from their vacation spot in Torre Molinos

it worked with the apk you provided ! Thanks a million
I had a similar apk from tweakers.net that didn't work ...
you're a life-saver !

Galaxy S5 Clone almost dead (OS damaged) and I can't flash. Help!

First of all, let me introduce myself. My name's Rafael and this is my 1st post in this forum. I hope humbly that you can to help me with the problem that I'll show you then:
Well. To begin, the issue is this... I am working with a telephone that's not mine. Somebody sent it to me to fix it, they said me that the phone doesn't download more apps because of "full memory". When I checked it, apparently it had the internal memory partitioned incorrectly, it said it was 16gb total storage with 7 GB available, but when I was installing some apps and went back to see the memory, it showed the Available Storage Memory with a large negative number, and it wasn't letting me install more apps. Some of the features of the phone are the following (according to MTK Droid Tools):
MTK6589 <---------(Actually it's MTK6571)
Model Name: Galaxy S5
Android Version: 4.4.4 <---------(Questionable)
Model Number: SM-G900H
Base Band: G900HXXU1ANCE
Then, to see if I could make some change, I decided to install a custom ROM, apparently for MTK6589 (at that time I didn't suspect about the horrible phone's falsehood). I wanted to see if this ROM brought the partition configured correctly. I tried to carry out the installation by the CWM Recovery from SD card. It turned out that the installation did not exceed 10% and it froze there. Then I removed the battery of the phone and inserted it again. When I try to turn it back on, it stays on the screen Mediatek. And from there, it does absolutely nothing more.
I've tried to flash back the backup that I made to the phone with MTK Droid Tools, both version 5 of SP Flash Tool as version 3, but I'm still not achieving positive results, always it throws me errors errors and more errors . I've searched all over the web, compatible ROMs for this phone, but apparently there is not anything. The only way in which (at least) it begins to flash from SPFT v5, is loading a ROM MTK6571; if not, it only throws errors. However, I've already tried, but it gave me error. It appears when the yellow bar that says Download Flash reaches 3%, and then it throws the error.
The only possible solution I see is to make a ROM (from the backup I made to the phone with MTK Droid Tools before to **** it up) installable from recovery (CWM) that is the only thing that works relatively well. And I have not reached that conclusion alone, but in bilateral agreement with an expert from another forum with who I have almost a month discussing the issue.
I really need help buddies. I am desperate because I'm a bit under pressure because I have almost a month with the phone without achieving the desired results. :crying:
Greetings and thanks in advance to any of you who want to help me.
PD: Sorry for my bad English if I committed mistakes.

Post removed

Killwish said:
Download stock firmware from http://samsung-updates.com or http://sammobile.com
And flash it via odin...
Good luck
Click to expand...
Click to collapse
Do NOT do this. None of them will work.
Your issue is that 99% of the time clones dont not have the software they claim and are never made by the company they claim they are. You could try porting a rom over that has the same chip but ill be honest. XDA doesnt really do anything with cheap knock off devices. Most people avoid them like the plague.

Sorry for my previous post..... I didn't read carefully. It's not s5 its clone....

Another way...
zelendel said:
Do NOT do this. None of them will work.
Your issue is that 99% of the time clones dont not have the software they claim and are never made by the company they claim they are. You could try porting a rom over that has the same chip but ill be honest. XDA doesnt really do anything with cheap knock off devices. Most people avoid them like the plague.
Click to expand...
Click to collapse
I was thinking about to take system.ubifs.tar and boot.img from the backup, to turn it into a bootable (installable) ROM from the recovery. Is it somehow possible?

06rafagar94d said:
I was thinking about to take system.ubifs.tar and boot.img from the backup, to turn it into a bootable (installable) ROM from the recovery. Is it somehow possible?
Click to expand...
Click to collapse
Best advise is that you can try. Like I said we dont deal with clones at all really.
Worst thing that will happen is that it wont work and you learned a lesson about clone devices.

[Completed] HOW TO: Create a COPY of phone, WITHOUT Root

This is absolutely unfathomable.
I find it nearly improbable that in order to create a FULL backup of a phone, you must root it, first.
With the possibility existing that an attempt to do exactly that, may well brick it.
And then we don't need a backup. We need a new phone. :silly:
But, an actual backup would have us able to re-start and try again (and again, and again, ad infinitum).
In hand, one bricked handset (ZTE N9132, and not actually via failed rooting). Let's call it TARGET.
And, luckily, one un-bricked handset of same (ain't eBay great). Let's call it SOURCE. They are running under version 5.1.1
Yes, I know, swap the SIM, change IMEI with carrier, back in business ... er, SOURCE broken glass and just ugly condition notwithstanding. BUT, as a learning experience for me, and a wish-I-had-done-that re-do for others with a similar brick, here's my desire.
I've been all over the web and just when something sounds promising you read, "this next step requires a rooted phone" .
So, here is a working SOURCE phone. stock. just as received from vendor. not setup. factory reset. no SIM.
I want to create a COPY/BACKUP/ROM (correct my wording, please) of this SOURCE phone. Wait... format requirement coming.
Then need to PUSH/SIDELOAD/UPDATE that SOURCE image onto TARGET, and we must note for record that TARGET only boots in recovery mode (i.e., not recognized by PC). That pretty much leaves the "from SDcard" option.
ADB, fastboot, FTM, something else? ... any and all NOT requiring "root".
Because both phones are wiped/reset, user data, settings, etc. are immaterial.
We would be only concerned with creating the minimum image from SOURCE possible to allow TARGET to "snap out of it".
How about it guys ?
Can this actually be done WITHOUT ROOT?
Thanks in Advance

Hi !
I wish you would post a little bit less fancy because some of us aren`t native English speakers , like me ... anyway , let me tell you what I`ve understood so far
You have 2 devices which are the same (note that "same" doesn`t mean same brand but exactly same brand VARIANT as same brand may have multiple variants)
You want to transfer a nandroid backup from one to another directly using a PC when both connected to the same PC
First , that`s impossible
Second , even if would be , one of them isn`t recognized by PC due to "brick" status
So , disconnect them both , get a coffee , pull the backup from the working one , save it on the PC , keep on drinking coffee and find a way to un-brick the other device
When done ... hum ... well , if the bricked device gets back to life , no need to restore any backup , right ?
I understand what you want , you think that pushing a backup from a working device onto a bricked one may fix it , nope , it won`t work
How to unbrick your device , as I couldn`t find any support here on XDA for it , can be posted here https://forum.xda-developers.com/android/help
And to make a nandroid you don`t actually need root , you need an unlocked bootloader which allows you to flash a custom recovery which has this function
Here is an interesting tool
Good luck !

xanthrax said:
Hi !
I wish you would post a little bit less fancy because some of us aren`t native English speakers , like me ... anyway , let me tell you what I`ve understood so far
Click to expand...
Click to collapse
Mulțumesc, camarad. Dar nu e problema mea. Sunt Ucraina, BTW.
xanthrax said:
You have 2 devices which are the same (note that "same" doesn`t mean same brand but exactly same brand VARIANT as same brand may have multiple variants)
Click to expand...
Click to collapse
SOURCE Model=N9132, HW= cvzA, s/n = 329xxxxxxxxx
TARGET Model=N9132, HW= cvzA, s/n = 323xxxxxxxxx
both running Android 5.1.1
in MY book, that's pretty INvariant, but, hey, bits could differ
xanthrax said:
... deleted ...
I understand what you want , you think that pushing a backup from a working device onto a bricked one may fix it , nope , it won`t work
Click to expand...
Click to collapse
YES! That's exactly what I want.
And "IT WON'T WORK" is the part that blows my mind.
Exactly the situation when you restore a dorked device from a bad/failed upgrade via recent backup.
But, in this case, WHY doesn't that work?
xanthrax said:
How to unbrick your device , as I couldn`t find any support here on XDA for it , can be posted here https://forum.xda-developers.com/android/help
Good luck !
Click to expand...
Click to collapse
Thanks, Xanthrax
New posting coming to /help

The process of writing the partitions is not just a simply copy /paste (it's above my understanding especially on Samsung devices...) connect to Odin and you'll see how many processes are used in
Follow that tutorial and also post there you're findings or concerns, I'm sure more skilled people will be able to offer help, Haraso camarad! ?
Sent from my Darkside of Oneplus 3T

[Completed] Can Clockwork or another recovery program find and backup your truly stock ROM?

My question current is really about better understanding something in this whole Root and Linux learning adventure I think I am totally confused about.
Basically if no custom ROM exist or your device is not listed on the supported list of devices in any recovery program....
OR as in my case you want desperately to get the thing back running on it's true stock what do you do?
Your rooted, but stuck.
So my main question is:
What is the best way to bring a device back to stock if there is no stock ROMs available and factory reset will not work?
On any device in this situation. Mostly I am hoping to have it explained in a way I can really finalize this confusing hole in my logic.
Like can a recovery program find it if it is still on the device somewhere and if not, why not?
Thanks in advance.
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.
I have discussed this problem in another thread if more details on all this specific to this device are of interest.

Duende101 said:
My question current is really about better understanding something in this whole Root and Linux learning adventure I think I am totally confused about.
Basically if no custom ROM exist or your device is not listed on the supported list of devices in any recovery program....
OR as in my case you want desperately to get the thing back running on it's true stock what do you do?
Your rooted, but stuck.
So my main question is:
What is the best way to bring a device back to stock if there is no stock ROMs available and factory reset will not work?
On any device in this situation. Mostly I am hoping to have it explained in a way I can really finalize this confusing hole in my logic.
Like can a recovery program find it if it is still on the device somewhere and if not, why not?
Thanks in advance.
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.
I have discussed this problem in another thread if more details on all this specific to this device are of interest.
Click to expand...
Click to collapse
Hello & welcome to xda-assist,
If you rooted the device you changed the system /kernel in the process, if root is all you done you should be able to unroot by using the unroot option in your root management application, if you did further changes like deleting system apps and so on it gets more complex, the best and easiest way to get back to the original state would be a copy of the latest firmware.. If it doesn't exist you're somewhat out of luck, please refer to this link for further help & information..
http://forum.xda-developers.com/android/help

Sam Nakamura said:
Hello & welcome to xda-assist,
If you rooted the device you changed the system /kernel in the process, if root is all you done you should be able to unroot by using the unroot option in your root management application, if you did further changes like deleting system apps and so on it gets more complex, the best and easiest way to get back to the original state would be a copy of the latest firmware.. If it doesn't exist you're somewhat out of luck, please refer to this link for further help & information..
http://forum.xda-developers.com/android/help
Click to expand...
Click to collapse
Thanks for the reply. So no way to get the extract the original firmware? I don't wish to un-root. The device was set to a very sad state of affairs when I got it, unrooted, with something very unlike the stock firmware and factory date reset not helping at all. Persistently locked into a lower version of Android than it was not meant for and not running the drivers or software it would seem I need to make it function properly that came with the device.
Basically it lead to my curiosity of how one goes about extracting or mining the data that is stored somewhere on the device if all I did was root. Which is all I did.
It should still be there. Basically how do I get to it?
The link takes me back to the forums for help, however I found no help there after much searching before I asked here but thanks

Duende101 said:
Thanks for the reply. So no way to get the extract the original firmware? I don't wish to un-root. The device was set to a very sad state of affairs when I got it, unrooted, with something very unlike the stock firmware and factory date reset not helping at all. Persistently locked into a lower version of Android than it was not meant for and not running the drivers or software it would seem I need to make it function properly that came with the device.
Basically it lead to my curiosity of how one goes about extracting or mining the data that is stored somewhere on the device if all I did was root. Which is all I did.
It should still be there. Basically how do I get to it?
The link takes me back to the forums for help, however I found no help there after much searching before I asked here but thanks
Click to expand...
Click to collapse
The intended of xda-assist is to direct you to the most suitable board of xda, we do not solve issues for you or do technical support, please be patient, it often takes time for exotic devices / questions to be seen by someone who can give hints and answers..
Edit: but it's not that the original firmware is stored somewhere on the device by default where you can grab it and reinstall it..
Sent from my OnePlus 2 using XDA Labs

Sam Nakamura said:
The intended of xda-assist is to direct you to the most suitable board of xda, we do not solve issues for you or do technical support, please be patient, it often takes time for exotic devices / questions to be seen by someone who can give hints and answers..
Edit: but it's not that the original firmware is stored somewhere on the device by default where you can grab it and reinstall it..
Sent from my OnePlus 2 using XDA Labs
Click to expand...
Click to collapse
Totally cool. It's a tough question.
The OG firmware thing is the toughest part to understand. Just wanted to make sure I was clear in my explanation and question.