Please note: the information in this thread is out of date. I recommend installing me176c-boot instead, found in https://forum.xda-developers.com/me...tloader-me176c-boot-asus-memo-pad-7-t3780225.
DISCLAIMER: I am NOT responsible for anything that goes wrong with your device. This tablet's very resilient and theoretically unbrickable, but it can still happen.
@social-design-concepts is working on a bootloader "unlock" for all Intel Bay Trail devices running Lollipop. It's working fine on our tablet, so he's given me permission to release the unlock for this device, as well as a TWRP image.
Download the images from here:
https://www.androidfilehost.com/?fid=312978532265362065
UPDATED! TWRP is now version 3.0.2!
MAKE A BACKUP OF ESP AND RECOVERY IN CASE ANYTHING GOES WRONG. YOU'VE BEEN WARNED.
These images aren't in a Nandroid or anything, you'll have to flash them manually via dd.
REQUIREMENTS
ASUS ME176C or ASUS ME176CX with root (duh )
and either-
Terminal Emulator must be installed on the tablet, and given root access
or
Access to a computer w/ ADB installed
INSTALLATION
Download the linked file from above, then unzip them to somewhere on your tablet. This directory will be noted as /path/to/unzipped/zip in this tutorial.
Open up a command prompt and plug in your tablet (if you're on PC) or just launch Terminal Emulator on your tablet.
This first command can be skipped if you're installing this without a computer, but if you're using ADB, then first run
Code:
adb shell
The next steps are universal for both Terminal Emulator and the PC command prompt or terminal.
While we could use tethered TWRP to back up these partitions, it cannot properly back up the ESP, so we'll be backing up the partitions manually. To do so, run the following to get root permission and back up the original recovery and ESP.
Code:
su
dd if=/dev/block/by-name/ESP of=/path/to/unzipped/zip/stock_ESP.img
dd if=/dev/block/by-name/recovery of=/path/to/unzipped/zip/stock_recovery.img
Then, to install:
Code:
dd if=/path/to/unzipped/zip/ESP.img of=/dev/block/by-name/ESP
dd if=/path/to/unzipped/zip/recovery.img of=/dev/block/by-name/recovery
Finally, reboot the tablet to make sure it worked. The ASUS screen should be replaced with an Intel one.
Volume Down + Power will give you an option of either fastboot or recovery, instead of just booting to fastboot like the stock bootloader.
do we still get otas? what happends if the ota contains a uefi update will it become locked again?
Ruben Craveiro said:
do we still get otas? what happends if the ota contains a uefi update will it become locked again?
Click to expand...
Click to collapse
Becouse the firmware update is for unknown reason always included in the esp.img, then the answer is yes no matter how unlogical it is.
P.S anybody still having 16GB whole emmc dd backup? Some guy from my country who doesn't speak English contacted me on PM, he tried to run some KK to LP update from 4pda.ru while already on lollipop. Now he is stuck in Aptio Setup Utlility (lying to him saying it's BIOS ) and so far this seems to be the only option to help him.
P.P.S I have finaly ordered a Y OTG cable from ebay so next month when I get it I can start debugging my debirf-xkiosk running on kali kernel to find out what's the problem.
*EDIT ilogical maybe?
---------- Post added at 09:05 PM ---------- Previous post was at 09:03 PM ----------
Why your tutorial can be in general and mine was moved to Q&A? It's unfair :'(
I got this 'Read only file system' message when I tried the first backup.. this shouldn't be happening, right? Presumably the backup failed?
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
adb server is out of date. killing...
* daemon started successfully *
[email protected]_1:/ $ su
su
[email protected]_1:/ # dd if=/dev/block/by-name/ESP of=/recoverystuff/stock_ESP.img
dd if=/dev/block/by-name/ESP of=/recoverystuff/stock_ESP.img
dd: /recoverystuff/stock_ESP.img: Read-only file system
1|[email protected]_1:/ #
Worked perfectly with your instructions. Used Terminal Emulator on the tablet.
Sent from my K013 using Tapatalk
seamo123 said:
I got this 'Read only file system' message when I tried the first backup.. this shouldn't be happening, right? Presumably the backup failed?
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
adb server is out of date. killing...
* daemon started successfully *
[email protected]_1:/ $ su
su
[email protected]_1:/ # dd if=/dev/block/by-name/ESP of=/recoverystuff/stock_ESP.img
dd if=/dev/block/by-name/ESP of=/recoverystuff/stock_ESP.img
dd: /recoverystuff/stock_ESP.img: Read-only file system
1|[email protected]_1:/ #
Click to expand...
Click to collapse
Try doing it through Terminal Emulator, see if that helps.
jerbear294 said:
Try doing it through Terminal Emulator, see if that helps.
Click to expand...
Click to collapse
Nah, same result using terminal emulator.. what's wrong I wonder?
seamo123 said:
Nah, same result using terminal emulator.. what's wrong I wonder?
Click to expand...
Click to collapse
Android in it's natire has no real rootfs so writing backup to /customdir/ rather than /sdcard/customdir is not gonnw work. If you "remounted" rootfs rw (not sure if you can remount ramdisk) it would still be all in ram.
---------- Post added at 09:26 PM ---------- Previous post was at 09:25 PM ----------
Mis012 said:
Android in it's natire has no real rootfs so writing backup to /customdir/ rather than /sdcard/customdir is not gonnw work. If you "remounted" rootfs rw (not sure if you can remount ramdisk) it would still be all in ram.
Click to expand...
Click to collapse
I wonder why people use ADB for shell when they don't have to
Mis012 said:
Android in it's natire has no real rootfs so writing backup to /customdir/ rather than /sdcard/customdir is not gonnw work. If you "remounted" rootfs rw (not sure if you can remount ramdisk) it would still be all in ram.
Click to expand...
Click to collapse
Oh ok, I'll just move the folder to the sdcard and give it a try..
seamo123 said:
Oh ok, I'll just move the folder to the sdcard and give it a try..
Click to expand...
Click to collapse
@Mis012 is right, either move it to a micro SD and make the path /Removable/MicroSD/recoverystuff or put it on the internal storage and make the path /storage/emulated/0/recoverystuff
jerbear294 said:
@Mis012 is right, either move it to a micro SD and make the path /Removable/MicroSD/recoverystuff or put it on the internal storage and make the path /storage/emulated/0/recoverystuff
Click to expand...
Click to collapse
Seemed to work fine, thanks! Boots up perfectly with the 'Intel' image. How does one get into recovery though? The volume up/down press/let go power button shenanigans for this pad always drove me totally up the wall. Anytime I ever got into stock recovery it was always by accident!
What's the key combo?
seamo123 said:
Seemed to work fine, thanks! Boots up perfectly with the 'Intel' image. How does one get into recovery though? The volume up/down press/let go power button shenanigans for this pad always drove me totally up the wall. Anytime I ever got into stock recovery it was always by accident!
What's the key combo?
Click to expand...
Click to collapse
Volume Down + Power, just like on the stock bootloader.
When you see the Intel screen release Power but keep holding Volume Down. You'll see a screen with a generic warning, then options to go to either fastboot or recovery.
Mis012 said:
Becouse the firmware update is for unknown reason always included in the esp.img, then the answer is yes no matter how unlogical it is.
P.S anybody still having 16GB whole emmc dd backup? Some guy from my country who doesn't speak English contacted me on PM, he tried to run some KK to LP update from 4pda.ru while already on lollipop. Now he is stuck in Aptio Setup Utlility (lying to him saying it's BIOS ) and so far this seems to be the only option to help him.
P.P.S I have finaly ordered a Y OTG cable from ebay so next month when I get it I can start debugging my debirf-xkiosk running on kali kernel to find out what's the problem.
*EDIT ilogical maybe?
---------- Post added at 09:05 PM ---------- Previous post was at 09:03 PM ----------
Why your tutorial can be in general and mine was moved to Q&A? It's unfair :'(
Click to expand...
Click to collapse
why just not simply go to dnx mode? then from there make fastboot flash osloader efilinux.efi and then fastboot boot droidboot.img from there it should boot to droidboot and allow to load temp recovery and flash .36(ive already been stuck in uefi for at least 2 times and this method helped me... yesterday i was stuck and its working again)
jerbear294 said:
Volume Down + Power, just like on the stock bootloader.
When you see the Intel screen release Power but keep holding Volume Down. You'll see a screen with a generic warning, then options to go to either fastboot or recovery.
Click to expand...
Click to collapse
That's great, thanks! So does this mean that we're all ready to install a custom ROM when one comes along? Running CM or AOSP on this device would be brilliant, I can finally forget all about that piercing white ASUS ui for a start
seamo123 said:
That's great, thanks! So does this mean that we're all ready to install a custom ROM when one comes along? Running CM or AOSP on this device would be brilliant, I can finally forget all about that piercing white ASUS ui for a start
Click to expand...
Click to collapse
Precisely. A custom ROM is possible with this bootloader.
Ruben Craveiro said:
why just not simply go to dnx mode? then from there make fastboot flash osloader efilinux.efi and then fastboot boot droidboot.img from there it should boot to droidboot and allow to load temp recovery and flash .36(ive already been stuck in uefi for at least 2 times and this method helped me... yesterday i was stuck and its working again)
Click to expand...
Click to collapse
He tried, it complained about some partitions not existing.
Mis012 said:
He tried, it complained about some partitions not existing.
Click to expand...
Click to collapse
he needs to repartition the tablet :
Code:
fastboot oem start_partitioning
fastboot oem partition /system/etc/partition.tbl
fastboot oem format factory
fastboot oem format cache
fastboot oem format system
fastboot oem format config
fastboot oem format logs
fastboot oem format misc
fastboot oem format data
fastboot oem stop_partitioning
Does it work with Build .36?
Hello,
i updated my me176c to the build number WW_V12.10.1.36_20151230 can i use your unlocked bootloader ?
intNERD said:
Hello,
i updated my me176c to the build number WW_V12.10.1.36_20151230 can i use your unlocked bootloader ?
Click to expand...
Click to collapse
you can use the unlocked bootloader on any lollipop version
Ruben Craveiro said:
you can use the unlocked bootloader on any lollipop version
Click to expand...
Click to collapse
Thank You! Great work! Cant wait for a custom rom!
Related
Hello,
I updated my UK Xoom 3G (MZ601) via OTA to 3.2 (H.6.5-17-3) last year.
Since I got interested in rooting the device I read I have to install CWM first.
However, when going into recovery mode (for testing) all I get is a green android bot.
Thanks to some googling I found some website that mentions to hold the power button (while the green android bot is shown) and press volume up, then release the power key. Now I see the stock 3e recovery menu.
Is it safe to simply unlock the bootloader and flash CWM via ADB? Or am I required to flash back to the xoom dev stock rom because of the green fella? My question refers to this part:
Or, if you do not already have root on your xoom when you get the green bot of ! then you have to do the following with the stock moto files for your device (from moto dev).
(This Wipes your Xoom )
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
Not sure why I would have to do that? In the end, I'd want to have a rooted stock 3.2.
First unlock it indeed while seeing the green bot in recovery.
(using the commands you posted yourself)
Then, you back into recovery, and push the new cwm recovery using adb
(look on the xda xoom's section: you'll find the right tutorial; should start with downloading adb, downloading cwm into the same directory as where you put the adb drivers for the xoom. Then open command as administrator, etc.)
After that, you should have CWM (or I recommend the touch Rogue recovery! ) on your Xoom, instead of the ugly little green bot, now allowing you to flash many, many ROMs, zips and many other to your device!
Enjoy. Hope this is clear enough and helps you towards the right direction! (if so, please do thank me, since I only just made an XDA account and would like at least one thanked post lol.
If not, please PM me or ask further explanations in this thread! )
adelancker said:
First unlock it indeed while seeing the green bot in recovery.
(using the commands you posted yourself)
Click to expand...
Click to collapse
I suppose you only refer to the adb commands without flashing the img files, right?
I still don't know why that other thread suggested to flash back to an older version first (see quote in my first posting)? Can anyone tell me if I have to downgrade at all?
Landorin said:
I suppose you only refer to the adb commands without flashing the img files, right?
I still don't know why that other thread suggested to flash back to an older version first (see quote in my first posting)? Can anyone tell me if I have to downgrade at all?
Click to expand...
Click to collapse
First unlock it using those fastboot commands you posted. You should in this series of commands not flash anything yet. Just unlock it first. When rebooting and showing the Moto logo:
Get back into recovery and then push the new recovery.img using adb commands
As far as I know, there is not one reason to downgrade. Should work just fine.
---------- Post added at 01:23 PM ---------- Previous post was at 01:05 PM ----------
adelancker said:
First unlock it using those fastboot commands you posted. You should in this series of commands not flash anything yet. Just unlock it first. When rebooting and showing the Moto logo:
Get back into recovery and then push the new recovery.img using adb commands
As far as I know, there is not one reason to downgrade. Should work just fine.
Click to expand...
Click to collapse
Otherwise, use this as your guideline and you should be fine:
http://forum.xda-developers.com/showthread.php?t=1249798
Thank you! All worked out fine. I followed the guide step by step, I did not downgrade the existing ROM.
In case someone else gets into the same situation and wonders how to do it:
once everything is set up for ADB and the device is found (command adb devices) type this in your command prompt window:
Code:
adb reboot bootloader
waited for fastboot protocol text to show up on Xoom device, then:
Code:
fastboot oem unlock
Confirmed the warning. Then had the device booting up normally to re-enable USB debugging. Then continued:
Code:
adb reboot bootloader
again waited for fastboot protocol text to show up on Xoom device, then:
Code:
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
When it said flashing done I restarted the Xoom (holding power button + volume up). About 3-4 sec after seeing the Motorola pic I hit volume down ("android recovery" is displayed), then volume up and CWM showed up.
Since I was already in CWM I also applied the universal root method ("install zip from sdcard" -> "choose zip from sdcard", then selected the actual file on the sd card, installed it, rebooted). Root works.
P.S.: just realized silly me forgot to do a nanddump before rooting.
something like forgetting a nanddump only happens once!
Glad to see it worked for you!
Even happier to see you didn't need to downgrade.
Once you flash a custom ROM, you'll have 3G and ICS!
I did the same a couple of months ago, and my device felt brand new!
Can anyone extend some help to a TF300T n00b?
I flashed the unofficial CM10 Jellybean ROM to my tf300t, and since the storage isn't working I can't move another ROM or even the stock firmware file to my SD card to flash. So, basically I'm stuck on the unofficial CM10 for now...
posted here because I can't post in the actual developement thread
just connect the tablet to a pc and copy the rom to the tablet. I dont rember if windows sees the internal storage. If it dosent linux should or you can install adb and push the file to /sdcard from your computer.
go here and dl the prog:
http://www.google.de/url?sa=t&rct=j...sg=AFQjCNG5sMnAkUGOfTZHgHJLFBARtdiyPg&cad=rja
extract it
boot into tecovery.
open the prog
choose the rom you like and push it to your tablet.
It is not possible to do it when you are in system, cause you cant write anything to the internal space.
mikaole said:
go here and dl the prog:
http://www.google.de/url?sa=t&rct=j...sg=AFQjCNG5sMnAkUGOfTZHgHJLFBARtdiyPg&cad=rja
extract it
boot into tecovery.
open the prog
choose the rom you like and push it to your tablet.
It is not possible to do it when you are in system, cause you cant write anything to the internal space.
Click to expand...
Click to collapse
I couldn't get the fast ADB pusher to work, nor the actual ADB. Fast pusher said it succeeded a few times but I couldn't find the new ROM on my SD card in CWM.
http://forum.xda-developers.com/showthread.php?t=1680570
Check here it has instructions on how to setup and use adb
MegaNoob said:
http://forum.xda-developers.com/showthread.php?t=1680570
Check here it has instructions on how to setup and use adb
Click to expand...
Click to collapse
looks promising. I hadn't been attempting to push the files while the tablet was in recovery because adb wouldnt recognize the tab when it was in recovery. I don't have my tablet cable, but I will try tomorrow morning. Thanks again.
ljungberg3 said:
looks promising. I hadn't been attempting to push the files while the tablet was in recovery because adb wouldn't recognize the tab when it was in recovery. I don't have my tablet cable, but I will try tomorrow morning. Thanks again.
Click to expand...
Click to collapse
if adb doesn't recognize the pad when it's in recovery, the drivers may not be installed correctly
paedz718 said:
if adb doesn't recognize the pad when it's in recovery, the drivers may not be installed correctly
Click to expand...
Click to collapse
I installed the drivers exactly as the guide directed, then tried using regular ADB, which didnt work. So I tried to use the ADB fast push and it didn't work either, under the "information" tab on the fast adb program it says
"Failed to mount as R/W"
is this a problem?
I got files to push via ADB, installation was aborted on the stock rom
I will try to find another stock rom to flash and update you guys. thanks for all the help so far
Can you still get to fastboot mode?
---------- Post added at 10:53 PM ---------- Previous post was at 10:44 PM ----------
If yes, dl the latest. Asus. STOCK, extract the blob, put it in the Fastboot Folder and. Open cmd
cd to the fastboot directory and write
fastboot -i 0x0B05 flash system blob
This will flash stock.
Don't give up, when it's not working. Just rewrite and try again and again.
A, user in the German Forum needed 20 times till it finally run through.
mikaole said:
Can you still get to fastboot mode?
---------- Post added at 10:53 PM ---------- Previous post was at 10:44 PM ----------
If yes, dl the latest. Asus. STOCK, extract the blob, put it in the Fastboot Folder and. Open cmd
cd to the fastboot directory and write
fastboot -i 0x0B05 flash system blob
This will flash stock.
Don't give up, when it's not working. Just rewrite and try again and again.
A, user in the German Forum needed 20 times till it finally run through.
Click to expand...
Click to collapse
I was able to push and flash a stock firmware! thank god! haha, and thank you guys for all the help!
ljungberg3 said:
I was able to push and flash a stock firmware! thank god! haha, and thank you guys for all the help!
Click to expand...
Click to collapse
Np
So, much of the stuff in this and other threads has been a tremendous help. I did pretty much exactly what OP did in this thread http://forum.xda-developers.com/showthread.php?t=1779080.
That thread lead me to this one, as I was having trouble getting my computer to recognize the usb drivers. I was able to finally get ADB to see the tablet, however, when I go to push the stock rom, I get an error message of "Protocol Failure" in cmd.
Any ideas?
http://s12.postimage.org/unt8ag1vh/adbcmd.jpg
Created new thread as OP solved his problem.
Hello there users. I'm currently a dev for Nokia X but I would love to help you guys out.
So, I'll be giving out ways on how you can try to get Root on your device. This is a discussion thread.
As I don't have the device myself, I'm counting on people who have purchased it.
So lets start. In order to get development for your device, you need to get a system dump of your whole/entire device.
But for that, you need Root. Heres an app that I think might root the device. http://www.cydiaimpactor.com/
Goto the link, download it and test it out. Give feedback.
And nothing happens. Maybe I`ve done somthing wrong...
So, in a dev options i`ve point usb debuging.
On my pc i got two new devices - Nokia composite adb interface and nokia 2 with yellow mark.
Then run cidia from admin name - usb - driver scan - no device found.
I tried with rooted nokia xl - just to see what happens - error - no such device.
stutofa aregercisr are
Thanks for your help, I tried it out and got this error all the time
Altivex said:
And nothing happens. Maybe I`ve done somthing wrong...
So, in a dev options i`ve point usb debuging.
On my pc i got two new devices - Nokia composite adb interface and nokia 2 with yellow mark.
Then run cidia from admin name - usb - driver scan - no device found.
I tried with rooted nokia xl - just to see what happens - error - no such device.
Click to expand...
Click to collapse
tdiddy.2 said:
Thanks for your help, I tried it out and got this error all the time
Click to expand...
Click to collapse
Okay, so that didnt work.
Now, goto this link and download the adb and fastboot drivers for Nokia X and install them.
After that, go HERE and flash CWM Recovery for Nokia X using the instructions given in the thread.
DONT DO THE ABOVE METHOD! As there is no backup, if something goes wrong, you'll lose the device. For now, wait and let me find more exploits. Till then, do install the adb and fastboot divers.
After that, goto ADB folder and Open command prompt from there (Shift + Right mouse button). Then type this:
Code:
adb reboot bootloader
fastboot -i 0x0421 devices
And see if the device gets recognized.
Then type:
Code:
fastboot -i 0x0421 reboot
You can try this method too: http://forum.xda-developers.com/showthread.php?t=803682
Okay will try. For the recovery, I tried both Nokia X's CWM and TWRP already, none of them worked However it's not going to brick my device haha
On fastboot - nothing. I coudn`t install adb from this tread
http://forum.xda-developers.com/showthread.php?t=2744191
Installer told me-unsupported language and close)
I used cmd.exe ,and path to android tools - on fastboot i got nothing. No list of devices. But.
On reboot or others command - answer is - Waiting for device
Super one click - runs adb server around 3 times, then program freez on - Waiting for device =)
If i click on button driver chek - no issues found.
Maybe i`ve got some trouble with drivers ?
I got them from here
http://developer.nokia.com/resources/library/nokia-x/getting-started/device-setup.html
But i haven`t adb_usb.ini where it should be...
Altivex said:
On fastboot - nothing. I coudn`t install adb from this tread
http://forum.xda-developers.com/showthread.php?t=2744191
Installer told me-unsupported language and close)
I used cmd.exe ,and path to android tools - on fastboot i got nothing. No list of devices. But.
On reboot or others command - answer is - Waiting for device
Super one click - runs adb server around 3 times, then program freez on - Waiting for device =)
If i click on button driver chek - no issues found.
Maybe i`ve got some trouble with drivers ?
I got them from here
http://developer.nokia.com/resources/library/nokia-x/getting-started/device-setup.html
But i haven`t adb_usb.ini where it should be...
Click to expand...
Click to collapse
adb_usb.ini is important as it is the key that recognizes the adb device to the computer.
Do all the above steps in the guide fully including the adb_usb.ini step.
mmmm, Nokia XL got connected without this file...
I tried all instructions on 3 different pc - this file is missed....
So,i just created this file.
on ADB devices i got answer - 188bde4a device
on command fastboot -i 0x0421 devices-
188bde4a fastboot
then i reboot device.
i`ve try out some comands - i lost recovery....
fastboot -i 0x0421 oem unlock
unlocked
fastboot -i 0x0421 flash recovery recovery img.
7seconds flash - and i coud not boot recovery....
i tyed this one
http://forum.xda-developers.com/showthread.php?t=2704379
but - phone boots up in normal mode...
ok,good news - got stock firmware from navifirm!
Just need stock recovery)
Okay, i tried superoneclick, not work :crying:
---------- Post added at 11:02 AM ---------- Previous post was at 10:58 AM ----------
And for the Fastboot...
Code:
Tungs-MacBook-Air:~ md232llaoption$ fastboot -i 0x0421 devices
f901c863 fastboot
Tungs-MacBook-Air:~ md232llaoption$
I think i goot rooted my device....
with root_backup
or towelroot.
So, if I`ll install gaps- that would be great. But i really need custom recovery)
http://forum.xda-developers.com/showthread.php?t=2783157
or in attach.
Copy all data to phone, then go to folder "1" install tr.apk
Make shure you`ve got internet connection.
in folder "2" is SUpersu apk.
In folder"3" - root explorer.
Also you`ll find apk for backup phone.
Altivex said:
mmmm, Nokia XL got connected without this file...
I tried all instructions on 3 different pc - this file is missed....
So,i just created this file.
on ADB devices i got answer - 188bde4a device
on command fastboot -i 0x0421 devices-
188bde4a fastboot
then i reboot device.
i`ve try out some comands - i lost recovery....
fastboot -i 0x0421 oem unlock
unlocked
fastboot -i 0x0421 flash recovery recovery img.
7seconds flash - and i coud not boot recovery....
i tyed this one
http://forum.xda-developers.com/showthread.php?t=2704379
but - phone boots up in normal mode...
ok,good news - got stock firmware from navifirm!
Just need stock recovery)
Click to expand...
Click to collapse
Thats it. You got the fastboot recognized. Now try Bin4ry Root Method and see if it'll work.
tdiddy.2 said:
Okay, i tried superoneclick, not work :crying:
---------- Post added at 11:02 AM ---------- Previous post was at 10:58 AM ----------
And for the Fastboot...
Code:
Tungs-MacBook-Air:~ md232llaoption$ fastboot -i 0x0421 devices
f901c863 fastboot
Tungs-MacBook-Air:~ md232llaoption$
Click to expand...
Click to collapse
You also got fastboot recognized. f901c863 is your fastboot device number.
Try Bin4ry root method.
Altivex said:
I think i goot rooted my device....
with root_backup
or towelroot.
So, if I`ll install gaps- that would be great. But i really need custom recovery)
Click to expand...
Click to collapse
Wait. Did you get Root? HOWWW?! Share if you did. Cause this is what the thread is about.
Dom3616 said:
Wait. Did you get Root? HOWWW?! Share if you did. Cause this is what the thread is about.
Click to expand...
Click to collapse
Towelroot in attach. Idk will it work on clear device,or you need to unlock bootloader. Cos on oem unlock- unlocked something=)
Altivex said:
Towelroot in attach. Idk will it work on clear device,or you need to unlock bootloader. Cos on oem unlock- unlocked something=)
Click to expand...
Click to collapse
Very good. I'll be updating this thread soon.
Now, next step is to goto this thread and make a full dump of your device: http://forum.xda-developers.com/showthread.php?t=2450045
Dom3616 said:
Very good. I'll be updating this thread soon.
Now, next step is to goto this thread and make a full dump of your device: http://forum.xda-developers.com/showthread.php?t=2450045
Click to expand...
Click to collapse
Yes yes!!
Hmmm, and online nandroid backup can do this procedure? Or dump and backup- defferent things?
Altivex said:
Hmmm, and online nandroid backup can do this procedure? Or dump and backup- defferent things?
Click to expand...
Click to collapse
Yes, you can use this also: http://forum.xda-developers.com/showthread.php?t=1620255
After creating the backup, upload it to Google Drive or any other server.
Altivex said:
Hmmm, and online nandroid backup can do this procedure? Or dump and backup- defferent things?
Click to expand...
Click to collapse
I tried to pull and got the recovery img for ya hope this work
Native recovery or custom?)
native I`ve restored yesterday from navifirm. And custom will make our life a bit easyer)
I`ve made a twrp backup, with nandroid . Backup have files with .win extension....
Hi everyone,
I was trying to update via OTA to the latest version, but after downloading the update the tablet started updating itself and returned the Android dead droid error. It is important to highlight that I was rooted with KingRoot and removed it to apply OTA update. Any help would be appreciated
regular_ said:
Hi everyone,
I was trying to update via OTA to the latest version, but after downloading the update the tablet started updating itself and returned the Android dead droid error. It is important to highlight that I was rooted with KingRoot and removed it to apply OTA update. Any help would be appreciated
Click to expand...
Click to collapse
Am in the same situation. Waiting to hear back from Cameron Yan.
Looks like you might need to flash the 1.5 version via fastboot and go through each update iteration.
Yeah u might have to flash 1.5
Your Jide Ambassador is here!!!
---------- Post added at 12:45 PM ---------- Previous post was at 12:35 PM ----------
U can't just remove the rooting and think the update will be applied. Each updated is like a layered cake placed on its foundation. When you rooted you messed with pliers of stability for future layered updates and the updates check where they are suppose to be place. If something is missing or out of place you are going to get an error.
Your Jide Ambassador is here!!!
regular_ said:
Hi everyone,
I was trying to update via OTA to the latest version, but after downloading the update the tablet started updating itself and returned the Android dead droid error. It is important to highlight that I was rooted with KingRoot and removed it to apply OTA update. Any help would be appreciated
Click to expand...
Click to collapse
I had the same experience and ended up flashing 1.5 and then going through the automatic updates. Took a little while, but the update installed and I am back to stock for the time being.
regular_ said:
Hi everyone,
I was trying to update via OTA to the latest version, but after downloading the update the tablet started updating itself and returned the Android dead droid error. It is important to highlight that I was rooted with KingRoot and removed it to apply OTA update. Any help would be appreciated
Click to expand...
Click to collapse
Same issue for me I am scared about the root by King root : not the cleaner tool ...
iceheart3131 said:
Same issue for me I am scared about the root by King root : not the cleaner tool ...
Click to expand...
Click to collapse
If you have rooted, the only way to get OTA that I have found is to reflash version 1.5 and then have the normal updates be applied.
I have done this and then rerooted after I have applied the current update.
tomlogan1 said:
If you have rooted, the only way to get OTA that I have found is to reflash version 1.5 and then have the normal updates be applied.
I have done this and then rerooted after I have applied the current update.
Click to expand...
Click to collapse
Ok , but where can I found this 1.5 version please ? there is no Download section on Jide webpage ...
Ok 1.5 version and toutos available on JIDE webpage
I have an issue with fastboot : adb devices found the tablet but fastboot devices found nothing ... My fastboot is functionnal with my edge 7, nexus 5x and android TV ... So it must be something specific to do on Utra Tablet ... But I don't know what
iceheart3131 said:
I have an issue with fastboot : adb devices found the tablet but fastboot devices found nothing ... My fastboot is functionnal with my edge 7, nexus 5x and android TV ... So it must be something specific to do on Utra Tablet ... But I don't know what
Click to expand...
Click to collapse
Probably obvious, but to you have USB debugging enabled?
tomlogan1 said:
Probably obvious, but to you have USB debugging enabled?
Click to expand...
Click to collapse
Yes i have... I have try to connecter other Devices to be sure but the issue is only with Ultra Tablet
iceheart3131 said:
Yes i have... I have try to connecter other Devices to be sure but the issue is only with Ultra Tablet
Click to expand...
Click to collapse
Try connecting via USB and then run a command like adb devices and then unplug the tablet and plug it back in. I remember a security (RSA?) prompt that you have to accept in order for this to work. Worth a try.
tomlogan1 said:
Probably obvious, but to you have USB debugging enabled?
Click to expand...
Click to collapse
Sorry for the long delay (Holydays !!)... Yes USB debug is enabled .
---------- Post added at 05:15 PM ---------- Previous post was at 05:02 PM ----------
tomlogan1 said:
Try connecting via USB and then run a command like adb devices and then unplug the tablet and plug it back in. I remember a security (RSA?) prompt that you have to accept in
Still not available with fastboot
Click to expand...
Click to collapse
iceheart3131 said:
Sorry for the long delay (Holydays !!)... Yes USB debug is enabled .
---------- Post added at 05:15 PM ---------- Previous post was at 05:02 PM ----------
tomlogan1 said:
Try connecting via USB and then run a command like adb devices and then unplug the tablet and plug it back in. I remember a security (RSA?) prompt that you have to accept in
Still not available with fastboot
Click to expand...
Click to collapse
When I use adb I get the device SN. When I use fastboot devices I get nothing. If I then adb reboot bootloader I get the attached response.
Click to expand...
Click to collapse
I follow this tuto (How to flash Remix OS 1.5 from Jide) :
To flash the ROM, please download the file from the following link and follow the below instructions.
https://drive.google.com/open?id=0B...1FVVR3RkRya29sakQ3SEdVbXU5cUg0YTIzUnNfUTRWMTA
Installing image files using fastboot
1. Make sure your Remix has working fastboot (http://wiki.cyanogenmod.org/w/Fastboot) and adb (http://wiki.cyanogenmod.org/w/Adb).
2. Download images
The information of the image zip file:
Images Zip File Name: SK1WG.zip
md5: f993e49ff5f0bfac169dcb62b2e820e8
sha1: 6f9b364f46680ff1294ff2eb9e3fe9aba6592d5a
3. Unzip the downloaded zip file ( SK1WG.zip ) and go to the folder
4. Connect the Remix to the computer via USB.
5. Make sure the fastboot binary is in your PATH (http://wiki.cyanogenmod.org/w/Doc:_paths) or that you place the recovery image in the same directory as fastboot.
6. Open a terminal on your PC and reboot the device into fastboot mode by typing adb reboot bootloader or by using the hardware key combination for your device while it is powered off.
7. Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
-If you don't see your device serial number, and instead see "", fastboot is not configured properly on your machine. See fastboot (http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro) documentation for more info.
-If you see "no permissions fastboot", make sure your UDEV (http://wiki.cyanogenmod.org/w/UDEV) rules are setup correctly.
8. Clean the existing data by entering the following command: fastboot -w
9. Flash images onto your device by entering the following three commands:
-fastboot flash system system.img
-fastboot flash recovery recovery.img
-fastboot flash boot boot.img
10. Once the flash completes successfully, run the following command to reboot the device into recovery to verify the installation.
-fastboot reboot
Click to expand...
Click to collapse
I can reboot with adb command
Code:
adb reboot bootloader
my tablet reboot and this menu is available :
but fasboot command seems still without effect , i have try to launch fastboot protocol in the menu : no effect . fastboot devices doens't return any ID . I have try to install complete suite android studio to have ALL tools ( and fastboot ) but it seems the same isssue .
iceheart3131 said:
I follow this tuto (How to flash Remix OS 1.5 from Jide) :
I can reboot with adb command
Code:
adb reboot bootloader
my tablet reboot and this menu is available :
but fasboot command seems still without effect , i have try to launch fastboot protocol in the menu : no effect . fastboot devices doens't return any ID . I have try to install complete suite android studio to have ALL tools ( and fastboot ) but it seems the same isssue .
Click to expand...
Click to collapse
Maybe a driver from previous devices? I'm using the Android naked drivers and they work with the tablet as well as my Android phone.
Victory !!!! until now i have tried with Windows 10 and it doesn't works . With a friend we have follow the sme process on Ubuntu and it works perfectly ! Thanks tomlogan1 for your patience and your support , I appreciate
iceheart3131 said:
Victory !!!! until now i have tried with Windows 10 and it doesn't works . With a friend we have follow the sme process on Ubuntu and it works perfectly ! Thanks tomlogan1 for your patience and your support , I appreciate
Click to expand...
Click to collapse
Congratulations! Now you can be ready when custom ROMs become available. Your presistance paid off.
Thanks to xda member @Shooting Star Max for the original post for this solution
If your phone is always rebooting into recovery, and the only way to boot normally is by using the bootloader, follow these instructions:
Some users recommend removing your SD before doing the following as incorrectly formatted SD Cards could cause the phone to boot into recovery instead of booting normally.
1) Boot into TWRP recovery.
2) Plug your Cedric into your computer (which needs to have drivers and fastboot installed).
3) Open a command prompt window and type:
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/misc misc.img
This will make a backup of the misc partition just in case.
4) Type the following:
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
This will clear the misc partition. You might get a message regarding lack of space, but it's okay.
5) Your Cedric will boot normally again
TheFixItMan said:
Thanks to xda member @Shooting Star Max for the original post for this solution
If your phone is always rebooting into recovery, and the only way to boot normally is by using the bootloader, follow these instructions:
1) Boot into TWRP recovery.
2) Plug your Cedric into your computer (which needs to have drivers and fastboot installed).
3) Open a command prompt window and type:
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/misc misc.img
This will make a backup of the misc partition just in case.
4) Type the following:
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
This will clear the misc partition. You might get a message regarding lack of space, but it's okay.
5) Your Cedric will boot normally again.
Click to expand...
Click to collapse
I did the procedure and everything went back normal.
I did a backup with the twrp and when I went to restore and go back everything as before, it will continue to restart in the bootloader and I must confirm with the power key to boot the system.
I tried to repeat the procedure but nothing to do does not work anymore.
Some help thank you
masterdex said:
I did the procedure and everything went back normal.
I did a backup with the twrp and when I went to restore and go back everything as before, it will continue to restart in the bootloader and I must confirm with the power key to boot the system.
I tried to repeat the procedure but nothing to do does not work anymore.
Some help thank you
Click to expand...
Click to collapse
As long as you have fully booted your phone before trying again I don't see why you couldn't repeat it
Or reflash the recovery and try again
[/ATTACH]
TheFixItMan said:
As long as you have fully booted your phone before trying again I don't see why you couldn't repeat it
Or reflash the recovery and try again
Click to expand...
Click to collapse
Still tried on minimal adb and phower shell does not work. I attach pictures.
masterdex said:
[/ATTACH]
Still tried on minimal adb and phower shell does not work. I attach pictures.
Click to expand...
Click to collapse
Make sure adb is connected properly
Code:
adb kill-server
adb devices
Your device should be displayed as connected & should be the only device listed
If it still doesn't work then the only solution I can think of is restoring your stock firmware by fastboot - do not flash the bootloader part of the firmware
TheFixItMan said:
Make sure adb is connected properly
Code:
adb kill-server
adb devices
Your device should be displayed as connected & should be the only device listed
If it still doesn't work then the only solution I can think of is restoring your stock firmware by fastboot - do not flash the bootloader part of the firmware
Click to expand...
Click to collapse
Yes is connected. If only I could find the firmware for my XT1675 16gb / 2gb single sim model.
masterdex said:
Yes is connected. If only I could find the firmware for my XT1675 16gb / 2gb single sim model.
Click to expand...
Click to collapse
Same phone as mine & Iv never had this problem - I use lineageos - try flashing that
Other than that I can't suggest anything else
Thank you anyway. They persistently waited for Lenovo to provide the tools and release the firmware for my model that is currently unavailable.
I've tried all the constructions here, but they all have background noise during calls and fixed gps in over a minute and it's not accurate.
Do you have my own model with the same features?
masterdex said:
Thank you anyway. They persistently waited for Lenovo to provide the tools and release the firmware for my model that is currently unavailable.
I've tried all the constructions here, but they all have background noise during calls and fixed gps in over a minute and it's not accurate.
Do you have my own model with the same features?
Click to expand...
Click to collapse
I have the XT165 running lineageos
No problems with calls - iv changed the build.prop to edit call volume (see my last post in the lineageos thread)
No problem with gps
You could try running these commands in fastboot as this was a fix for gps in past moto devices
Code:
fastboot erase modemst1
fastboot erase modemst2
Okay, now I'm just trying to build stock, if I think I bought the phone, just the time to get home and unlock bootloader and put custom rom, I almost do not know the functions of building stock. Now I see how it behaves and I guess if I install Lineage again and make all the corrections you've suggested very kindly thanks.
TheFixItMan said:
4) Type the following:
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
This will clear the misc partition. You might get a message regarding lack of space, but it's okay.
Click to expand...
Click to collapse
Clearing the whole misc partition may be overkill and cause other issues. In the LG threads they currently suggest clearing only the first 256 bytes.
ST Dog said:
Clearing the whole misc partition may be overkill and cause other issues. In the LG threads they currently suggest clearing only the first 256 bytes.
Click to expand...
Click to collapse
This works fine for our users - its been tested & no one has reported any issues
TheFixItMan said:
This works fine for our users - its been tested & no one has reported any issues
Click to expand...
Click to collapse
That's cool. Just a thought.
Different OEs put different stuff there, but really no reason to clear it all if only part is the problem.
And one never knows when they might change the usage.
Oh, and masterdex above appears to have had some issue.
ST Dog said:
That's cool. Just a thought.
Different OEs put different stuff there, but really no reason to clear it all if only part is the problem.
And one never knows when they might change the usage.
Oh, and masterdex above appears to have had some issue.
Click to expand...
Click to collapse
It worked for him but then he restored old phone backups - I recommended flashing lineageos from scratch
Nothing to do, I tried again to download Lineage, make a clean installation by deleting all the entries in the TWRP, configuring the phone restarted in recovery, and rewriting the procedure, the result does not change always restarts the bootloader.
At this point you only have to install the firmware from scratch, someone knows where to find firmware stock model XT1675 16gb storage and 2 gb sin ram single sim?
masterdex said:
Nothing to do, I tried again to download Lineage, make a clean installation by deleting all the entries in the TWRP, configuring the phone restarted in recovery, and rewriting the procedure, the result does not change always restarts the bootloader.
At this point you only have to install the firmware from scratch, someone knows where to find firmware stock model XT1675 16gb storage and 2 gb sin ram single sim?
Click to expand...
Click to collapse
This is rom stock Cedric work on XT1675 16 gb 2 gb ram installed on Motog5 brand Tim :https://www.youtube.com/watch?v=EMyaDv1lcYg
TheFixItMan said:
I have the XT165 running lineageos
No problems with calls - iv changed the build.prop to edit call volume (see my last post in the lineageos thread)
No problem with gps
You could try running these commands in fastboot as this was a fix for gps in past moto devices
Code:
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
I tried to give these commands fastboot but the result and that when I restart the phone no longer sees the sim and I have to reinstall the original firmware with fastboot. Tried twice the same result, are you sure you have the right commands?
My Cedric is listed on the adb devices code when it's turned on. But if I restart to twrp then it's not listed. Now how can I perform this
Sent from my Motorola Moto G 2014 using XDA Labs
---------- Post added at 11:57 AM ---------- Previous post was at 11:52 AM ----------
It is listed when I turned off the Mtp. But when I give the first command to backup the misc folder I get
[?] /dev/block/platform/soc/7824900.sdhci/by-name/misc: 1048576/?.
Sent from my Motorola Moto G 2014 using XDA Labs
---------- Post added at 12:17 PM ---------- Previous post was at 11:57 AM ----------
Again solved it. I just backed up the misc in twrp itself by copying the misc file to the /sdcard using the inbuilt file manager of twrp. Then tried the second command. It worked like charm. Thank you
Sent from my Motorola Moto G 2014 using XDA Labs
Perfect!
Thank you, TheFixItMan! I have an XT1672, Android 7.0 Stock Rom, and I was having this problem after trying the November update via OTA. The correction steps worked perfectly! Happy New Year!
Thanks hope to try this tonight, have you had feedback that this works? Thanks