[Completed] Little help with installing custom ROM please? - XDA Assist

Hello people!
I haven't been to XDA for a while since my XPeria T has done a nice job for me, but lately it's starting to show how old it got, not because apps got newer or required more resources, but it started switching keyboard to Chinese without letting me switch back, I can't answer when my phone is ringing, blue screen flashes on YT app etc.
These are just some of the problems I encountered, but I won't bug you with the details as I gave Sony a nice amount of rage on their FB site for releasing damaged software to not-so-expensive phones and leaving them that way...
Before I had HTC WFS, and my friend rooted it for me, so I am still kinda new in this, and if anyone could briefly describe step by step process of installing custom ROM with root I would be very grateful.
The reason I'm asking this is because I'm afraid I'm gonna brick it if I do it on my own, I've done the easy part (downloading SDK and fastboot driver), now I have to install it, find a nice ROM I have, but I still need to install CWM and before I've had some problems (because of the firmware I think, when tried installing 4.4.4 on WFS it couldn't after 4.4.2).
Also, is there any way to back my original software up in case everything goes downhill I can just roll it back, continue complaining how I have a ****ty phone and be satisfied with it anyway?
So, just to be clear, my knowledge of Linux systems isn't great, at least not to experiment on my own (ironic as I'm programming in Python) so if anyone could make it look like this:
1. Do this
2. Do this (in case it fails, do this)
3. Then do this
Done!
I would be forever grateful!
Thanks maties! (sorry if the question is too simple, I've tried gathering information from "xperia t development" thread, but there's so many things and I don't understand what half of them do, I requested to unlock bootloader from Sony and I'll try to do this on my own )
EDIT: We're talking about GSM Xperia T (Croatia, Europe) in case anyone needs that info!

Okay, I think I've successfully unlocked the bootloader since I got this text in CMD after a long headache of installing fastboot drivers because win10 (as windows 8) has to have disabled option for preventing unsignatured driver installation or something.
So I got this text: ...
(bootloader) Unlock phone requested
OKAY [ 0.422s]
finished. total time: 0.422s
So now I'm going to try and install CWM from here: http://forum.xda-developers.com/showthread.php?t=2657190
Not because it's touch, but because it's the last version of CWM posted on Xperia T subforum so I'm hoping I'll be able to install those 4.4.4 ROMS
EDIT: It seems I need to root my phone before doing it, so I'll try to do that before I install CWM

Okay, now I'm stuck (thanks God it's not fatal)
As I'm trying to install CWM to my phone and it's not rooted, I first tried a method above, but .bat file gets stucked @ Daemon started successfully.
So, I decided to give flashtool a shot, installed all the drivers, when I connect the phone everything seems normal, then when I click on root (SuperUser and SuperSU) a little program appears on my XPeria and when I click "make it ra1n" the phone reboots.
Debugging enabled, unknown apps (or similar) enables, fake locations enabled.
Darn.

I'm out...spent whole day packing my old FW downloading other one etc. to find out it's the newer one, I didn't pay attention to number before last one...
If anyone could tell me which version is rootable, I'd be grateful, I don't want to give up yet...
EDIT: Never mind, found everything, I think puzzles are finally coming into places...

Related

[HELP] Looking for Stock Rom for Alcatel OT-983

Hello, and hope this is the right place to post this.
So, without any knowledge about all this smatphone/android stuff, I finally got one by a really good price. An ot-983.
Some friends conviced me to root it. I found a way to do it and noticing all the bloatware from it's original carrier (this phone was carrier unlocked when bought) I decided to clean up a bit.
I ended up cleaning a lot of stuff that I simply didn't use from a \custapp\ folder in there.
Thing is, a day latter I got a notification of a firmware update and I just said yes.
The said update failed, complaining it seems about the lack of some of the deleted bloatware.
Now, here's when the lack of thinking shows.
Wondering about it, I decided to look around options and found the factory reset.
Being a new and mostly empty phone, I did it (wiped clean the sd too),
And there, it went all into hell!
After reboot, it can't get my wireless anymore (have to use a static ip workaround for it...)
Root Checker says it's not properly rooted (using the same rooting technique as the first time doesn't fix it)
superuser still seems to be working, altho it crashes now and then with some errors about permissions.
also, can't get BusyBox working because it says there's no su binary and I can't download an update for it.
In short, I guess I need to get this phone to it's basics, if possible unbranded.
I don't really know what I need for that, but here I am, reaching at you that might help
I guess I need a stock rom and a way to flash it.
I'd appreciate a lot any help on getting whatever it is needed.
*cheers
root alcatel ot 983
ahkronn said:
Hello, and hope this is the right place to post this.
So, without any knowledge about all this smatphone/android stuff, I finally got one by a really good price. An ot-983.
Some friends conviced me to root it. I found a way to do it and noticing all the bloatware from it's original carrier (this phone was carrier unlocked when bought) I decided to clean up a bit.
I ended up cleaning a lot of stuff that I simply didn't use from a \custapp\ folder in there.
Thing is, a day latter I got a notification of a firmware update and I just said yes.
The said update failed, complaining it seems about the lack of some of the deleted bloatware.
Now, here's when the lack of thinking shows.
Wondering about it, I decided to look around options and found the factory reset.
Being a new and mostly empty phone, I did it (wiped clean the sd too),
And there, it went all into hell!
After reboot, it can't get my wireless anymore (have to use a static ip workaround for it...)
Root Checker says it's not properly rooted (using the same rooting technique as the first time doesn't fix it)
superuser still seems to be working, altho it crashes now and then with some errors about permissions.
also, can't get BusyBox working because it says there's no su binary and I can't download an update for it.
In short, I guess I need to get this phone to it's basics, if possible unbranded.
I don't really know what I need for that, but here I am, reaching at you that might help
I guess I need a stock rom and a way to flash it.
I'd appreciate a lot any help on getting whatever it is needed.
*cheers
Click to expand...
Click to collapse
pls i need you to explain to me carefully , step by step how you rooted the alcatel ot 983 , pls i have searching for the past weeks on google without results , pls help me , pls explain carefully , thanks in advance , i will be so happy if you help , thanks again in advance
mohamm said:
pls i need you to explain to me carefully , step by step how you rooted the alcatel ot 983 , pls i have searching for the past weeks on google without results , pls help me , pls explain carefully , thanks in advance , i will be so happy if you help , thanks again in advance
Click to expand...
Click to collapse
I simply downloaded the drivers from alcatel website
and then used the root package from here: <can't post outside links. it's a thread on error-soft dot net
Followed the instructions on the .txt included and it worked.
After that I think I had to install Superuser app (from live store)
be careful. My problems came from deleting some stock apps included and then doing a firmware update.
so, don't delete stuff around if you're thinking in doing the upgrade.
I need original stock alcatel ot 983 rom
hi guys
I bricked my ot 983 after flashing with different alcatel models rom
can some one please give me a copy of original stock rom for alcatel one touch 983
please
my email [email protected]
maybe your handheld is a brand new and nobody mod it yet
be patient bro and keep searching in google with any keyword
help me make tutorial on youtube
ahkronn said:
I simply downloaded the drivers from alcatel website
and then used the root package from here: <can't post outside links. it's a thread on error-soft dot net
Followed the instructions on the .txt included and it worked.
After that I think I had to install Superuser app (from live store)
be careful. My problems came from deleting some stock apps included and then doing a firmware update.
so, don't delete stuff around if you're thinking in doing the upgrade.
Click to expand...
Click to collapse
bro i dont know much about android stuff , but pls can you make a tutorial on youtube like this you can help me and millions out there for rooting the phone , ps help and thanks so much in advance
ahkronn said:
I simply downloaded the drivers from alcatel website
and then used the root package from here: <can't post outside links. it's a thread on error-soft dot net
Followed the instructions on the .txt included and it worked.
After that I think I had to install Superuser app (from live store)
be careful. My problems came from deleting some stock apps included and then doing a firmware update.
so, don't delete stuff around if you're thinking in doing the upgrade.
Click to expand...
Click to collapse
Where did you get the upgrade from ?
My story is like this: rooted, uninstalled some bloat from system and after a factory reset I'm stuck in the initial setup wizard (after completing almost all stages from setup it crashes at the end, after connecting at the google account - tryed to ignore that step but either way it crashes). Fastboot works but adb don't.
I do have another identical phone Alcatel One Touch OT-983 but with no root, with no modifications. Is there a way to backup the original/stock image and flash it over the malfunctioning one and restore it??
I tried with the proprietary upgrade tool from Alcatel but no succes as it close saying I don't need an upgrade because it's the last version of software installed in my phone. I thought even to broke intentionally the rom but I'm afraid that the upgrade utility from Alcatel will let me down, as I read that another users didn't managed to complete successfully the upgrading process. Is there a way to trick the system that has a previous version of Android?
Thank you for taking your time to read this and hope someone has an idea to solve our problem.
Have a nice day guys, you can contact me at puiocku at gmail dot com.
Have someone this stock rom (for Alcatel One Touch 983 (Valencia)) ???
Here is a Alcatel OT-983 rom, not sure which country it is from: https://www.dropbox.com/s/g2ljtrpqru3uihm/rom 983.zip?m
Here is my o2 uk backup rom: http://www.mirrorcreator.com/files/C4VEKHEI/OT-983_backup_uk.rar_links
this .zip file contains the boot.img, system.img and recovery.img
Someone needs to create a clockwork mod recovery for our phones now.
here is the sourcecode for this phone: http://www.mirrorcreator.com/files/85KDRTYP/OT_983_20130103.7z_links
Can't get to recovery
I have a bricked rooted OT 983, by error i installed a ZTE Blade's CM9 ROM and now i can't get my phone to recovery by using ADB that is the only way, i have downloaded the stock ROM but i don't know how to install it. :crying: PLEASE HELP!!!!!!!!!!!!!!!!!!!!
i done the same
Please help!! my phone is stuck on
jrdsetupwizard has stopped
cant get past setup screen
Possible solution for getting back original ROM on "stuck" phone
ryanraven said:
i done the same
Please help!! my phone is stuck on
jrdsetupwizard has stopped
cant get past setup screen
Click to expand...
Click to collapse
I recently "semi bricked", if my Alcatel OT983, if that's possible. It would not boot fully and got stuck on the "jrdsetupwizard has stopped" screen.
Here's what I did. The issue with getting the Alcatel One Touch Upgrade software to work appears to be getting the correct USB Driver installed. There are a number of potential USB drivers. This phone needs the driver in the Alcatel One Touch Upgrade. The stock Windows one or the one used for rooting the phone using instructions from the errorsoft website from the oneofgod will not work with this upgrade procedure.
1. Download the Alcatel One Touch Upgrade software and install on your machine. Open up the folder where the software is installed.
Look inside the folder that is called USB Driver and look inside the appropriate folder for your type of Windows machine 64bit or 32bit (x86) and install that driver for USB - that is the correct one for the upgrade
2. Run the upgrade software whilst connected to the internet. Connect your phone when it is off. You should just get the Android icon i.e. not charging or anything else. The icon should just stay there all the time the process takes place.
3. The upgrade will download. It's when the process gets to about 70% that the phone the starts upgrading. It will take a few moments but when it starts progressing into the late 70s and 80s you should be well on the way. At least that's how it went for me and I got my phone back!
Hope this helps.
to Hajj_3 :
Tanks for share the ROM.. I need it to recover my friends phone..
I just got this phone, not looking to root it yet as theres no option for a custom rom yet.
didnt want to start a new thread as theres not really any section for this phone yet.
Everything was fine until i installed the firmware update. Now applications cannot access the mic. Some complain about it being in use by another app. others like video editor or sound recorder will record, but the video recorder there is no file, and sound recorder crashes when you hit stop.
Alcatels website is useless, wasnt working yesterday, today it is but cant find any contact details incase its a bug in there firmware. Everything works fine except for that. Which is annoying because i use RTA software and now it doesnt as it cant access the mic.
any ideas?
Hi guys,
I've rooted my phone with abd and udpate.zip a long time ago, and it was fine till some days ago it stopped from receiving calls and the home button does nothing when pressed, although in recovey mode it works.
I've done a hard reset, reflashed the recovery.img, system.img and boot.img I've found in this post with fasboot, but did not solve the problem.
I've tried a firmware update with Alcatel's own software but it just keeps saying my firmware is updated already. I've also tried to edit the proinfo file, but I don't know what to change in the file. You can see more about that method here: http://forum.gsmhosting.com/vbb/9772370-post8.html
My guess is that the files that are corrupted and preventing me from receiving calls are somewhere else than those img's I've flashed. Has anybody got a FULL backup of his rom (e.g. Rom Manager) so I can recover the phone completely?
Thanks!
upgrade software
bussand said:
I recently "semi bricked", if my Alcatel OT983, if that's possible. It would not boot fully and got stuck on the "jrdsetupwizard has stopped" screen.
Here's what I did. The issue with getting the Alcatel One Touch Upgrade software to work appears to be getting the correct USB Driver installed. There are a number of potential USB drivers. This phone needs the driver in the Alcatel One Touch Upgrade. The stock Windows one or the one used for rooting the phone using instructions from the errorsoft website from the oneofgod will not work with this upgrade procedure.
1. Download the Alcatel One Touch Upgrade software and install on your machine. Open up the folder where the software is installed.
Look inside the folder that is called USB Driver and look inside the appropriate folder for your type of Windows machine 64bit or 32bit (x86) and install that driver for USB - that is the correct one for the upgrade
2. Run the upgrade software whilst connected to the internet. Connect your phone when it is off. You should just get the Android icon i.e. not charging or anything else. The icon should just stay there all the time the process takes place.
3. The upgrade will download. It's when the process gets to about 70% that the phone the starts upgrading. It will take a few moments but when it starts progressing into the late 70s and 80s you should be well on the way. At least that's how it went for me and I got my phone back!
Hope this helps.
Click to expand...
Click to collapse
The problem is, the upgrade software link doesn't work anymore :\.
ht tp: // ww w1. alcatelonetouch.com/global-en/ support/download/one_touch_ 983.html
(remove of spaces, im a new user so they won't let me post one)
Is there anyway someone can find a link for it because i have been searching for ages and haven't found one.
http://www.alcatel-mobilephones.com/global-en/support/download/one_touch_983.html

Lenovo IdeaTab A2107A-F

I am starting this thread to hopefully encourage discussion on the Lenovo A2107A-F tablet variant.
I am aware there is an existing thread on the A2107 here:
http://forum.xda-developers.com/showthread.php?t=1982334
but that thread is concentrating on the A-H (dual sim + wifi) variant which is somewhat different from the A-F (wifi only).
So far I have not found any custom rom development, which is disappointing as the stock rom leaves a lot to be desired IMHO. While the current OTA update is fine for web surfing, reading emails etc, HD video playback (particularly YouTube HD) is very poor. Also the recent OTA update forces an optimization of apps on bootup which leads to long boot times
You can root and install CWM by following steps 1-5 from the 1st post here:
http://forum.xda-developers.com/showthread.php?t=2044496
Note that "-Update 3-" mentioned in the post does not appear to work for the A-F model!
So, has anybody any leads on possible development on this tab?
Any tips on improving performance?
My first tip:
If after installing CWM you cannot get to the CWM recovery screen after powering down the device, look for for the file "/system/reboot-from-recovery.p". If it's there, either delete it or move it to some other place. This file restores the default recovery on a system reboot.
I got bitten by this a couple of times
Thanks for starting a separate thread for the A2107A-F. I'm new to Android devices and just got this one two weeks ago. I'd like to get rid of several of the apps that I have no use for and from what I understand that means I have to root it. I got lost in the details of the other thread, but I tried reading all of it. I'm on Vista and somewhere along the line I installed one of the suggested ADB drivers via PDAnet. Device Manager is showing Android Phone and under that Android ADB Interface. I wasn't sure if that matched closely enough with the step-by-step threads since I don't really think of the device as a phone, so I've been holding off on going further. I've tried using a few other drivers that were suggested in the large thread and some other threads, but Vista always tells me the current driver is the most up-to-date one.
Do you know if it's okay for it to say Android Phone rather than something else?
Thanks. I've got some other questions about the specifics of some of the other steps, but this is probably enough to get started.
My apologies in advance if my posts are too long and my questions are too basic for these forums. Feel free to point me somewhere else based on what I'm asking for. I'd honestly appreciate any leads towards my goal of getting rid of the bloat on this device and making it more responsive. (Wow! The portrait to landscape lag is really bugging me now after reading around here).
Anyway, my primary purpose is to remove the seemingly unneeded programs, services and widgets that come with the tablet. Maybe I'm just ignorant about these things, but at this time things like messaging (IMO), mapping, and some of the other default features are of no use to me. They seem to be eating up a lot of resources. I can kill some of the services I think they are associated with, but they keep popping back up.
I did watch the "noob" video (color me a tiny ant to be squashed) and did try to search for an answer to get me even started. I've read the huge main A2107A thread (80+ pages) and tried three of the suggested ADB drivers with my Vista 32 setup for my A2107A-F. The only one that even seemed to connect was ADPnet and it showed the tablet as a Android Phone. Maybe I'm just too paranoid, but after the multiple "brick" posts I'd like to make sure I'm on the right path before trying to "root" the device which appears to be the first step in removing all the extra stuff Lenovo added.
Not that it matters, but I've had the tablet for almost two weeks now and my favorite things are Slacker Radio, Scrabble, Roll It and Zen pinball. I do play Words with Friends with my wife, but I don't like it since some of the words they allow are not valid in Scrabble (which I used to play as an expert competitively face-to-face).
If you are so inclined, feel free to PM me for a Scrabble game. I promise I will not use anything other than my brain and the built in dictionary to make my plays. (I'm a bit rusty since I gave up competitive Scrabble in 2006).
So, long story short... Thanks in advance for any and all advice you can give on slimming down the Lenovo A2107A-F. And if you want an honest Scrabble challenge feel free to PM me.
As far as checking if your drivers are installed properly I would open a dos (command) prompt in window and from within the window change to the directory where you have the 4.03root files. From the command prompt type 'abd.exe shell' and you should see something like "[email protected]:/ $". If you don't see this then you will not be able to root! You need to make that USB debugging is turned on on your device you have an entry in the device manager for ADB Interface (expand on the device which you have showing up).
I am no expert, and I struggled with this on my first go also
Once rooted you can then install Titanium Backup from the play store and use it to get rid of the bloatware! Proceed with caution however as it is possible to remove critical system apps!
degsie said:
As far as checking if your drivers are installed properly I would open a dos (command) prompt in window and from within the window change to the directory where you have the 4.03root files. From the command prompt type 'abd.exe shell' and you should see something like "[email protected]:/ $". If you don't see this then you will not be able to root!
Click to expand...
Click to collapse
Thanks! That's the type of test suggestion I was looking for to make sure I was on the right path with the driver.
So has anyone tried creating a rom for this tab yet? I've been doing some research into porting another rom to work on the A2107A-F, but want to make sure there isn't one already.
I just received a notification of a new firmware update for the A2107A-F. This would be the second available update.
Has anyone else gotten this and taken the plunge yet? I'm curious if this is possibly Jellybean, as some of the larger screen IdeaTab models run this.
Sent from my IdeaTab A2107A-F using xda app-developers app
ssenemosewa said:
I just received a notification of a new firmware update for the A2107A-F. This would be the second available update.
Has anyone else gotten this and taken the plunge yet? I'm curious if this is possibly Jellybean, as some of the larger screen IdeaTab models run this.
Sent from my IdeaTab A2107A-F using xda app-developers app
Click to expand...
Click to collapse
DON'T DO THE UPDATE!!! I lost root access and now I don't know whether or not if I try to re-root if its gonna brick my tablet!
Kevin147 said:
DON'T DO THE UPDATE!!! I lost root access and now I don't know whether or not if I try to re-root if its gonna brick my tablet!
Click to expand...
Click to collapse
I lost root after applying the first update a while back. That's typical when updating. Afterward, I was able to re-root mine again using the same procedure as before. All was well. So, don't panic...yet.
Can you report on what other changes the update made? Is it Jellybean? Or maybe ICS 4.04?
ssenemosewa said:
I lost root after applying the first update a while back. That's typical when updating. Afterward, I was able to re-root mine again using the same procedure as before. All was well. So, don't panic...yet.
Can you report on what other changes the update made? Is it Jellybean? Or maybe ICS 4.04?
Click to expand...
Click to collapse
Well, I just re-rooted my tablet and everything was successful! There is absolutely no difference AT ALL with that so called "update".
Kevin147 said:
Well, I just re-rooted my tablet and everything was successful! There is absolutely no difference AT ALL with that so called "update".
Click to expand...
Click to collapse
Although I have my A2107A rooted and tweaked to my satisfaction, there are a few lingering issues that I'd hoped an update would correct:
1) The neutered Bluetooth stack. The tablet is supposed to work with Bluetooth keyboards, mice, etc. It doesn't. Although I've gotten it to talk to an external GPS module, other Bluetooth data connections simply will not work. Oh, and Bluetooth audio? Forget about it!
2) Some settings that are present in stock ICS builds are just omitted in this one. As an example, the ability to specify a default TTS voice. It's present under settings in my wife's tablet and every other ICS build I've ever encountered. Not this one!
Sent from my IdeaTab A2107A-F using xda app-developers app
Kevin147 said:
DON'T DO THE UPDATE!!! I lost root access and now I don't know whether or not if I try to re-root if its gonna brick my tablet!
Click to expand...
Click to collapse
I was rooted too, lost root access (only with some apps!) after the 130221 update Feb 28. I'll try the same root procedure as before to see if I can get it back. Glad to see a thread on the popular US version A2107A-F. Maybe someone will port Jelly Bean to this tablet! Doesn't appear Lenovo wants to do it...
Rob
I cannot get this 'update' to install after downloading. The tablet reboots to CWM during the install (I am rooted with CWM installed) and when I attempt to manually select the update.zip from /sdcard/googleota/ I get on error (status 7). In desperation I re-loaded the stock rom that I found on another thread and when the tablet attempts to update I get a "assert failed apply_patch_check( /system/app/applicationsprovider.apk)" error Anybody any ideas?
degsie said:
I cannot get this 'update' to install after downloading. The tablet reboots to CWM during the install (I am rooted with CWM installed) and when I attempt to manually select the update.zip from /sdcard/googleota/ I get on error (status 7). In desperation I re-loaded the stock rom that I found on another thread and when the tablet attempts to update I get a "assert failed apply_patch_check( /system/app/applicationsprovider.apk)" error Anybody any ideas?
Click to expand...
Click to collapse
I'm in exactly the same boat as you. I'm getting the same exact error. except that I do not have CWM installed (I am rooted though). Perhaps there's a problem with the update.zip?
Something odd that I noticed however: After the tablet reboots into recovery mode, the update fails, and I go to browse for the update.zip, the sdcard/googleota directory is missing (along with everything that follows it alphabetically). They reappear upon normal boot. I've tried copying it to a directory closer to the beginning of the alphabet and it does show up while in recovery mode. But it still will not install.
Maybe I somehow do not have the available space to perform the update? Is that possible? I show plenty of available space on both sdcards. Could we somehow be below a certain ROM space threshold necessary for an update?
I think in my case because I loaded a 'stock' rom I got from another thread, this rom is failing a verification test the update is doing before install. I do not know how to get around this! I'm continuing my search, but I am not so confident this will be resolved easily...
degsie said:
I think in my case because I loaded a 'stock' rom I got from another thread, this rom is failing a verification test the update is doing before install. I do not know how to get around this! I'm continuing my search, but I am not so confident this will be resolved easily...
Click to expand...
Click to collapse
Well, I am running a stock rom. I am unwilling to "mess with success" until there's a 100% reproducible way of recovering if it fails. And, so far, everything I've read in the other A2107A thread has been hit or miss for the A2107A-F people.
Anyway, If the update is performing a verification test, then it my "virgin stock ROM" should certainly pass it. The only thing that I did is to root it. Hmmm...could the update be testing for that and refusing to install if it detects a rooted device? I would tend to doubt that, since the previous ota update went just fine. I lost root in the process but easily reapplied it afterward.
Thoughts?
Interestingly, I flashed the A2107A-F_S483_121115 rom (again, found in another thread) as I was having verification problems with the OTA update just released from lenovo which was available from the A2107A-F_S484_121211 flashed rom. While the S483_121115 rom appears to be older, I no longer get the option to update via OTA as the tablet is telling me that my s/w is up to date! Go figure.
It's really too bad this device hasn't taken off. If I actually knew how to dev then I would start developng ROMs for it. I'm enjoying it now that I have root and got rid of bloat.
Hey guys. Just wanted to say if someone can send me a stock rom and be willing to test, I'll try to do up a good rom for the -f models. I'd use mine for the stock rom, but I've edited a lot of the system, so no go there. If you have the stock rom or want to be a tester, let me know.

How to find stock ROM files for my BL unlocked XT925 with no backups?

First a few disclaimers to explain why I'm here.
- My secondary intention with this question is finding some answer as generic as possible to also help other people. Of course my primary intention is fixing my own issue, but the biggest part of it from what I can tell in the past 8 hours have been finding ROM files. All links are broken, except for 4.1.2 and none of those worked for me. In fact, they bricked my phone pretty hard.
- I'm on a mac. It's a nightmare finding tools for the mac, but I doubt any of them would really be any use for my case, one reason why I didn't even bother going for a windows vm. Another one is I'm traumatised by installing and running VMs. Finally this is for the challenge and learning a bit more.
- I've being trying to fix this through lots of research in the past 8 hours and I do know a few bits about going around and doing things (so sad this guide had no repercussion so far). But clearly, I'm dumb enough to brick my phone twice with no backups. At least could figure it out the first time (I had more time in hands as well). Please consider this. This means I've tried a lot of stuff you may wanted to advise, but it also mean I may have missed something obvious in the middle.
Okay...
By "bricked" I mean:
1. I can't go through the same process I did before to flash any CM image. CWM won't flash CM11 and CM12 recovery complains my bootloader isn't 4.4.
2. Both CWM and twrp recoveries should allow touch. None work, so I an't use twrp.
3. Battery keeps getting low and I've got no clue how to charge it to full again or even see how much it is at without installing twrp, which keeps getting uninstalled randomly at reboots, despite all of this topic about a solution. `fastboot getvar battery-voltage` doesn't show it. The mac script (which I was about to write myself based on op) also doesn't seem to help. In my case, I've removed the `./fastboot` because I've got it on my shell path.
I believe (1) happened, as I said on the disclaimer, right after I've flashed one of those 4.1.2 ROMs. By "flashed" I mean running the BAT file which mostly works on mac. ECHO of course wouldn't show the messages of progress there, but all fastboot commands do run.
And I also believe if only I could find 4.4 stock ROM files they might work or, at least, bring bootloader back to where it was so I could install CM12 again. And as far as I could notice without having Windows to try, no windows tool would really help here. That RSD Lite for instance, looks like it's just a GUI to run fastboot commands.
Above ALL
I just wanted to find a ROM stock file which I could fastboot flash into xt925 to reset it as hard as possible from zero and that the link will probably not break in the future for whoever may need it.
I figured THIS shouldn't be too hard to find, even for mac only, but it has been.
PS: Being able to fix the battery thing is also very important and quite a relevant follow up on the question! Right now I'm stuck with a ROM file that might work, but got no battery to try! ( 10 hours debugging now... )
only one stock kitkat rom for XT925 ! i'll upload this for you !
You know, if this works I'll have to, at least, go through some of your 187 posts and find a dozen or so to thank you way more than once!
I've now downloaded [this one](http://forum.xda-developers.com/showpost.php?p=63163078&postcount=6), which [he also posted again later on](http://forum.xda-developers.com/showpost.php?p=63272842&postcount=2), hoping it will do it! If it does, I'll try to upload in this post, as it looks like XDA hosted files last for much longer than anything else.
Only problem for flashing anything now is I can't seem to get enough battery!

Updating advice please ! Reroot failure

Hi everybody ! Ill try to keep it simple as I'm sure its covered somewhere but here goes ....
Ive been using my shield portable, rooted, for ages now no problems.
Like many Ive updated it in short ever since nothing whatsoever has worked properly , most annoyingly the screen doing backflips when you go near it and hundreds endless strange updates when rebooting.
Anyway I don't think you or I or any of us want to waste time trying to figure out why its done any of this but I just want to be able to fix it. I guess I'm going to have to start again somehow! its worth noting here that all my backup apps like Helium now don't seem to work.
After the update I of course ReRooted and it appears fine from boot loader , still says unlocked. but upon usage its clearly very confused about whether its rooted or not !
In short its useless. Advice please My kung Fu warriors
May your arrows fly straight and true
I have no idea about the various issues, but I would perform a factory reset, and clear cache and dalvik cache using at least 3 swipes per each function. The method of rooting I recommend is by flashing a zip of SuperSU from a custom recovery menu. CWM or TWRP are both available for the NSP. After flashing SuperSU, when you reboot and go into SuperSu you'll see that it's installed (locked down tighter) as a system app.
Downloads:
SuperSU (latest stable version) v2.65
CWM Recovery Menu (latest version) v6.0.4.4
TWRP (Modified recovery (based on TWRP v2.8.7.0)
Sorry. This is the best I can offer you right now. If this doesn't work I would reflash the stock images of whatever OTA you wanna be on. The images can be found @:
SHIELD Open Source Resources and Drivers. You'll need at least the platform-tools portion of the Android SDK (to use Fastboot to flash from recovery). A user friendly PC app that can basically do all this sort of stuff is Shield Ram v1.1. You might find that easier to use.
Oh and here's the latest Minimal ADB and Fastboot Drivers installer [v1.3.1]
If you need further help, let me know.
Hi ! Thanks for the good advice.
I should have mentioned, I'm using a Mac now.
From what I understand it's still possible , maybe
Even easier.....
Sorry to throw a spanner in your super helpful works !
Thanks again
[/COLOR]
Marrhead said:
Hi ! Thanks for the good advice.
I should have mentioned, I'm using a Mac now.
From what I understand it's still possible , maybe
Even easier.....
Sorry to throw a spanner in your super helpful works !
Thanks again
Click to expand...
Click to collapse
Yeah, pretty much the rule is generally "as long as you can still see the screen, it's probably fixable". Sounds to me like your best bet, would be to download the OTA you wanna be on, and flash a new install to your Shield. It's the quickest way from A-B. I'm about 99% sure that this would solve the problem (as long as you re-root it properly). Though if you have your reasons, you can try some of the other things first. You're welcome and let me know how things go!
So where does one get the latest OTA?
cheers
Marrhead said:
So where does one get the latest OTA?
cheers
Click to expand...
Click to collapse
I did link up the main Nvidia page that would lead to the OTA images, but here's a direct link to DL just the OTAs:
Edit: you can get there through the link I included in my previous post: SHIELD Open Source Resources and Drivers. I'm having issues with editing posts, and all sorts of odd **** with the link trying to post a more direct link. It's an Nvidia site, just scroll down to Shield Portable Recovery OS Images (something like that).
Unfortunately there are only Linux and Windows downloads available. I'm not sure what your best option would be, as you have a Mac. You could contact Nvidia support, and see what they say about it. Sorry, but I don't think I can probably help much more than this.When I contacted Nvidia support about a year ago, they were pretty helpful. Hopefully you get this sorted soon. Oh and the OTAs are flashed via a terminal/command prompt. So if you can emulate DOS on your Mac (which I don't see why not...DOSbox? maybe) then that sounds to me like the solution.
Ok , hit another brick wall. Im using a windows computer now, followed all the instructions i can find, and now the bootloader seems dysfunctional.
Ive got adb and fastboot and its recognising the device but once rebooted into bootloader which loads fine, the commands say no device found and nothing works in this mode.
If i hit recovery mode then a little dead android appears! poor little guy.
I tried shield ram but it had same problems, seems to run fine but cant find shield once its in bootloader...
Ive got the image zip of the update i want to flash but no idea if im doing it right- not sure how to use it.
Help!

[Completed] Wacom Cintiq Companion Hybrid ( DTH-A1300L ) android needs custom rom or stock bad

I have a Wacom Cintiq Companion Hybrid ( DTH-A1300L ) android version needs help in so many ways. I bought it because I really need one for one of my jobs, yet can't really afford the crazy overpriced insanity that is a new Wacom so the reason it was so cheap was "can't connect to the Play Store. I know, hella foolish, I thought I could fix it by rooting it, but this thing is like level 10 as there is so little info as no one wanted to touch them it seems. I did find one guy on this forum that at one point rooted I am fair to average at rooting and the understanding of all that surrounds it. I have happily and successfully rooted my phones and tablet but I am no pro and fairly good at having gaping invisible holes in my info or logic when it comes to things like this.
Most frustrating is this thing is stuck on android 4 . 1 . 1 for no good reason I can imagine. It has dev tools installed after factory data reset but no google apps. (It arrived factory data reset)
I tried the relevant framework and store and the delete the cache trick to no avail. It can not update and can not even get to the Play Store.
Sooo the bad news is; no Google apps. No updates offered and stuck on some weird what looks like not stock version of 4 .1 .1 Jellybean.
When I plug it into my PC via USB it does not even show up in device manager.
The good news is I rooted it. Checked with root checker (unfortunately for now its Kingroot)
1. I have no idea how to make a back up from here. (no USB connection to PC issue)
or
2. what rom will work as my device is not listed on any of them. It would be great to find the stock rom as I am afraid this things cool and weird cintiq mode, pen function like abilities may be disabled or rendered useless with just any android rom.
Is there anyway to somehow find the stock OS on my device through boot loader? A place to find my stock or like rom. A clever work around?
Thanks in advance. for any who take up the challenge and offer any help or thoughts.
Cheers
Anyone know
What clockwork or custom recovery should I use?
Duende101 said:
I have a Wacom Cintiq Companion Hybrid ( DTH-A1300L ) android version needs help in so many ways. I bought it because I really need one for one of my jobs, yet can't really afford the crazy overpriced insanity that is a new Wacom so the reason it was so cheap was "can't connect to the Play Store. I know, hella foolish, I thought I could fix it by rooting it, but this thing is like level 10 as there is so little info as no one wanted to touch them it seems. I did find one guy on this forum that at one point rooted I am fair to average at rooting and the understanding of all that surrounds it. I have happily and successfully rooted my phones and tablet but I am no pro and fairly good at having gaping invisible holes in my info or logic when it comes to things like this.
Most frustrating is this thing is stuck on android 4 . 1 . 1 for no good reason I can imagine. It has dev tools installed after factory data reset but no google apps. (It arrived factory data reset)
I tried the relevant framework and store and the delete the cache trick to no avail. It can not update and can not even get to the Play Store.
Sooo the bad news is; no Google apps. No updates offered and stuck on some weird what looks like not stock version of 4 .1 .1 Jellybean.
When I plug it into my PC via USB it does not even show up in device manager.
The good news is I rooted it. Checked with root checker (unfortunately for now its Kingroot)
1. I have no idea how to make a back up from here. (no USB connection to PC issue)
or
2. what rom will work as my device is not listed on any of them. It would be great to find the stock rom as I am afraid this things cool and weird cintiq mode, pen function like abilities may be disabled or rendered useless with just any android rom.
Is there anyway to somehow find the stock OS on my device through boot loader? A place to find my stock or like rom. A clever work around?
Thanks in advance. for any who take up the challenge and offer any help or thoughts.
Cheers
Anyone know
What clockwork or custom recovery should I use?
Click to expand...
Click to collapse
Greetings and welcome to assist. If you have root yoy can try installing gapps through flashify it may work. For custom rom there is an excellent guide here
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
and for custom recovery an excellent guide here
https://forum.xda-developers.com/android/software/guide-how-to-compile-twrp-source-step-t3404024
Good luck
Sawdoctor
sawdoctor said:
Greetings and welcome to assist. If you have root yoy can try installing gapps through flashify it may work. For custom rom there is an excellent guide here
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
and for custom recovery an excellent guide here
https://forum.xda-developers.com/android/software/guide-how-to-compile-twrp-source-step-t3404024
Good luck
Sawdoctor
Click to expand...
Click to collapse
Thanks, I will see what I can find out and report back. Also editing from device to check date
sawdoctor said:
Greetings and welcome to assist. If you have root yoy can try installing gapps through flashify it may work. For custom rom there is an excellent guide here
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
and for custom recovery an excellent guide here
https://forum.xda-developers.com/android/software/guide-how-to-compile-twrp-source-step-t3404024
Good luck
Sawdoctor
Click to expand...
Click to collapse
Excuse my noobness. Flashify looks good, I installed it, but don't I need some image from somewhere either the stock OS or a new one for it to work? Not sure how to get Gapps from there.
It did I think, find something, a "restore kernel" and "stock recovery" I am unsure did it find my stock kernel and recovery and or ROM and I should boot from that? ( again apologies a-lot of new info and its getting a bit swirly) In otherwords since my device is not listed any where and at this point any working Android version will do, I am wrong to try and reboot from this? These devices are supposed to come stock on 4.2.2, so I am hoping perhaps incorrectly it will go back to that? That would be ideal at this point.
So I can work again whatever works.
Also I a bit concerned about the "date" I posted from on one of these. I think I posted from the Wacom. Perhaps the problem in deeper than I thought as that is Linux time 0?
I think it self corrected but originally it said I posted on Jan 1 1970...
As for custom ROM, I probably wont be able to make my own custom ROM, even though I would love to take to the time to learn, for now I have too many art and work related deadlines.
I was hoping for one that already existed that would work with my device.
Perhaps I misunderstood something about how all this works? Also I do not have Unbuntu. I should as I support an open internet, but WINE really does not run the Adobe products I need for work so
I am stuck with Windows.
Duende101 said:
Excuse my noobness. Flashify looks good, I installed it, but don't I need some image from somewhere either the stock OS or a new one for it to work? Not sure how to get Gapps from there.
It did I think, find something, a "restore kernel" and "stock recovery" I am unsure did it find my stock kernel and recovery and or ROM and I should boot from that? ( again apologies a-lot of new info and its getting a bit swirly) In otherwords since my device is not listed any where and at this point any working Android version will do, I am wrong to try and reboot from this? These devices are supposed to come stock on 4.2.2, so I am hoping perhaps incorrectly it will go back to that? That would be ideal at this point.
So I can work again whatever works.
Also I a bit concerned about the "date" I posted from on one of these. I think I posted from the Wacom. Perhaps the problem in deeper than I thought as that is Linux time 0?
I think it self corrected but originally it said I posted on Jan 1 1970...
As for custom ROM, I probably wont be able to make my own custom ROM, even though I would love to take to the time to learn, for now I have too many art and work related deadlines.
I was hoping for one that already existed that would work with my device.
Perhaps I misunderstood something about how all this works? Also I do not have Unbuntu. I should as I support an open internet, but WINE really does not run the Adobe products I need for work so
I am stuck with Windows.
Click to expand...
Click to collapse
If you just want to be able to install apps from the playstore then this is a simple alternative
https://www.xda-developers.com/unshackle-your-device-from-the-google-play-store-with-apkupdater/
If your phone is rooted then flashify can flash zips like gapps without the need for a custom recovery. If you are serious about trying to make your own rom/recovery then use a virtualbox in windows. http://www.osboxes.org/ has plenty of prebuilt virtual linux machines that will run on windows
Regards
Sawdoctor
I appreciate all your help. I got the "google of every kind from Gapps on has stopped" is over, which was intense as it popped up every few seconds, I somehow got that to quit by reloading the proper one from the APK Pure app which was an odd work around but nothing else was working. Still have this unsettling bare bones screen and none of the stock apps as well as it being stuck in 4.1.1. This device was made for 4.2. and I assume it was on here at one point.
I wonder if that alone could cause hardware issues. I thought about taking out the battery, until I realized that thing is inaccessible as a thing can be without wrecking the industrial glues and taking the entire thing apart which sounds
like an accident waiting to happen and possible making things worse. I imagine that is last case scenario.
Like I said I would love to make my stock reload, at this point that would be great as this thing seems unstable and no trick makes the play store work or allow me to sign into the device with my google email.
I think you are saying to make my own recovery/ROM of my own device I need to do the virtual box thing. Correct? Or is that for writing your own custom ROM? I can try that; make my own recovery that is, as it is not on CWM or TWRPs supported devices list so I have no choice and all in all would prefer the thing to load as if it was fresh out of the box not this 4.1. One serious hiccup I have found trying to use my PC is my device is not recognized as a storage device or otherwise. Not sure if this is due to the weird settings of Cintiq mode or simply because the thing is in a very weird state of 4.1.1. So that may make making changes via computer impossible. I am not the type to give up. Thanks again Saw
Here also is a sum up I added to a the just basic question of Can you find the Stock from a recovery device. Basically is there any way to return a device to stock with no ROMs available to do so, as in extract if from the device itself.
Additional backstory if helpful.
"I have a Wacom Cintiq Hybrid running Android 4.1 that is ( now ) rooted..
This is a very bad thing. The Real Stock ROM has palm rejection and all the drivers to make it work as a tool. So stock is the ideal but it is clearly not stock as my device supposedly came in the
box running 4.2 and with software and drivers to make it work properly with the pen. This has nothing. No software and the smallest amount of apps possible. Worse this is no custom ROM its on ( I think) as it would be the worst one ever and it was not rooted on arrival. I have no idea what happened before I got it. I may have made the mistake of rooting it really as I found out to my dismay there is no ROM support. So back to square one. I bought it ( very cheap for one of these ) "stuck and unable to go to the play store" and I did not realize until I got it, on a version of Android it was not meant for. Wacom is totally and woefully unhelpful in every way. They seem to want to quietly put this device behind them at the expense literally of their customers."

Categories

Resources