Related
[how-to] another advenure: From German "unrootable" 3.2 build10 to rooted 4.0.3R5a
Hi there,
after about 5 nights, this "morning" at 4am, I won over Sony and M$ :highfive:
So i want to write this little tutorial for the ones, who might still be stuck on 3.2 build10.
I bought my tablet S 114DE/S, German with 3G, right before Xmas. Thought, it would be an easy task ... ha-ha.
First thing I read was, that build 10 is unrootable. F#?!
Started reading everyhing on XDA and other forums. Also read Cat McGowan's "adventure". Tried to do it like him... but as my tablet is German region an region changer only works with rooted devices, I could not flash his US files. But the idea was born.
Found the thread: XDA Developers > Sony Tablet S > Tablet S General > NEW Update Links Inc Tablet S/P R5A & Xperia S R6b
The "oldest" downloadable German original Sony FW was ICS R2a. I was not sure if this was still rootable, i would have liked to find a R1a, but what the heck, worst case is a not rooted ICS, which is still better than an unrooted 3.2!!
Downloaded, put on SD an flashed with recovery mode. Went fine.
So all you need to get away from "unrootable" build10 is a rootable original FW for YOUR tablet's country code!!! Hope you find one. There are many in the above mentioned thread.
Installed ADB automatic installer, no probs. i have Windows 7 pro 64bit.
Would be really NICE to add a clearly visible advice to also install the ADB driver (most likely MANUALLY on some systems) before using any special tools... I did not see any advice, maybe I was blind...
At least tell everybody to check, if the driver is working, by booting in recovery and looking at Windows device manager.
Problem is to find the right driver...if you simply choose the INF like for the "normal boot" ADB device, W7/64 does not install properly, you can get an error... really badly misleading message comes from Windows: It's telling something about MTP device ... well, actually you need the ADB driver!! Took me some hours... but as I found that problem only later, it took me 2 nights before, trying Condi's flasher and AIO 5.3 tool, without success...
OK, ADB drivers were installed (I only had the normal boot drivers at that time).
Downloaded Condi's AIO 5.3 tool, used the "root device" option, everything went OK, I was really happy! Rooted ICS R2a. First big step. 3.2 build10 unrootable? Not really... you only need a rootable original Sony firmware, flash it the normal way.
Then, I wanted to upgrade to R5a of course!
Condi's flasher 2.2. did not work. Maybe also because of the missing ADB driver for recovery mode?? Dunno. It always ended with: System.zip and all the other zips "not found", although I also tried pushing them manually to the internal SD before... when checking later, they disappeared.
Tried AIO 5.3 and custom signed zip. Always stuck in recovery mode with "Status 7" Error, like described in post #72 in this post:
XDA Developers > Sony Tablet S > Tablet S Android Development > [FW R5A WIFI/3G] NEW! custom preROOTed newest stock nbx03 R5A with R1A's recovery!
Also here, it would be nice to bring the advice (install ADB drivers for recovery mode) BEFORE! It does NOT appear in the tool's window IF you are stuck!
After finding the right driver, it was no problem installing the prerooted double-flash zip with the AIO tool... Also here, do not panic when the "Status7" Error appears... it's normal, it disappears after a few seconds and at the same time, the hint about the driver comes up in the command window...
Btw I had no problems with missing google market or apps or any Sony applications. Google play is working, also Sony remote etc.
OK, that's it!
Waiting for 4.2
Have fun with your rooted Sonys!
Many thanks to Condi and the other devs for the tools, videos, tutorials... they may not be perfect, but without, it would be impossible for guys like me :angel:
Daniel
Hi all,
I have Gionee elife s5.5 and it had english rom (android 4.2.2) with google play installed. The problem was it kept freezing a couple of times a day, so I tried to reinstall the only official rom I could find (CBT5701A01_A_T2898) with flash tool. After the installation, it got stuck in the boot loop.
I tried:
- entering the recovery mode and cleaning the cache
- entering the recovery mode and factory reset/wipe
- reinstall rom with flash tool with update option
- reinstall rom with flash tool with download option
- reinstall rom with flash tool with download and format option
- reinstall rom with flash tool v3.1344.0.212 and v5.1352.01
So far, no luck. The only answer I can think of is that this rom is not for my phone version. Anybody has any idea what can I do? Or does anybody have some other rom I could try to install?
Thanks in advance.
tchs said:
Hi all,
I have Gionee elife s5.5 and it had english rom (android 4.2.2) with google play installed. The problem was it kept freezing a couple of times a day, so I tried to reinstall the only official rom I could find (CBT5701A01_A_T2898) with flash tool. After the installation, it got stuck in the boot loop.
I tried:
- entering the recovery mode and cleaning the cache
- entering the recovery mode and factory reset/wipe
- reinstall rom with flash tool with update option
- reinstall rom with flash tool with download option
- reinstall rom with flash tool with download and format option
- reinstall rom with flash tool v3.1344.0.212 and v5.1352.01
So far, no luck. The only answer I can think of is that this rom is not for my phone version. Anybody has any idea what can I do? Or does anybody have some other rom I could try to install?
Thanks in advance.
Click to expand...
Click to collapse
Where did you get the phone? Try looking here, translate it using Google.
http://www.mgyun.com/
I bought it on ebay from China. Thanks for the link but no luck. I've downloaded the new rom and the romaster program (I'm guessing I should use it for the installation) but the program is not detecting that the phone is connected via usb. Same thing with vroot.
Since this rom is in another format, I was thinking maybe I could install it via adb option in recovery mode but I'm getting 'device not found' message when I try to start adb shell.
tchs said:
I bought it on ebay from China. Thanks for the link but no luck. I've downloaded the new rom and the romaster program (I'm guessing I should use it for the installation) but the program is not detecting that the phone is connected via usb. Same thing with vroot.
Since this rom is in another format, I was thinking maybe I could install it via adb option in recovery mode but I'm getting 'device not found' message when I try to start adb shell.
Click to expand...
Click to collapse
Have you installed the drivers for the phone?http://gionee.co.in/portfolio/elife-s5-5/#t4
---------- Post added at 03:12 AM ---------- Previous post was at 02:30 AM ----------
Try here, you need to register.
http://www.yougerom.com/bbs/forum.php?mod=viewthread&tid=265
Yes, I installed usb and phone drivers. I also installed adb driver (at least adb driver installer says it is installed as android composite adb interface) and yet when I try adb shell, deamon starts ok but I keep getting the message that the device is not found.
The rom from your link is the same one I already have, but thanks anyway.
All this is very frustrating. Seems like everywhere I go, I hit the wall:
- if the phone has sdcard I could try install rom from there, but it doesn't
- if adb connection works I could try that, but it doesn't
- if romaster detects the phone I could try install it from there, but it doesn't
- sp flash tool is working but I could find only one rom version and it's not working
You did the brushing before installing the flash've used Flashtool?
Have you looked in setting pc, peripherals, if you have something in conflict, if you do not have the yellow exclamation mark?
Also I have just bought this phone, by Liaow, who did the root and installed the Playstore. Now my phone is still stuck in Hong Kong and I do not know when it will arrive in Italy.
How did you like the phone, the battery life, becomes very hot since the minimum thickness?
I don't know what do you mean by 'brushing' so the answer is probably not?
Everything looks ok in pc's control panel, no conflicts or unrecognized devices etc. It's win7 64bit.
I was thinking about buying it via Liaow but in the end I used ebay. It took 3 weeks to arrive, and I paid for DHL express delivery (!) Isn't EU wonderful thing...
I really liked the phone (in the brief time it was working). Display is great, it's fast and the battery would last for a day without a problem. The build is very solid. I wasn't playing any games on it or use any apps that would use cpu extensively, but in normal operational time I didn't notice any significant heating. I even liked the Amigo skin. It has some nice features and was working very fast. The only problem was it kept freezing couple of times a day, usually after long times of inactivity which led me to believe it has some sort of problem with power saving functions in android (or amigo). Oh one other thing: it doesn't have notification led. I miss that.
If you don't get your phone, I know where you can get one very, very cheap. It's stuck in the boot loop, but still...
Brushing think it is to do a full wipe before doing the flash with Flashtool.
When you receive your phone, you've got an update OTA of 98 mb?
Thank you but the phone I have already paid and are waiting for his arrival.
I hope we put less than three weeks since I also took DHL.
In Italy we have a beautiful community where there are developers who work here in Xda, who are fond of Chinese mobile phones and in particular there is a person who develops rom alternatives.
So I guess I would be able to help me if I had the same problem, but I hope I do not have any problems.
You say you had blocks of hibernation in power saving mode enabled, then maybe in normal mode just fine.
I do not usually use the mode energy in any phone I've had.
I prefer to charge the battery when needed.
First I tried only update, after that I tried full wipe.
I did try to disable every power saving mode I could find, but the phone still kept freezing. Although, there are some options that are useful, like limiting cpu for more energy and lower temperature.
I didn't get OTA update, but the seller told me that they had to open the box to install english rom version with google play. Maybe they also installed this update.
got another elife threat here http://forum.xda-developers.com/showthread.php?t=2699708
Here's the quick update: after I manually edited adb_usb.ini file, adb sideload works now. But...none of the rom's I have can be installed with adb (I get 'installation failed' message after transfer).
So, what I need is:
- rom that can be installed via adb sideload
or
- rom that can be installed via flashtool with scatter file (after extensive search of the web, the only rom I could find on several places is the one made 11-03-2014 and this one is not working for me)
Any help would be greatly appreciated.
tchs said:
Here's the quick update: after I manually edited adb_usb.ini file, adb sideload works now. But...none of the rom's I have can be installed with adb (I get 'installation failed' message after transfer).
So, what I need is:
- rom that can be installed via adb sideload
or
- rom that can be installed via flashtool with scatter file (after extensive search of the web, the only rom I could find on several places is the one made 11-03-2014 and this one is not working for me)
Any help would be greatly appreciated.
Click to expand...
Click to collapse
http://bbs.amigo.cn/thread-758-1-1.html
XPAction said:
http://bbs.amigo.cn/thread-758-1-1.html
Click to expand...
Click to collapse
Thanks but I already tried that. This only works with Romaster app and it doesn't recognize my phone being connected while on boot loop or recovery mode.
Even my phone is stuck on boot, can anyone help me
Tired of searching everywhere cant find it anywhere, can anyone please share a link from where I can download rom for my gionee elife S5.5 Indian version, my phone was working fine until I installed beats audio It asked to reboot and the then it never rebooted, stuck on gionee boot animation, I also flashed the Chinese rom but it doesn't support, phone was booting up but the rom is too lagging and unstable. I don't want to go to the service center cause my phone is rooted and warranty will be voided, I just bought it two days back. Is CWM available for this phone cause I couldn't find that too, I'd be more than grateful If anyone can help me out I just need the rom file (Indian version), thanks a million !!!!
i also tried to install beat audios on my gionee s5.5 ... and now it is not statting my phone get stucks at boot animation logo "gionee smatyphone"
Here are some good news people: needrom.com site finally released new rom version and it can be installed via adb sideload. It is CH/EN version and even when you switch it to English, some things still stay in Chinese but hey - at least it's not in boot loop anymore and now you have more options for rom installation.
Thanks dev, was so sick of this phone and its features, especially free mobile heater(owen) + worst sound ever + lots of lags, even flappy bird lags on this phone though I had optimised the cpu performance using set cpu to its max by creating a profile to play flappy bird, mediatek chipset sucks happy after entering the snapdragon world, just bought M8 yesterday and believe me this is the best phone till date though the ram is 2gb the processor is a the beast and there's no comparison to it and when it comes to the sound no one can beat htc, the looks it feels so ****n premium, the touch is like butter smooth, loving it!! Thanks
Sent from my HTC One_M8 using XDA Free mobile app
how to install rom from needrom via adb shell.?? can anyone explain?
FirmwareFile
https://firmwarefile.com/gionee-s5-5 , i've used T8881 version , and it was good
Hi guys!
A friend of mine was telling me he ordered a new tablet because his old one got broken.I got interested and asked about his problem.
After hearing out the symptoms and the fact that the stock rom has not been modified,i offered to fix his problem.
No physical damage,just a self-brick during normal usage;it sounded fairly easy to repair...i had no idea what i had gotten into.
I later discovered that Sony did everything to make open-source development slower and close to impossible.
Despite that i have seen you guys literally do magic here.
So in the last 2 days i have been trying every posibility found here with very low success.
What is happening:
-The tablet turns on and get's stuck at the Sony logo
-I can access Recovery mode but it is stock Rom...nothing much to do.
-Fastboot mode...no chance
-I installed the Adb drivers while stuck in bootloop.When i go to Device Manager the status of the device says,error 10-Device cannot start.No detection in Adb
-In recovery mode Adb detects the device but i get error:closed on any command
I know there's a low chance but i took on the challenge and i'm not ready to give up.I am no expert,i just experimented on several cheap tablets so i can help myself when in need.All subjects ended up out of service
Maybe some of you guys could throw a tip or two so i could at least have something to keep trying with.
Thank you for the great work
Guessing it is xts, then try the xts unbricker tool you can find it the development forum
smgdev said:
Guessing it is xts, then try the xts unbricker tool you can find it the development forum
Click to expand...
Click to collapse
I have tried it and without great success.
I am not really sure if i'm allowed to call that bootloop.It never gets past the Sony logo
I recently purchased an RCA Voyager III model RCT6973W43 and I've noticed no one has said anything about how to root this one yet. I've heard of users who have had success with rooting the original Voyager and Voyager IIs, but there's nothing on the Voyager III. I think it's possible that the same procedure for rooting those devices might work for the Voyager III, but I don't want to take any chances in case it bricks mine. So is there a whole different procedure with my particular device? Or is the Voyager III simply too new?
Bump
RobinHood16 said:
I recently purchased an RCA Voyager III model RCT6973W43 and I've noticed no one has said anything about how to root this one yet. I've heard of users who have had success with rooting the original Voyager and Voyager IIs, but there's nothing on the Voyager III. I think it's possible that the same procedure for rooting those devices might work for the Voyager III, but I don't want to take any chances in case it bricks mine. So is there a whole different procedure with my particular device? Or is the Voyager III simply too new?
Click to expand...
Click to collapse
Bump!
Yes please!
I tried RCA to see if they would at least update the tablet and turn on the FM receiver. They claim it doesn't have it. I'm pretty sure it has both the FM and a GPS receiver built in. I think I also found a "clone", the DigiLand DL721-RB appears to be the same hardware.
What I'm trying to do is simply enable all the features the hardware has. The Atom x3 is supposed to have pretty much all the standard stuff, my RCA RCT6973w43 (on sale at Walmart right now for $37) does OTG nicely, but if I had the FM also it would be perfect for a tablet based car stereo. If anyone figures it out and can get the FM and or GPS going, I'd be tickled.
I just bought a couple of these for 25 bucks. I would very much like to get them rooted. Any news on if the method for the other Rca's works?
No good. I attempted to root the Voyager III with One Click Root, and it told me it was unrootable for the time being.
Any clues yet?? everyone owns this tablet figured there'd be a root already for this one.
i read where someone tried to root the 43 using 42, and it bricked the tablet, so i'm reluctant to try it. don't know if the 42 and the 43 had the same processor, or what makes them so different it would cause that to happen. maybe we can get a bump.
keep finding tons of people looking for root, but not dice so far. i've only got one cuz they were sold out. actually bought the display model. wish i had more than one so i could experiment. 8(
I'd been able to install twrm halfway then it fails signature verification.
Just got one of these! Bump
yes bump!!!! I can't believe this hasn't been rooted yet. is it because it's an intel x86 architecture?? I'm guessing it would require someone to compile the code for sudo/su/root to run on it??
anything yet?? 8(
---------- Post added at 02:04 AM ---------- Previous post was at 01:39 AM ----------
just as a quick notei found this guys.
http://specdevice.com/showspec.php?id=7920-d3ef-0033-c5870033c587
it's an alco tablet with the same model # as the voyager 3 RCT6973W43.
weird thing is it appears to have a quadcore arm processor, and not an intel atom.
i heard there was a root for the alco from twitter profile @srsrOOT, but they haven't responded yet.
no clue if this will help at all. I would imagine if the alco has an arm proc, and the rca has an intel then we'd need a different su/sudo binary for the RCA because the RCA runs on a CISC processor, and the ARM is a RISC. hope there's some clues here. hit us back with any info you find. 8(
look here
bump
Thought Id try bumping this. Sorry itll prolly be gone soon.
This tablet is begging for a root. I did a bunch of adb uninstalling and got rid of google play stuff. Battery is MUCH better. I suppose a custom rom would immensely improve battery.
TimmyP said:
Thought Id try bumping this. Sorry itll prolly be gone soon.
This tablet is begging for a root. I did a bunch of adb uninstalling and got rid of google play stuff. Battery is MUCH better. I suppose a custom rom would immensely improve battery.
Click to expand...
Click to collapse
Did you guys unlock the boot loader yet?
Code:
adb reboot fastboot
fastboot flashing unlock
If so, you can try and boot the cwm recovery I use on mine(RTC6873W42) to get a root shell. (if the kernel drivers were the same it would actually be full recovery enviroment) And with that root shell you could pull your boot.img . The expected result of the fastboot boot command is an attempted boot to cwm recovery except the screen will be blank, and adb will give root shell access.
Code:
fastboot boot v31-test-rca-recovery-cwm-ramdisk-20170709-2052.img
https://www.androidfilehost.com/?fid=961840155545581102
And with the pulled boot.img you can make the recovery fully boot by swapping the kernel, then manually change some rc files in the ramdisk folder of the boot.img the allow it to be rooted.
When you get that far, and if you need help, just ask.
This doesn't work with an RCT6973W43, I'm afraid. I get the blank screen from "adb reboot fastboot", as is apparently expected, but while the RCT6973W43 is in this mode, Windows doesn't recognize the device at all, as there are no drivers available. Also, it keeps disconnecting and reconnecting, so that "fastboot flashing unlock" can't get a fix on the device -- it's stuck on "< waiting for any device >" forever, and can only be stopped with Ctrl-C. Otherwise, the only way to restore the device to working order is a hard restart.
RobinHood16 said:
This doesn't work with an RCT6973W43, I'm afraid. I get the blank screen from "adb reboot fastboot", as is apparently expected, but while the RCT6973W43 is in this mode, Windows doesn't recognize the device at all, as there are no drivers available. Also, it keeps disconnecting and reconnecting, so that "fastboot flashing unlock" can't get a fix on the device -- it's stuck on "< waiting for any device >" forever, and can only be stopped with Ctrl-C. Otherwise, the only way to restore the device to working order is a hard restart.
Click to expand...
Click to collapse
That connect disconnect is expected when Intel drivers for fastboot not installed. I will link you to my write up on how to install
https://raw.githubusercontent.com/m...ster/unlock_tool/manual root instructions.txt
Read the document and follow directions in the driver install section. If trouble let me know
Neither of these builds works for me. My build number is RCT6973W43-ANDROID6.0-V16-V1.18.0-M01. Also, even if I could find the correct files, the Intel drivers don't work with my device.
RobinHood16 said:
Neither of these builds works for me. My build number is RCT6973W43-ANDROID6.0-V16-V1.18.0-M01. Also, even if I could find the correct files, the Intel drivers don't work with my device.
Click to expand...
Click to collapse
Sorry this is giving you such trouble,
but if you cant get the drivers to work, then you hae no way to know if these files will not work on your device.
If you are refering to the "tools" then, yes they will not work, as I coded them to not work if build numbers are not matched. But I never suggested tring the "tools". just the unlock and "fastboot boot" steps
again , If you cant get windows drivers to install then , thats as far as you can go.
I had a pictoral 'guide' for doing it, but cant find it right now.
In that case, my only recourse is to give up. It seems to me that they have made this tablet absolutely unrootable.
i managed to unlock bootloader
i used the method here https://raw.githubusercontent.com/m...ster/unlock_tool/manual root instructions.txt to unlock boot loader only difference is the fastboot screen flashes just input unlock command and keep taping up it works dont really know where to go from here
seasonednovice said:
i used the method here https://raw.githubusercontent.com/m...ster/unlock_tool/manual root instructions.txt to unlock boot loader only difference is the fastboot screen flashes just input unlock command and keep taping up it works dont really know where to go from here
Click to expand...
Click to collapse
Did you attempt my directions at the end . To boot the modified cwm , to get adb root shell?
I rooted my ZTE Grand X Z777 w/Qualcomm chipset... Android is Jelly Bean 4.3 and Cricket Wireless is the vendor, (but I'm an American and I live in Omaha, Nebraska, United States....) I rooted with Kingoroot without doing enough research like a dummy and I lost power before I got a custom recovery installed. I flashed with TWRP and it erased everything on the phone. I need a stock rom that is not MT6572. My imei is (was)... 864642021470202... I see the same MT6572.zip on every site and I've checked at least 100. The thing is... Zte made more than one Grand X Z777. This is the MTK chipset and everyone in America that I've talked to are all looking for the Qualcomm chipset. Jelly Bean 4.3 (not 4.2), and snapdragon 200 or 220. I don't understand why people think that you can flash a Qualcomm chip with an Mtk image, system, boot... Please tell me how if it can be done... It's all wrong and it doesn't work. Nothing works. The driver is Z777 and it's in my C:\Windows\System32\drivers\UMDF\WpdMtpDr.dll and I had to write some code to even get anything done at all. I'm just going to ask XDA because everyone has got it wrong for this phone. Mine was stuck at 0% right after the logo screen trying to load an upgrade from sd card. Wouldn't get reconized by windows unless I held down both volume buttons with power off and plugged it into pc. Adb, fastboot, Ubuntu, would not see it. Error: device not found 'null'... I finally managed to get recovery on it by magically unlocking the bootloader of a device stuck in bootloop and not recognized. Not sure how I did it but I did. I did an md5 check and 6 files were wrong. So I had no radio, imei, no ip address, no mac address.... No way to update but I got usb debugging turned back on and still could not find a stock rom that would work. Now it's back in a bootloop trying to load an update from sd card and the bootloader is locked again... HELP...????..... PLEASE??????????? my email is [email protected] or [email protected].com
chadmaller4444 said:
I rooted my ZTE Grand X Z777 w/Qualcomm chipset... Android is Jelly Bean 4.3 and Cricket Wireless is the vendor, (but I'm an American and I live in Omaha, Nebraska, United States....) I rooted with Kingoroot without doing enough research like a dummy and I lost power before I got a custom recovery installed. I flashed with TWRP and it erased everything on the phone. I need a stock rom that is not MT6572. My imei is (was)... 864642021470202... I see the same MT6572.zip on every site and I've checked at least 100. The thing is... Zte made more than one Grand X Z777. This is the MTK chipset and everyone in America that I've talked to are all looking for the Qualcomm chipset. Jelly Bean 4.3 (not 4.2), and snapdragon 200 or 220. I don't understand why people think that you can flash a Qualcomm chip with an Mtk image, system, boot... Please tell me how if it can be done... It's all wrong and it doesn't work. Nothing works. The driver is Z777 and it's in my C:\Windows\System32\drivers\UMDF\WpdMtpDr.dll and I had to write some code to even get anything done at all. I'm just going to ask XDA because everyone has got it wrong for this phone. Mine was stuck at 0% right after the logo screen trying to load an upgrade from sd card. Wouldn't get reconized by windows unless I held down both volume buttons with power off and plugged it into pc. Adb, fastboot, Ubuntu, would not see it. Error: device not found 'null'... I finally managed to get recovery on it by magically unlocking the bootloader of a device stuck in bootloop and not recognized. Not sure how I did it but I did. I did an md5 check and 6 files were wrong. So I had no radio, imei, no ip address, no mac address.... No way to update but I got usb debugging turned back on and still could not find a stock rom that would work. Now it's back in a bootloop trying to load an update from sd card and the bootloader is locked again... HELP...????..... PLEASE??????????? my email is [email protected] or [email protected]
Click to expand...
Click to collapse
I suggest that you go to this link https://www.zteusa.com/zte-grandx#support and contact the support team (Contact Support) instead.
And no, Mediatek software WILL OBVIOUSLY NOT WORK on qualcomm hardware!
Edit: I found this! https://www.stockrom.net/2017/08/st...nd-x-z777-cricket-android-4-3-jelly-bean.html
Not sure if it's for Qualcomm version or MTK, but you can try it (password for archive is given in the article).
Still searching
Well I still haven't found firmware but I have a bunch of bin files from the automated server QPST. I just found them but now what? And ZTE is no help. They won't even tell me why some Z777's are msm8210 and some msm8610... Found out there's also serious problems with both of those boards. They want me to send it in and pay more than what the phone even costs. It's stuck in recovery mode trying to load an update and there is no menu. Stays at 0%