Related
Hi all,
I have a few small concerns about "[IMPORTANT][GUIDE] What to do after you have bought your Galaxy S3 4G GT-I9305?" - http://forum.xda-developers.com/showthread.php?t=1967124
I've now rooted my phone and done almost everything exactly as instructed (I also fell into the boot-recovery.p in system folder-trap, but got up again). I finished doing steps 1-5 including Nandroid backup from CWM recovery. Am now back at step 6: "Remember where you left off in 2nd step above? Well now you can go back and complete the partition backup of the efs folders. You should be left with 4 backup files for this final section of the backup process". This I don't fully understand.... I understand that I need to go back to this page: http://forum.xda-developers.com/showpost.php?p=33048706&postcount=1
And what I previously did at step 2 is the 3 headlines shown below with *....*. What I didn't do at step 2 is (---*....*---) below:
-------------------------------------
*Setting up QPST with your PC:*
*Backing Up IMEI / NV Data:*
(---*Restoring IMEI / NV Data:*---)
*Restore USB Settings after Backup / Restore:*
(---*Recovering IMEI And Data Connection After Flashing WRONG Root Package Intended For I9300:*---)
-------------------------------------
I don't really see any headlines regarding "partition backup of the efs folders"? But in the top it says: "Click HERE for information on the long awaited and all new EFS Professional v2.0 including download! Now supporting Qualcomm devices!". I downloaded this program, ran it but am a bit confused about all these settings and options in these programs. I'm also confused because I think that the "[IMPORTANT][GUIDE] What to do after you have bought your Galaxy S3 4G GT-I9305?" is a bit unclear here. I think it's unclear how I exactly get these 4 backup files aka "partition backup of the efs folders". I've tried to search the forum for instructions and it seems like I can do:
1) Download ktool app to phone - http://forum.xda-developers.com/showthread.php?t=1314719
2a) Install terminal emulator and issue the command: "dd if=/dev/block/mmcblk0p3 of=/storage/extSdCard/efs.img bs=4096" - http://forum.xda-developers.com/showthread.php?t=2269318
2b) Similar method, I think - with busybox and a few other commands: http://forum.xda-developers.com/showthread.php?t=1089039
3) Just copy/paste the /efs folder - http://forum.xda-developers.com/showthread.php?t=2369049
4) Use efs backup windows program - http://forum.xda-developers.com/showthread.php?t=1673059
Question 1: Are there other methods?
Question 2: Are any of these methods better or worser than the other methods? Consider the worst-possible cases, i.e. a some time the phone gets bricked. I suppose using a phone app for trying to restore /efs isn't a good strategy if you cannot even boot the phone?
Question 3: Do all backup /efs-folder applications do the same thing, only copy /efs so I don't need to use "multiple strategies" / "multiple methods"?
Question 4: Do you recommend something, e.g. using multiple of the methods above ("multiple strategies")?
I just would like to ask, because I think the "[IMPORTANT][GUIDE] What to do after you have bought your Galaxy S3 4G GT-I9305" is a bit unclear here and right now I don't really know what exactly to do. I think I'll go for method 3 above if all methods are equally appropriate...? I've never tried to restore /efs and hope I'll never have to do it...
If you have an i9305, you're in the wrong section. This is the i9300 Q&A within the i9300/i9305 section. The i9305 has it's own Q&A given that it has a different hardware specification.
If you have an i9305, please use the /!\ report button top right of your post to report the thread be moved by a moderator.
If you have the i9300, please clarify this in post 1 and remove the link to teh i9305 thread as yuou shouldn't use guides / info about other devices as you could end up bricking your device.
rootSU said:
If you have an i9305, you're in the wrong section. This is the i9300 Q&A within the i9300/i9305 section. The i9305 has it's own Q&A given that it has a different hardware specification.
Click to expand...
Click to collapse
Thank you very much - thread is now moved! I hope someone can still explain something to me about the 4 questions.
deleted
JJEgan said:
http://forum.xda-developers.com/showthread.php?t=1946915
Click to expand...
Click to collapse
I already linked to this page - this page is what my 4 questions are about. What are you trying to say with the same link to the same page I already linked to? I mean: We're only talking about EFS backup, ok? I also wrote that I did all the steps except doing the EFS backup - did you read that? At least I don't understand your answer, because I don't think your reply answers any of the 4 questions about EFS backup.
I give up .
newsboost said:
...
2a) Install terminal emulator and issue the command: "dd if=/dev/block/mmcblk0p3 of=/storage/extSdCard/efs.img bs=4096" - http://forum.xda-developers.com/showthread.php?t=2269318
2b) Similar method, I think - with busybox and a few other commands: http://forum.xda-developers.com/showthread.php?t=1089039
...
Click to expand...
Click to collapse
Also a very similar and IMHO simpler method is to use ADB with a very similar command line (it is also much simpler since you will be typing on your computer on presumably a normal keyboard and big screen).
To do that in ADB you need to have USB debugging enabled in your ROM (and very likely you need to be rooted). But even simpler/nicer is to actually use ADB with a smarter recovery (I am using Philz on my i9300) - in those ADB is enabled and you are rooted by default
JJEgan said:
Your questions refer to other phones not I9305.
AT Note
I9003
Samsung Vibrant
GT N7100
I9100.
So i don't have a clue about these other phones EFS backup and pointed you to the I9305 EFS thread as its not the same as others .
I did not realize you had edited your post that was in the I9300 forum.
Click to expand...
Click to collapse
I don't understand you. Why do you think my questions are not for the I9305?
I have NOT - I repeat: NOT edited anything in my original post, but as you can see the original post was in the wrong location and it was then moved to the correct location where it is now. I have no idea why you think my questions are not about the I9305 ?
Ok, now I think maybe I can guess what you mean:
The first question I ask is not very clear, agreed. I write: I think it's unclear how I exactly get these 4 backup files aka "partition backup of the efs folders" + "I don't really see any headlines regarding "partition backup of the efs folders"? " - so sorry about that. But my first question is: What do I do now, because the instructions seems unclear?
The next 4 questions are actually also for the I9305. Maybe you think this shouldn't work on the I9305 but AFAICS I would guess all the mentioned methods are valid on the I9305. Maybe you don't know the answer then - that's fair. My problem is that I haven't made my EFS backup yet, because I wanted to hear you guys first. I write that I'm stuck because the instructions are unclear to me and then I searched the forum for alternative methods. Am I supposed to use the "new EFS Professional v2.0" program and is this the recommended method for EFS backup on the I9305?
xclub_101 said:
Also a very similar and IMHO simpler method is to use ADB with a very similar command line (it is also much simpler since you will be typing on your computer on presumably a normal keyboard and big screen).
To do that in ADB you need to have USB debugging enabled in your ROM (and very likely you need to be rooted). But even simpler/nicer is to actually use ADB with a smarter recovery (I am using Philz on my i9300) - in those ADB is enabled and you are rooted by default
Click to expand...
Click to collapse
Ok, so you agree with my theory that all the mentioned methods are equally good and basically no method is better/worser than the others as long as you have a backup on your pc harddisk?
I think you understood the questions correctly - thank you very much for that. This implies that I can use all methods and there's no difference and nothing is "recommended" in favor of other methods, is this correct? I've never bricked my phone, so I'm a bit unsure here...
Thanks.
JJEgan said:
I give up .
Click to expand...
Click to collapse
Sorry, but I don't understand you. You only linked to a page which I already linked to and you didn't write any explanation or anything. I then explain that I already linked to this page - this page is what my 4 questions are about and I'm asking about how to proceed with making the EFS backup, because I think the page is unclear. I ask which tool is recommended. I ask what you are trying to say with the same link to the same page I already linked to?
I also wrote that I did all the steps except doing the EFS backup - did you read that? At least I don't understand your answer, because I don't think your reply answers any of the 4 questions about EFS backup. Then you deleted your link again (which I already posted to in the first place) and you write that you "give up" - sorry, but I don't understand a word of that. I'm very sorry - not trying to be rude or anything, but I don't have a clue about what you tried to say.
Another problem which I forgot to state earlier is that when I run the program "EFS Professional 2.0.68" I get this message:
BusyBox v.1.21.0 is an unstable release!
If you encounter any issues, it's strongly recommended that you downgrade to BusyBox v.1.20.2 before continuing to use EFS Professional.
Please visit (webpage) for more information.
Click to expand...
Click to collapse
This makes me afraid of making the EFS backup using this tool and this is also why I ask these 4 questions, before I actually do the EFS backup... Again: Not trying to be rude - so if I'm a noob, asking noob questions or something. I had the I9000 for 2 years and never really had any problems, forgot how I rooted the phone and how I made EFS backup. Now I get this "busybox"-warning, which I don't like... If I try to backup using this tool I use the "Backup"-tab + under "Backup Options" + "Device Filter" I select "*** All Partitions ***" and then I get:
"readlink: applet not found. Please install a BusyBox binary that contains the required applet. Busybox v1.20.2-Stericson is recommended for compatibility"
Click to expand...
Click to collapse
What now? The program hangs and nothing happens and I have to kill it - this made me post the 4 questions in the top. Sorry that I didn't give these details before now - now you got the whole situation I'm in and the background for my questions...
newsboost said:
Hi all,
I have a few small concerns about "[IMPORTANT][GUIDE] What to do after you have bought your Galaxy S3 4G GT-I9305?" - http://forum.xda-developers.com/showthread.php?t=1967124
..............
I'm also confused because I think that the "[IMPORTANT][GUIDE] What to do after you have bought your Galaxy S3 4G GT-I9305?" is a bit unclear here. I think it's unclear how I exactly get these 4 backup files aka "partition backup of the efs folders". I've tried to search the forum for instructions and it seems like I can do:
1) Download ktool app to phone - http://forum.xda-developers.com/showthread.php?t=1314719
2a) Install terminal emulator and issue the command: "dd if=/dev/block/mmcblk0p3 of=/storage/extSdCard/efs.img bs=4096" - http://forum.xda-developers.com/showthread.php?t=2269318
2b) Similar method, I think - with busybox and a few other commands: http://forum.xda-developers.com/showthread.php?t=1089039
3) Just copy/paste the /efs folder - http://forum.xda-developers.com/showthread.php?t=2369049
4) Use efs backup windows program - http://forum.xda-developers.com/showthread.php?t=1673059
Question 1: Are there other methods?
Question 2: Are any of these methods better or worser than the other methods? Consider the worst-possible cases, i.e. a some time the phone gets bricked. I suppose using a phone app for trying to restore /efs isn't a good strategy if you cannot even boot the phone?
Question 3: Do all backup /efs-folder applications do the same thing, only copy /efs so I don't need to use "multiple strategies" / "multiple methods"?
Question 4: Do you recommend something, e.g. using multiple of the methods above ("multiple strategies")?
Click to expand...
Click to collapse
Preliminary answers to unclear instructions (I edited this post and add the busybox question to the EFS-thread where I think it belongs):
Answer 1: xclub_101 proposed ADB and/or Philz? I haven't tried this yet - not sure if I want to try it.
Answer 2: I would like to hear other opinions.
Answer 3: I don't understand it - using the "root explorer"-method provides a backup of /efs around 2-300 KB. I then tried the "Samsung Galaxy S3 ToolKit" - it produces "efs.img" around 20.480 KB + efs.tar: 205 KB. The "terminal emulator-strategy" gives also a 20.480 KB efs.img-file, but not exactly the same size as the one produced by "Samsung Galaxy S3 Toolkit". So I must conclude that not all applications/methods produce the same /efs-backup. This is pretty weird, I think...?
Answer 4: Now I have a backup using 3 different "strategies"/methods. By the way, I found out ktool is only for I9300 - weird in my opinion because the /efs folder is the same on both I9300 and I9305 and both the 20.480 KB files are produced using commands that work on other phones than the I9305 too...
newsboost said:
Ok, so you agree with my theory that all the mentioned methods are equally good and basically no method is better/worser than the others as long as you have a backup on your pc harddisk?
I think you understood the questions correctly - thank you very much for that. This implies that I can use all methods and there's no difference and nothing is "recommended" in favor of other methods, is this correct? I've never bricked my phone, so I'm a bit unsure here...
Thanks.
Click to expand...
Click to collapse
All methods are very similar indeed - the only thing that you need to keep in mind is HOW you are going to restore the backup if things really go bad.
The "partition physical image" (with dd or similar) is IMHO simpler under all "normal" circumstances (and it might also hold older deleted files that other methods might not even see) but results in a slightly larger file. The only drawback that I see is if somehow you get bad sectors just in the middle of the memory for that partition - but as far as I know that is not really possible with modern NAND setups that have wear-leveling incorporated in their firmware.
xclub_101 said:
All methods are very similar indeed - the only thing that you need to keep in mind is HOW you are going to restore the backup if things really go bad.
The "partition physical image" (with dd or similar) is IMHO simpler under all "normal" circumstances (and it might also hold older deleted files that other methods might not even see) but results in a slightly larger file. The only drawback that I see is if somehow you get bad sectors just in the middle of the memory for that partition - but as far as I know that is not really possible with modern NAND setups that have wear-leveling incorporated in their firmware.
Click to expand...
Click to collapse
Thank you very much - I'm almost satisfied and relaxed now
I'm very happy with the "dd"-method, because it produces a file around 20 MB - the bigger the better, IMHO - better backup too much than too little!
If something happens to my phone, e.g. the /efs-partition gets corrupt, can I always expect that I can boot up the phone, put the backup on my external SD-card and start up a terminal emulator program and then use the "dd"-method to restore /efs? Or should I use the ADB-commands (not exactly sure how to do it). Most important: I have the impression that my two 20 MB backups are fine...
Hi all, finally I registered here at xda today because of the great new HP TPToolbox that jcsullins provides here.
This is really really great !! Many thanks !
As a newcomer to this forum I somehow can not comment on the original thread ( ) although I'm developer for decades ..
Well - so far I've been around on webosnation and other forum - but here I find that the core of development happens here.
XDA seems to be a great place to be - as a developer.
1. About the posting from jcsullins: http://forum.xda-developers.com/showpost.php?p=52765181&postcount=5
It read:
> Only Touchpad Wifi supported (not 4G) at this time
I assume this is really limited to the released HP TouchPad and does not include the never released HP TouchPad Go (7" device) - right ?
2. I read:
> Reflash A6 Firmware allows you to reflash the A6 firmware.
I very much assume I can not use this if my TP is bricked (my TP does not show anything on the screen and no light at the home button).
So - I guess - I first need to do through the TPdebrick procedure.
Sure I know these instructions: http://rootzwiki.com/topic/38786-tpdebrick-v004 Again, thanks to jcsullins for providing these too.
( Also - I wonder if there is a way to use these instructions from a Win7 system too ?)
3. In terms of using TPToolbox to get Android installed on TP:
Till today I run only webos 3.0.5 on my TouchPads and I want to keep webos around. I have 32GB (Wifi) and 64GB (Wifi) and TP GO (Wifi).
What is the recommendation before installing some Android (4.4) on a TP. Do I need to rearrange / clean up some of the existing webos volumes?
Imagine - I have no experience with Android setup. I read all of the TPToolbox thread - but found no guidance for people who want to keep webos on the same device. And I have no good understanding of what the limitations/drawbacks are when running webos and Android on the same device.
4. I read:
> It will then install moboot (which is included in TPToolbox)
I have no clear understand what moboot is doing and if needed how to remove it again. Will it allow me to boot in Android or webos ?
How many Android versions can I install in parallel and then select one at boot time ?
5. A final question for now. Is there any consideration that in future TPToolbox could allow installing openWebOS if this becomes available for existing TP devices?
anyone with some answer please ?
anyone with some answer please ?
No need to answer all questions at once.
I'm most interested in comments about question (3):
what the limitations/drawbacks are when running webos and Android on the same device: 32GB (Wifi) and 64GB (Wifi) ?
[email protected] said:
anyone with some answer please ?
No need to answer all questions at once.
I'm most interested in comments about question (3):
what the limitations/drawbacks are when running webos and Android on the same device: 32GB (Wifi) and 64GB (Wifi) ?
Click to expand...
Click to collapse
OPINIONS ARE subjective as you you appear to have several tablets it is in your best interests to test out and find what works for you. I personally am using Milaq's.
Have fun trying them.
sstar said:
OPINIONS ARE subjective as you you appear to have several tablets it is in your best interests to test out and find what works for you. I personally am using Milaq's.
Have fun trying them.
Click to expand...
Click to collapse
Thanks for your comment. So far I have no idea what "Milaq" is: I assume some kind of Android version - but such version is not documented with TPToolbox - so, for sure I will not use that for now.
My question (3) is more about hard facts: what the limitations/drawbacks are when running webos and Android on the same device: 32GB (Wifi) and 64GB (Wifi) ?
Will both OS run well on a 32GB system if both are installed and they use some shared disk space (volume?). I would consider at least 5GB of shared disk space to allow (video) file exchange on the device.
What is a recommended configuration to run webos and Android on the same device. Or doesn't it make sense at all and better use 2 devices?
Will TPToolbox optimize the volume size for both OS?
Can I configure the default OS at boot time? How to do? (Can I run Android apps inside a webos window?)
Unable to navigate TP Toolbox UI
I'm trying to use TP Toolbox to install Android on my TP. When I reach the TouchPad Toolbox UI on the tablet, the volume keys aren't working to navigate, so I have no way to select Complete Data Reset. Any ideas??
[email protected] said:
Thanks for your comment. So far I have no idea what "Milaq" is: I assume some kind of Android version - but such version is not documented with TPToolbox - so, for sure I will not use that for now.
My question (3) is more about hard facts: what the limitations/drawbacks are when running webos and Android on the same device: 32GB (Wifi) and 64GB (Wifi) ?
Will both OS run well on a 32GB system if both are installed and they use some shared disk space (volume?). I would consider at least 5GB of shared disk space to allow (video) file exchange on the device.
What is a recommended configuration to run webos and Android on the same device. Or doesn't it make sense at all and better use 2 devices?
Will TPToolbox optimize the volume size for both OS?
Can I configure the default OS at boot time? How to do? (Can I run Android apps inside a webos window?)
Click to expand...
Click to collapse
As you point out, this is the place for answers. All of your questions have been answered in other threads. Search is your friend. WIth respect to the TP GO, it does not appear to have ever been released, but if you have one, you'll have to answer your own questions because no one here has ever mentioned having one:
http://www.pcmag.com/article2/0,2817,2397197,00.asp
Touchpad linked to google account acting badly
J Scullins Toolbox installed with ease. Many thanks. Freed up memory and eliminated WebOS (pretty but pretty useless). Booted fine, loaded CM 11 4.4.2. Then asked if I wanted to restored my google apps from google account. I did. Began updating apps, but included all apps I've ever installed on any android device and loaded my current phone (Galaxy 3) wall paper. Repeated message -> "Unfortunately Trebuchet has stopped" Did not seem to affect downloading updates. Then died. Plugging into charger (wall socket) did not wake it up. Charged all night. Nothing. Unplugged and plugged in again, self-rebooted to boot menu, but has phone screen and shows charging at 1%. Should I reboot to restore mode and start over? Anyone having charging issues after using Toolbox? Thanks.
shumash said:
As you point out, this is the place for answers. All of your questions have been answered in other threads. Search is your friend.
Click to expand...
Click to collapse
Thanks for promising that I should be able to find answer. I did read the complete thread about TPToolbox and few others too and search before I started this new thread - but my above 5 questions remained open. If anyone has found a good pointer please paste a URL here.
If I find correct answer myself I will put such links here.
ad (4) I think I understand moboot good enough for now. In my words it is a boot manager that comes with Android or at least you can use with Android. It is not a webos app or so. Not 100% sure how to get it on the TP device - but I assume when I install Android for first time it will also install and it will somehow stay even if Android gets deinstalled. Anyhow - any link to a good wiki page would be much appreciated.
ad (1) Yes, TP GO is a rare device - but several 100 seem to be around by now. Many of these come with some Android 2.X version installed. ( Mine was patched to webos 3.0.5 ) Ok, if noone has a GO here I have to assume that TPToolbox does not support / was not tested on TP GO. So far posting from jcsullins does not mention the TP GO at all: http://forum.xda-developers.com/show...81&postcount=5
mheath said:
I'm trying to use TP Toolbox to install Android on my TP. When I reach the TouchPad Toolbox UI on the tablet, the volume keys aren't working to navigate, so I have no way to select Complete Data Reset. Any ideas??
Click to expand...
Click to collapse
I have a TP 4G - sounds like this could be an issue? Will this Toolbox installation work on the 4G? If not, is there a good alternative to install Android?
mheath said:
I have a TP 4G - sounds like this could be an issue? Will this Toolbox installation work on the 4G? If not, is there a good alternative to install Android?
Click to expand...
Click to collapse
The original TPtoolbox thread answers this 4G question as: http://forum.xda-developers.com/showpost.php?p=52923285&postcount=65
Toolbox not working for me
Hello,
i tried Toolbox to bring life back to my Touchpad.
When i'm running this program it starts very well but i can't get the menue.
So it's not possible to run one of the menue-points.
I use Windows 7 64bit, the TP is connected with USB-sign on.
My problem:
In the WebOs-log the last line shows a flash-failure.
When i'm starting the TP, first a static HP-logo comes up, followed from a rotating HP-logo,
the a screen changes from black to white with a grey button rotating.
Any idea?
Thanks!
Rekaro said:
Hello,
i tried Toolbox to bring life back to my Touchpad.
When i'm running this program it starts very well but i can't get the menue.
So it's not possible to run one of the menue-points.
I use Windows 7 64bit, the TP is connected with USB-sign on.
My problem:
In the WebOs-log the last line shows a flash-failure.
When i'm starting the TP, first a static HP-logo comes up, followed from a rotating HP-logo,
the a screen changes from black to white with a grey button rotating.
Any idea?
Thanks!
Click to expand...
Click to collapse
Re-read the directions for TP Toolbox. You need to boot into WebOS recovery (a static usb symbol). It sounds like your TP is trying to boot into WebOS, not WebOS recovery.
A) Have novacom installed
To load TPToolbox, you will need novacom to be installed on your PC.
You can download and install novacom from http://www.openwebosproject.org/open.../packages.html
Or, you can download and run a java-based "universal installer" from http://code.google.com/p/universal-n...downloads/list
B) Put the Touchpad into webOS recovery mode and connect via USB cable to PC
NOTE: Even if webOS is removed, webOS recovery will still exist as it's built into the bootloader.
If you have moboot already installed, just select "webOS recovery" there.
Or, power the Touchpad off via webOS, then with the Touchpad is off, hold VolumeUp (closest to Power) and Power until you see the USB symbol.
Or, hold Power+Home until the screen changes (about 10 secs) and then start holding the VolumeUp button until you see the big USB symbol.
Click to expand...
Click to collapse
shumash said:
Re-read the directions for TP Toolbox. You need to boot into WebOS recovery (a static usb symbol). It sounds like your TP is trying to boot into WebOS, not WebOS recovery.
Click to expand...
Click to collapse
Thanks,
no it's in recovery mode i'm shure. A big usb symbol on the screen and some other lines.
I can then open the terminal-window and connect the Touchpad.
I add here pictures what happens when i type the commands "printenv" and "token".
When i type reboot, the TP starts correct to boot, first the static HP sign, then a greyed HP sign and then a screen (see the picture) with a grey rotating Button.
That's it.
issue loading TPTToolbox
Sorry folks - i am fairly new at this - and we all had to start at some point - so if this is obvious to most, i apologize.. but need a little help.
I cant seem to get the Toolbox to load, i downloaded it from the post,{as well as the Novacom driver} i have extracted the three files - when i open the .bat file i get the message below. I have the TouchPad connected via USB, and windows has assigned it a letter drive and I have the big USB icon on the pad screen
message:
"
Setting Palm path ...
Checking novacom service ...
Loading TPToolbox ...
.
Cannot connect to Touchpad.
Make sure Touchpad is connected with USB cable.
Make sure Touchpad is in webOS Recovery (bootie) mode
(where big USB symbol shows on Touchpad screen)
.
"
Toolbox
I'm not sure you understand the instructions on how to do the install.
Here is a link with instructions that I used for my install:
http://liliputing.com/2014/06/use-touchpad-toolbox-install-android-erase-webos-hp-touchpad.html
While the instructions are written for windows users, I used them for my Ubuntu Linux install and everything
worked perfectly.
Recovery problem when running toolbox
I've followed the instructions for running the Toolbox and have removed WebOS, setup the directory sizes and uploaded the ROM and GApps AND renamed the files as specified in the how-to.
However I am having issues with the recovery. The recovery I downloaded was update-CWM-jcs-dm-tenderloin-20140317.zip
I get the error that "No supported recovery file found. Aborting."
I've seen mention that the cable could be bad however if I have no files in the ttinstall directory, I get an error that there's no ROM. I upload the ROM and rename it and the error then is about the Recovery file so that means the ROM was in fact uploaded so the cable theory is moot.
I'm thinking the recovery file needs to be named something specific however when I have tried to use the file names listed as
Compatible Legacy ROM files:
cm-10.1-*-tenderloin.zip or
skz_tenderloin-2.11_jb_4.2.2-*.zip
Click to expand...
Click to collapse
but that doesn't work. Is the file name supposed to be something else?
(Sorry about asking this here. Tried to ask in Developer thread but I don't have enough posts)
chrisjpopp said:
I've followed the instructions for running the Toolbox and have removed WebOS, setup the directory sizes and uploaded the ROM and GApps AND renamed the files as specified in the how-to.
However I am having issues with the recovery. The recovery I downloaded was update-CWM-jcs-dm-tenderloin-20140317.zip
I get the error that "No supported recovery file found. Aborting."
I've seen mention that the cable could be bad however if I have no files in the ttinstall directory, I get an error that there's no ROM. I upload the ROM and rename it and the error then is about the Recovery file so that means the ROM was in fact uploaded so the cable theory is moot.
I'm thinking the recovery file needs to be named something specific however when I have tried to use the file names listed as
but that doesn't work. Is the file name supposed to be something else?
(Sorry about asking this here. Tried to ask in Developer thread but I don't have enough posts)
Click to expand...
Click to collapse
Try the update-TWRP-jcs-dm-tenderloin-20140512.zip instead. It worked just fine for me.
chrisjpopp said:
I've followed the instructions for running the Toolbox and have removed WebOS, setup the directory sizes and uploaded the ROM and GApps AND renamed the files as specified in the how-to.
......
(Sorry about asking this here. Tried to ask in Developer thread but I don't have enough posts)
Click to expand...
Click to collapse
How did you rename the file? I don't think you need to rename any file.
No matter how many times I reinstall novacom TPtoolbox will not get past
Checking Novacom services....
And goes no fauther.
I am running windows 8.1
HP Touchpad 4G - Issue running
[email protected] said:
The original TPtoolbox thread answers this 4G question as: http://forum.xda-developers.com/showpost.php?p=52923285&postcount=65
Click to expand...
Click to collapse
Good thing I didn't wipe webOS off! I'd have a nice frisbee. Hopefully these guru's will fix that issue and we can all be happy. Thanks JCSullins.
Hey guys. Sorry to bother you in the X98 section, but since there's no section for the X80 yet and maybe the devices have some similarities, I hope it's ok.
The tablet worked fine, but to remove any possible bloatware under Windows or Android, I reset Windows. Somehow the device must have crashed (low battery?) and now I can't boot to Windows anymore (black screen and / or boot loop). Of course I made no backup / recovery disk. Android still works fine and I still get into BIOS / UEFI.
I tried reinstalling Windows via OTG with USB stick. I got to the point where I can choose a partition. Problem is, there are lots of partitions (Android, recovery, System and so on). I located the Windows partition, formatted / deleted it and tried to reinstall Windows on this partition. Just the exact way I would do it on a PC. Somehow it won't install on this partition. The error message says something about "the partitions are not in the recommended order. Further information for installation on GPT-volumes..." (I don't know the exact English phrasing because everything is in German). I chose "continue anyway". Then I get the message that "the EFI-system is not formatted in NTFS. Format the partition to FAT32 and start install procedure again". I press ok and get back to Windows Setup (Install now).
I also tried different repair and recovery options. One time I got error code 0xC0000034. Funny thing is, Windows still seems to be there because while trying to repair / recover I tried to load some drivers and could see the hard drives and folders under Windows.
I tried downloading the original roms here: http://pan.baidu.com/s/1qYEa8gc
You need a Baidu account for the larger files and after days and days I gave up to create such an account as it seems to work only with a mainland China number. There's an option for oversea mobiles but that's not working. I tried a QQ-account, but Baidu wants to link with it and you need that telephone number again. So apparently there's no way to get the original files that way.
I found some stuff here: http://www.needrom.com/download/teclast-x80-pro-dualboot/ but that's only a tutorial file in Chinese and some flash programms / drivers (also got them from Baidu - smaller files are possible to download without an account).
Long story short: I guess recovering Windows 10 is too much effort, so I want to make the tablet Android only and of course want to use the whole capacity for Android. I found a thread on reddit about removing Windows on the X98: https://www.reddit.com/r/teclast/comments/479eua/teclast_x89_how_to_remove_windows_10/
But I have no idea which partitions are definitely needed for Android and which ones I can safely delete. I found a partition map here: http://wheresmykeyboard.com/2015/08/teclast-x98-air-64gb-dual-boot-default-partition-map/ but that doesn't help me that much because they look different.
Attached you will find a photo of all the partitions on my device. I guess there are some which were created during the failed Windows installation because I had about 20 GB free space and now only 17.7 GB.
So is there anybody out there who knows if it's possible to remove Windows completely and which partitions I have to delete?
Did you ever figure this out? I just bought an X80 Pro and was thinking of doing something similar since I plan on making it an android-only tablet.
Deathgazer said:
Did you ever figure this out? I just bought an X80 Pro and was thinking of doing something similar since I plan on making it an android-only tablet.
Click to expand...
Click to collapse
Hi. Sorry for the late replay. Yes, I figured it out and my X80 Pro is now running Android-only with 32 GB. In the end, it wasn't that hard but a long way to success.
metalaxi said:
Hi. Sorry for the late replay. Yes, I figured it out and my X80 Pro is now running Android-only with 32 GB. In the end, it wasn't that hard but a long way to success.
Click to expand...
Click to collapse
Please do describe how you achieved Android-only with 32 GB memory
Cheers
metalaxi said:
Hi. Sorry for the late replay. Yes, I figured it out and my X80 Pro is now running Android-only with 32 GB. In the end, it wasn't that hard but a long way to success.
Click to expand...
Click to collapse
Yes please tell us how metalaxi , it'll be much appreciated.:good:
Ok, guys. Since some of you are asking how I did it, I'm going to try to explain it. It's kinda embarrassing that I don't remember the exact way but I hope it helps somehow. I used the tutorial from this site: http://techtablets.com/forum/topic/x80-plus-android-os-only/#login
Even though it's supposed to be for the Plus model, it also worked on the Pro. Btw, the guy Alex in that thread is me .
You can download all the files from my Google Drive here: https://drive.google.com/open?id=0BxEFqy4Rt9w_cnh3VG9ySk5sOHM
You need
- Android5.1 Upgrade Tool.rar
- X80 Pro (E3E6)- Dual OS - Android5.1-V1.04 Firmware.rar
- gpt.rar (Credit goes to Allember @techtablets-forum; hope it's ok to spread the file)
First you have to install the flash tool. Unrar the firmware and replace the gpt.bin. Then flash the firmware by checking BLANK.
Problem is that when I did all that, my Windows was already crushed and wasn't working anymore. I can't remember anymore if I erased the Windows partitions or any others beforehand. If you're not interested in Windows anymore, just flash it without changing or erasing any of the partitions. I guess by replacing the gpt-file, you do all that automatically.
I hope this somehow helps you. Feel free to ask for more help.
Have a good night!
metalaxi said:
Ok, guys. Since some of you are asking how I did it, I'm going to try to explain it. It's kinda embarrassing that I don't remember the exact way but I hope it helps somehow. I used the tutorial from this site: http://techtablets.com/forum/topic/x80-plus-android-os-only/#login
Even though it's supposed to be for the Plus model, it also worked on the Pro. Btw, the guy Alex in that thread is me .
You can download all the files from my Google Drive here: https://drive.google.com/open?id=0BxEFqy4Rt9w_cnh3VG9ySk5sOHM
You need
- Android5.1 Upgrade Tool.rar
- X80 Pro (E3E6)- Dual OS - Android5.1-V1.04 Firmware.rar
- gpt.rar (Credit goes to Allember @techtablets-forum; hope it's ok to spread the file)
First you have to install the flash tool. Unrar the firmware and replace the gpt.bin. Then flash the firmware by checking BLANK.
Problem is that when I did all that, my Windows was already crushed and wasn't working anymore. I can't remember anymore if I erased the Windows partitions or any others beforehand. If you're not interested in Windows anymore, just flash it without changing or erasing any of the partitions. I guess by replacing the gpt-file, you do all that automatically.
I hope this somehow helps you. Feel free to ask for more help.
Have a good night!
Click to expand...
Click to collapse
Hi @metalaxi. Do you think its possible to like "reverse" and use the same files to remove Android instead and maintain the Windows 10? Appreciate to hear from you. Thanks!
Do we have to change the gpt before doing what you said in your PDF? Or I have just to follow your PDF?
Hi guys, got mine a few months and want to get rid of the Windows part, but the instructions are insufficient for a joker like me.....
1. Download the firmware, its 4 parts of rar being zipped together
2. flash the firmware HOW?!?!?! I have no Idea...... please give us some closer instructions.
reycharlesconrad said:
Hi @metalaxi. Do you think its possible to like "reverse" and use the same files to remove Android instead and maintain the Windows 10? Appreciate to hear from you. Thanks!
Click to expand...
Click to collapse
Sorry, I can't answer that sufficent enough. As far as I know, you can just delete all partitions except the ones from Windows. Then format the unallocated space and merge it with the one from Windows. No guarantee!
dirkzelf said:
Hi guys, got mine a few months and want to get rid of the Windows part, but the instructions are insufficient for a joker like me.....
1. Download the firmware, its 4 parts of rar being zipped together
2. flash the firmware HOW?!?!?! I have no Idea...... please give us some closer instructions.
Click to expand...
Click to collapse
1. Which 4 parts do you mean?
2. To flash any firmware, you need to install all the upgrade tools:
IntelAndroidDrvSetup1.5.0
iSocUSB-Driver-Setup-1.2.0
PhoneFlashTool_5.3.4.0_internal_win32
metalaxi said:
1. Which 4 parts do you mean?
2. To flash any firmware, you need to install all the upgrade tools:
IntelAndroidDrvSetup1.5.0
iSocUSB-Driver-Setup-1.2.0
PhoneFlashTool_5.3.4.0_internal_win32
Click to expand...
Click to collapse
it's too long ago, so I don't know what I exactly did there, but since there was no reply for a long time, I just took a shot and worked out well, now I have an Android only tablet.
I just got lucky I guess....
partition help
Hi, please help.
I have x80pro e3e8
I managed to erase a complete disk partition.
You are trying to revive again, fail.
installed here:
iSocUSB-Driver-Setup-1.2.0
IntelAndroidDrvSetup1.5.0
PhoneFlashTool_5.3.4.0_internal_win32
downloaded here:
Firmware (20161020_SZ)
Tablet joined and tried to flash.
* failed - failed loadet.efi
Please help. I can not download from Baidu
* If I use phoneFlasTool and flash a blank disc - Create Flash partition and dual boot and replace recovery?
What to do with an empty disc?
Thanks for any advice
It is not so hard. By mine it was only trial and error. Installiert all drivers an go in the bootloader with three Finger method. Go two levels up and go into bootloader. Then connect to PC and look in Intel flashing tool if connection is reconiced correctly. Select the downloaded file and select flash. Thats it. Device will reboot and you are ready to go.
theone0987654321 said:
It is not so hard. By mine it was only trial and error. Installiert all drivers an go in the bootloader with three Finger method. Go two levels up and go into bootloader. Then connect to PC and look in Intel flashing tool if connection is reconiced correctly. Select the downloaded file and select flash. Thats it. Device will reboot and you are ready to go.
Click to expand...
Click to collapse
Thank you for the advice. That's right, I did it was marked. I found a reason. rom file was saved on desktop, and had a long name (as I downloaded it) It must copy the file to C've renamed the firmware. Everything went alright. I downloaded and used the GPT files for resizing disk and now goes all right. Thank you for responding to my question.
hi, I have problem while flashing.
Phone flash tool always gives ERROR
Automatic reboot is not supported on this device, please reboot the device manually
ERROR : [Port 0/1/4] Failed to reboot the device
Click to expand...
Click to collapse
Any idea what to do? I followed all the steps, tried many times, still same problem. And it's not possible to reboot device manually, because then it lose connection with PC
Restock OS Without Android
Hi there.
I have to restock my Device, but the Intel Flash Tool does not recognize my Device.
I cannot boot into Android to turn on USB-Debugging or go into fastboot mode
How do i flash my device without any OS installed?
---------- Post added at 04:03 PM ---------- Previous post was at 03:52 PM ----------
affe2000 said:
Hi there.
I have to restock my Device, but the Intel Flash Tool does not recognize my Device.
I cannot boot into Android to turn on USB-Debugging or go into fastboot mode
How do i flash my device without any OS installed?
Click to expand...
Click to collapse
Ok, got it working... dnx fastboot mode is there
....
hello guys by accident i deleted windows 10, how can i reinstall them? i dont have the windows 10 icon in the dual boot select i only see the android icon
mike mike baby said:
hello guys by accident i deleted windows 10, how can i reinstall them? i dont have the windows 10 icon in the dual boot select i only see the android icon
Click to expand...
Click to collapse
Straightforward if you can obtain a USB stick capable of storing over 7GB (some 8GB sticks may not); USB hub (ideally a powered hub); USB keyboard; OTG cable.
1) Obtain the Windows files of the correct firmware. The procedure outlined here is for E6E9 firmware, but other firmware will be similar. Download the circa 6.5GB E6E9 firmware Windows files from https://yadi.sk/d/XEvRsoiD3Q4vKX or https://mega.nz/#F!I0AXGR5C!YiNFkZL9DIvzepH28qAjEQ (or from appropriate source for your firmware version).
Decompress the downloads as required to obtain six folders and two files.
2) Format the stick to FAT32.
3) Name the stick WINPE (five uppercase characters).
4) Copy the previously mentioned folders and files to the USB stick.
5) Plug USB stick and USB keyboard into hub; plug hub into OTG cable; plug OTG cable into tablet whilst the tablet is off.
6) Turn on tablet and immediately start tapping << Delete >> key on USB keyboard. This should open the UEFI config section prior to Android boot option. If the tablet displays the Android boot option, turn off the tablet, wait a few seconds, then turn on and start tapping << Delete >> key on USB keyboard again.
7) When in UEFI, touch the title menu option of << Save and Exit >> and look in the << Boot Override >> section for the name of your USB stick, then touch the name of your USB stick. The screen will immediately go blank as the tablet starts to boot from the USB stick.
8) After a few minutes, a numerically display of progress will be displayed in a CMD window.
9) After reaching 100% and nearing completion of the overall installation, the tablet will prompt for acceptance, so accept that prompt.
10) The setup will run a few final operations for a few seconds, then automatically reboot.
11) Done.
You will be prompted to complete the OOBE on each Windows boot until you complete OOBE.
Your current stage : qualcomm hs-usb qdloader 9008 in your network devices ,when you connect your phone.(if not, get your
google to findout how to get here).
Attention Moto G 2nd generation users. Unbrick using SD card dump
Can anybody create the following file from working Moto g(2014). ?.It will save Many devices. Please give a google drive link.
Reference from below Threads.....
http://forum.xda-developers.com/showthread.php?t=2549068
http://forum.xda-developers.com/showthread.php?t=2660566
The following guide is for S3 but it will work for All the Qualcomm based devices. No need to have Linux os to perform this back up.Can be done using the windows.
Insert memory card into working & rooted Moto g and issue the following command using ADB
->adb.exe shell dd if=/dev/block/mmcblk0 of=/storage/sdcard1/debrick.bin bs=1024 count=81920
increase the count if you face any problem. Compress and Upload the debrick.bin in google drive and leave a link.
Explanation:
How to UNBRICK:
Credit goes to these guys in this thread, I thought i was onto something origional, however after doign some searching i found others have figured this out for a different Variant of the S3
What you did:
Bricked downgrading the bootloader after upgrading to the 4.3 bootloader. The 4.3 bootloader appears to blow efuses that stop previous boot loaders from booting. Now your EMMC has non booting garbage on/in it. YAY! not...
What we are doing:
What we will be doing is writing the Partition layout (Partition.mbn) among other things to the SD so the phone will boot from it after it fails to boot from the EMMC. According to my research the CPU is designed to cascaded from one storage device to the other in the event of failure on the first device. This also means if your EMMC is smoked, you could technically run the whole rom and everything from the sd card, or that's my assumption.
What you need:
- A Micro SD card 16GB or larger. this will no work on smaller cards, i tried a 2GB 4 GB and 8GB for the sake of testing and it fails.
- A working Dump that includes the SBL1, SBL2, SBL3, aboot, TZ and RPM from a working device that matches your DEVICE MODLE ie: I747U or I747M If you wanto t create your own dump from a friends device the command in a rooted adb shell would be as follows but not exact depending where you want the dump file to end up being on your sd cards. "dd if=/dev/block/mmcblk0 of=/storage/sdcard1/debrick.bin bs=1024 count=81920" That is what I used my my co-workers CM 10.2 rom to get the 4.3 bootloader/debrick dump. NOTE: the device has to be rooted with a working busybox that supports the dd command.
- The ability to write the dump image to the micro sdcard.
If this method works, my hardbricked Moto G 2014 will thank you!
Anyway, thank you so much for your hard work trying to help every user with a bricked Moto G 2014!
Pleaseeeeeeeeee! help in xt1069 to!
Help me too! I have Moto g xt1069.
Tnx
help
ByReverso said:
If this method works, my hardbricked Moto G 2014 will thank you!
Anyway, thank you so much for your hard work trying to help every user with a bricked Moto G 2014!
Click to expand...
Click to collapse
hey guy has to offer me of your moto g2 files. Please mine too this in this state
@lets_do_it,
In Brazil has a group on Facebook with over 1000 (all witch hardbrick) people and we are trying to get the files but it's pretty hard ):
lets_do_it said:
Your current stage : qualcomm hs-usb qdloader 9008 in your network devices ,when you connect your phone.(if not, get your
google to findout how to get here).
Attention Moto G 2nd generation users. Unbrick using SD card dump
Can anybody create the following file from working Moto g(2014). ?.It will save Many devices. Please give a google drive link.
Reference from below Threads.....
http://forum.xda-developers.com/show....php?t=2660566
http://forum.xda-developers.com/show....php?t=2549068
The following guide is for S3 but it will work for All the Qualcomm based devices. No need to have Linux os to perform this back up.Can be done using the windows.
Insert memory card into working & rooted Moto g and issue the following command using ADB
->adb.exe shell dd if=/dev/block/mmcblk0 of=/storage/sdcard1/debrick.bin bs=1024 count=81920
increase the count if you face any problem. Upload the debrick.bin in google drive and leave a link.
Explanation:
How to UNBRICK:
Credit goes to these guys in this thread, I thought i was onto something origional, however after doign some searching i found others have figured this out for a different Variant of the S3
What you did:
Bricked downgrading the bootloader after upgrading to the 4.3 bootloader. The 4.3 bootloader appears to blow efuses that stop previous boot loaders from booting. Now your EMMC has non booting garbage on/in it. YAY! not...
What we are doing:
What we will be doing is writing the Partition layout (Partition.mbn) among other things to the SD so the phone will boot from it after it fails to boot from the EMMC. According to my research the CPU is designed to cascaded from one storage device to the other in the event of failure on the first device. This also means if your EMMC is smoked, you could technically run the whole rom and everything from the sd card, or that's my assumption.
What you need:
- A Micro SD card 16GB or larger. this will no work on smaller cards, i tried a 2GB 4 GB and 8GB for the sake of testing and it fails.
- A working Dump that includes the SBL1, SBL2, SBL3, aboot, TZ and RPM from a working device that matches your DEVICE MODLE ie: I747U or I747M If you wanto t create your own dump from a friends device the command in a rooted adb shell would be as follows but not exact depending where you want the dump file to end up being on your sd cards. "dd if=/dev/block/mmcblk0 of=/storage/sdcard1/debrick.bin bs=1024 count=81920" That is what I used my my co-workers CM 10.2 rom to get the 4.3 bootloader/debrick dump. NOTE: the device has to be rooted with a working busybox that supports the dd command.
- The ability to write the dump image to the micro sdcard.
Click to expand...
Click to collapse
Help
ByReverso said:
If this method works, my hardbricked Moto G 2014 will thank you!
Anyway, thank you so much for your hard work trying to help every user with a bricked Moto G 2014!
Click to expand...
Click to collapse
the links do not work
It days trying to solve this problem, mine is xt1068
thirtytwoob said:
the links do not work
It days trying to solve this problem, mine is xt1068
Click to expand...
Click to collapse
Links for the thread is updated. you can view the reference now
ripizud said:
@lets_do_it,
In Brazil has a group on Facebook with over 1000 (all witch hardbrick) people and we are trying to get the files but it's pretty hard ):
Click to expand...
Click to collapse
If someone creates this image it will be helpful. since it requires basic rooting of the device (busy box installed)
and adb pull and need to compress the image.i got the seperate files like tz,sb1,..etc from another thread but i dont know how to create each partition using mini partition wizard. Because there are around 36 partitions ,cannot perform this manually
Reference links won't work
JeffDrk said:
Reference links won't work
Click to expand...
Click to collapse
click my original post.i can able to access
Good morning friends!!!
This link here from a web site development:
https://github.com/MotorolaMobilityLLC
estou com uma aparelho xt1068
tenho duvida de esse procedimento poderia danificar o aparelho de teste ?
UP my thread is my only hope.. Please can someone link the 1068 files
Could you detail the procedure is to provide the files used my Moto G2 does not start the recovery.
In that format should be the sdcard? (FAT32, NTFS, EXFAT)?
If someone finds out that this solution actually does work, and tests it on a hardbricked device with success:
WALL OF TEXT INCOMING:
I would like to help, but I only have a working XT1072 and my debrick.img would be useless here. But it should work, and you can get technical details by dissasembling recovery.img and checking recovery.fstab But I might make sooner or later an XT1072 debrick.img and place it in a thread with multiple debrick images for multiple images. We could make these from rooted devices running a stable ROM with a specified bootloader version, and gather them listing them in the following format, along with usage instructions:
D_V_B_A_T_debrick.zip
Device Codename
V:Variant
B:Bootloader version
A:Android version
T:TWRP version
Example:
thea_XT1072_48.21_5.1.1_3.0.2-0_debrick.zip with an mmc0blk0.img file inside.
just like this thread http://forum.xda-developers.com/galaxy-s4-verizon/help/help-plz-starting-debrick-img-t3003027
If this does really work, then Moto users won't live in fear anymore. A prosperous, brick-free glorious era awaits...
But it's not guaranteed to work, because Motos have been never recovered from a Lollipop hardbrick and this method surely had to be tested before (or was never tested and we had the solution AT OUR EYES). We need cooperation from everyone, and testers with both bricked and working devices from the same variant will be thanked in the post main page. Once the process is perfected, I will send my own debrick to be the second one in the list Someone please unbrick any Moto and then post the IMG and how did you make it (block size, count)
Please OP read this and make a debrick test thread! My device works OK but anything can happen.
benjausen said:
If someone finds out that this solution actually does work, and tests it on a hardbricked device with success:
WALL OF TEXT INCOMING:
I would like to help, but I only have a working XT1072 and my debrick.img would be useless here. But it should work, and you can get technical details by dissasembling recovery.img and checking recovery.fstab But I might make sooner or later an XT1072 debrick.img and place it in a thread with multiple debrick images for multiple images. We could make these from rooted devices running a stable ROM with a specified bootloader version, and gather them listing them in the following format, along with usage instructions:
D_V_B_A_T_debrick.zip
Device Codename
V:Variant
B:Bootloader version
A:Android version
T:TWRP version
Example:
thea_XT1072_48.21_5.1.1_3.0.2-0_debrick.zip with an mmc0blk0.img file inside.
just like this thread http://forum.xda-developers.com/galaxy-s4-verizon/help/help-plz-starting-debrick-img-t3003027
If this does really work, then Moto users won't live in fear anymore. A prosperous, brick-free glorious era awaits...
But it's not guaranteed to work, because Motos have been never recovered from a Lollipop hardbrick and this method surely had to be tested before (or was never tested and we had the solution AT OUR EYES). We need cooperation from everyone, and testers with both bricked and working devices from the same variant will be thanked in the post main page. Once the process is perfected, I will send my own debrick to be the second one in the list Someone please unbrick any Moto and then post the IMG and how did you make it (block size, count)
Please OP read this and make a debrick test thread! My device works OK but anything can happen.
Click to expand...
Click to collapse
I have the files of all partition gathered from other thread but i don't know ,how to create 36 partition on sd card i mean file system differ for each partition.like FAT,ext4,.Thatswhy i require a debrick image file which has partition information.once it is available i can "dd" the files to each partition.
But can you please post your files ?. Xt1072 files are okay. our devices are bricked because of different partition size from kitkat to lollipop so
your help is required.i can change the partition size later i have the partition table information with me.
http://forum.xda-developers.com/moto-g-2014/help/help-partition-layout-info-dump-xt1068-t3333342
I am available for testing
benjausen said:
If someone finds out that this solution actually does work, and tests it on a hardbricked device with success:
WALL OF TEXT INCOMING:
I would like to help, but I only have a working XT1072 and my debrick.img would be useless here. But it should work, and you can get technical details by dissasembling recovery.img and checking recovery.fstab But I might make sooner or later an XT1072 debrick.img and place it in a thread with multiple debrick images for multiple images. We could make these from rooted devices running a stable ROM with a specified bootloader version, and gather them listing them in the following format, along with usage instructions:
D_V_B_A_T_debrick.zip
Device Codename
V:Variant
B:Bootloader version
A:Android version
T:TWRP version
Example:
thea_XT1072_48.21_5.1.1_3.0.2-0_debrick.zip with an mmc0blk0.img file inside.
just like this thread http://forum.xda-developers.com/galaxy-s4-verizon/help/help-plz-starting-debrick-img-t3003027
If this does really work, then Moto users won't live in fear anymore. A prosperous, brick-free glorious era awaits...
But it's not guaranteed to work, because Motos have been never recovered from a Lollipop hardbrick and this method surely had to be tested before (or was never tested and we had the solution AT OUR EYES). We need cooperation from everyone, and testers with both bricked and working devices from the same variant will be thanked in the post main page. Once the process is perfected, I will send my own debrick to be the second one in the list Someone please unbrick any Moto and then post the IMG and how did you make it (block size, count)
Please OP read this and make a debrick test thread! My device works OK but anything can happen.
Click to expand...
Click to collapse
The model of my cell phone and the XT1078, however he is full brick, if you can find the backup.img the XT1072 I could do a test here in my. I would be very agradesito.
ByReverso said:
If this method works, my hardbricked Moto G 2014 will thank you!
Anyway, thank you so much for your hard work trying to help every user with a bricked Moto G 2014!
Click to expand...
Click to collapse
Please tutorial??
lets_do_it said:
I have the files of all partition gathered from other thread but i don't know ,how to create 36 partition on sd card i mean file system differ for each partition.like FAT,ext4,.Thatswhy i require a debrick image file which has partition information. once it is available i can "dd" the files to each partition.
But can you please post your files ?. Xt1072 files are okay. our devices are bricked because of different partition size from kitkat to lollipop so
your help is required.i can change the partition size later i have the partition table information with me.
http://forum.xda-developers.com/moto-g-2014/help/help-partition-layout-info-dump-xt1068-t3333342
Click to expand...
Click to collapse
I will try to help. I currently cannot post my own files, also I need to know information like the block size for the DD command. Also a document with recovery.fstab will help because I run Windows right now. Android phones use ext4 by default, so use this.
---------- Post added at 03:33 PM ---------- Previous post was at 03:31 PM ----------
eliezer.system said:
The model of my cell phone and the XT1078, however he is full brick, if you can find the backup.img the XT1072 I could do a test here in my. I would be very agradesito.
Click to expand...
Click to collapse
I will try to take a partition dump from my own phone, but I am afraid I will mistype the command and ruin the phone. I will try anyway and when I have time I will post the IMG.
Hello There,
It's been a while since i last put Android on my HP Touchpad and around 5 years ago i put it back to Native OS and cleared everything out,
Can someone please provide me the latest download link for an Android Image ? ( preference would be for Bluetooth to work - if that was ever cracked ).
Also - can't get the Novacom drivers working via MAC OS - tried everything - any ideas ? ( I just want to get Clockwork on - so i can dual boot - Native WEBOS and Android )
Any links to the best way to get Android back on would be appreciated - as i've forgotten most of the steps
I've got Windows 10 on my Mac Book Pro - so if that's the only way to get working Novacom I can do that as well..
Appreciate any help,
Thank You All,
gpzarquon said:
Hello There,
It's been a while since i last put Android on my HP Touchpad and around 5 years ago i put it back to Native OS and cleared everything out,
Click to expand...
Click to collapse
A lot has changed since then, so the Tablet now has WebOS only?
gpzarquon said:
Can someone please provide me the latest download link for an Android Image ? ( preference would be for Bluetooth to work - if that was ever cracked ).
Click to expand...
Click to collapse
Bluetooth works well for version Evervolv 7.1.2 Android Nougat
gpzarquon said:
Also - can't get the Novacom drivers working via MAC OS - tried everything - any ideas ? ( I just want to get Clockwork on - so i can dual boot - Native WEBOS and Android )
Click to expand...
Click to collapse
If you want to use WebOS and Android then the TPToolBox by jcsullin must be use to repartition the internal storage.
gpzarquon said:
Any links to the best way to get Android back on would be appreciated - as i've forgotten most of the steps
I've got Windows 10 on my Mac Book Pro - so if that's the only way to get working Novacom I can do that as well..
Appreciate any help,
Thank You All,
Click to expand...
Click to collapse
WebOS can be used with any version of Android and even share the same swap partition. But requires the use of the TPToolBox to properly resize and create the Android Partition. That must be run by using the Novacom which it loads the TPToolBox into Memory that allows installation.
There are a lot of steps to take, but there are a lot of guides on this site that shows how it is done.
You can follow my guide on how to get Android on the Tablet:
https://forum.xda-developers.com/t/...all-android-roms-with-swap-partition.3901773/
The following guides provide the Novacom drivers built into Linux OS:
https://forum.xda-developers.com/t/hp-touchpad-novacom-repair-android.3960435/
https://forum.xda-developers.com/t/hp-touchpad-debrick-linux-live-cd.4189245/
Good luck!
HP_TOUCHPAD said:
A lot has changed since then, so the Tablet now has WebOS only?
Bluetooth works well for version Evervolv 7.1.2 Android Nougat
If you want to use WebOS and Android then the TPToolBox by jcsullin must be use to repartition the internal storage.
WebOS can be used with any version of Android and even share the same swap partition. But requires the use of the TPToolBox to properly resize and create the Android Partition. That must be run by using the Novacom which it loads the TPToolBox into Memory that allows installation.
There are a lot of steps to take, but there are a lot of guides on this site that shows how it is done.
You can follow my guide on how to get Android on the Tablet:
https://forum.xda-developers.com/t/...all-android-roms-with-swap-partition.3901773/
The following guides provide the Novacom drivers built into Linux OS:
https://forum.xda-developers.com/t/hp-touchpad-novacom-repair-android.3960435/
https://forum.xda-developers.com/t/hp-touchpad-debrick-linux-live-cd.4189245/
Good luck!
Click to expand...
Click to collapse
I'm kind of there now - thank you
I did ( unfortunately ) have to do a mass wipe and lost all my WEB OS - as I was getting more then one boot loader selectable and none would mount or boot ( probably due to bad sizing on my behalf on CM-CACHE and CM-SYSTEM ).
Tried Kit Kat and Nougat - but currently looking at PIE as there's two things i'd really like which are Netflex and Spotify ( I know - it's sad but true ) - thanks for all your help - much appreciated.
Would be interested in LUNE OS and what kind of builds we have since LG took over ( if there are any ) and always a fan of anything UNIX ( UMBUNTO excuse spelling )
THanks Again,
> GPZ
gpzarquon said:
I'm kind of there now - thank you
I did ( unfortunately ) have to do a mass wipe and lost all my WEB OS - as I was getting more then one boot loader selectable and none would mount or boot ( probably due to bad sizing on my behalf on CM-CACHE and CM-SYSTEM ).
Tried Kit Kat and Nougat - but currently looking at PIE as there's two things i'd really like which are Netflex and Spotify ( I know - it's sad but true ) - thanks for all your help - much appreciated.
Click to expand...
Click to collapse
Any version of Android can easily be flash at any time, just follow the guide as is.
gpzarquon said:
Would be interested in LUNE OS and what kind of builds we have since LG took over ( if there are any ) and always a fan of anything UNIX ( UMBUNTO excuse spelling )
THanks Again,
> GPZ
Click to expand...
Click to collapse
Here are the main links for information and how to get it done:
https://forum.xda-developers.com/search/51822741/
https://www.youtube.com/channel/UCKoir6bzzPU-Uq9UjcRR3hw
https://forums.webosnation.com/hp-touchpad/
Thanks very much - I'm enjoying Pie on the touchpad now - but no matter what I do - I can't get LUNEOS to come up as a Boot Option.
Are there any post checks I can do ?
Check the Boot file ?
Check the unarchive of LUNEOS went into correct directory etc ?
I can see now have a LUNEOS mount point in the recovery.
Any help would be appreciated,
Thanks,
> Guy
gpzarquon said:
Thanks very much - I'm enjoying Pie on the touchpad now -
Click to expand...
Click to collapse
Great ! Any version of Android can be easily flash ( install ), using TWRP
gpzarquon said:
but no matter what I do - I can't get LUNEOS to come up as a Boot Option.
Click to expand...
Click to collapse
Any uImage. file that is copy onto the /boot partition will be available at the boot screen. The size of boot partition is limited and if there is not enough room the file would not be copy. I know there is too much information on this site about the Tablet, but all the details has been explained.
gpzarquon said:
Are there any post checks I can do ?
Check the Boot file ?
Click to expand...
Click to collapse
Check the space available in the /boot partition, using TWRP.
gpzarquon said:
Check the unarchive of LUNEOS went into correct directory etc ?
I can see now have a LUNEOS mount point in the recovery.
Any help would be appreciated,
Thanks,
> Guy
Click to expand...
Click to collapse
If you know about Linux commands, it should be easier to understand how to check for partitions size and the file system.
All of my guides provide a flash file (zip) Wipe_All, that will automatically set the Tablet's partitions, format and make it ready to install anything.
But it must be followed exactly with all the steps.
Good luck!