First,
*
Grateful for the help and attention of those who saw it then
*
My problem is the following,
I own a Razr - XT890 JB. (To my knowledge, the last update provided by Software him, was the "Claro Brazil")
*
I modified my build.prop Mobile, everything went well,
More on grounds of extreme stupidity mine, I opted to return the original
however, when you replace the file did not give priority to the recording file, as it should have done, and rebooted the machine, all unintentionally;
*
From there, caught in the Bootloader screen
*
I tried different ROMs, which came closest is the XDA Rom,RazRi_JB_X-2014-Jul-11.zip
She reaches in the Rom Boot screen, install everything perfectly, plus al relates to a Bootloader,
Other Roms give error, or error in / system / build.prop other give that error related command line "getvar max-download-size"
*
Please, I request immediate help, RSD does not also recognize the device to which the installation commands from it, and I have no great knowledge to try to "solo" via SDK commands, correct me about the errors.
*
But here I am, if you have a forum that I still have hope that helps me is this,
*
If anyone can (and if they work of course) upload or give me a link of a BKP-ROM of this apparatus, I believe that giving the System Restore Partition with Original Build.prop everything is working again, I searched for a good gringos forums , and saw some similar cases are resolved well, but with other devices.
*
*
I hope I was clear enough.
*
*
Without more,
Thank you again.
From A very desperate Brazilian
klizardstz said:
First,
*
Grateful for the help and attention of those who saw it then
*
My problem is the following,
I own a Razr - XT890 JB. (To my knowledge, the last update provided by Software him, was the "Claro Brazil")
*
I modified my build.prop Mobile, everything went well,
More on grounds of extreme stupidity mine, I opted to return the original
however, when you replace the file did not give priority to the recording file, as it should have done, and rebooted the machine, all unintentionally;
*
From there, caught in the Bootloader screen
*
I tried different ROMs, which came closest is the XDA Rom,RazRi_JB_X-2014-Jul-11.zip
She reaches in the Rom Boot screen, install everything perfectly, plus al relates to a Bootloader,
Other Roms give error, or error in / system / build.prop other give that error related command line "getvar max-download-size"
*
Please, I request immediate help, RSD does not also recognize the device to which the installation commands from it, and I have no great knowledge to try to "solo" via SDK commands, correct me about the errors.
*
But here I am, if you have a forum that I still have hope that helps me is this,
*
If anyone can (and if they work of course) upload or give me a link of a BKP-ROM of this apparatus, I believe that giving the System Restore Partition with Original Build.prop everything is working again, I searched for a good gringos forums , and saw some similar cases are resolved well, but with other devices.
*
*
I hope I was clear enough.
*
*
Without more,
Thank you again.
From A very desperate Brazilian
Click to expand...
Click to collapse
As i can read from your post, u do have an unlocked bootloader and u do have installed a custom recovery. U can access the recovery and wipe partitions. If so, all can be solved.
A build.prop change may get you a bootloop, but shouldn't be able to remove the device installation methods and booting of other roms.
There is a huge chance that something in your data partition doesn't match the things that the rom wants to boot, so u get the bootloop. What it is can be difficult to say, only a logcat can provide answers if it works.
There are 4 methods to solve this.
1. hope logcats works and find the root of the problem (can be very difficult, if u dont know what logcat does and how it works)
2. download a custom rom, wipe the system, data and cache partitions and install a fresh custom rom
3. download your newest firmware from here and install by RSD lite when in Fastboot mode (power + volume down)
4. manually flash and wipe the new firmware
D:
Hazou said:
As i can read from your post, u do have an unlocked bootloader and u do have installed a custom recovery. U can access the recovery and wipe partitions. If so, all can be solved.
A build.prop change may get you a bootloop, but shouldn't be able to remove the device installation methods and booting of other roms.
There is a huge chance that something in your data partition doesn't match the things that the rom wants to boot, so u get the bootloop. What it is can be difficult to say, only a logcat can provide answers if it works.
There are 4 methods to solve this.
1. hope logcats works and find the root of the problem (can be very difficult, if u dont know what logcat does and how it works)
2. download a custom rom, wipe the system, data and cache partitions and install a fresh custom rom
3. download your newest firmware from ## and install by RSD lite when in Fastboot mode (power + volume down)
4. manually flash and wipe the new firmware
Click to expand...
Click to collapse
Sorry for the delay dear friend.
I am currently without a computer and unable to respond, since the cell has not returned to work,
tried the "LogCat" and without success, a message that has no logs, not even the XDA App worked,
Should I start worrying?
Also already tried several ROM'S, the only one that installs with success is that I found here on XDA, however the bootloop, since other, or withdrawing the "GetJar" they conclude.
Someone to help this desperate soul?
Grateful friends.
You are my last hope.
klizardstz said:
Sorry for the delay dear friend.
I am currently without a computer and unable to respond, since the cell has not returned to work,
tried the "LogCat" and without success, a message that has no logs, not even the XDA App worked,
Should I start worrying?
Also already tried several ROM'S, the only one that installs with success is that I found here on XDA, however the bootloop, since other, or withdrawing the "GetJar" they conclude.
Someone to help this desperate soul?
Grateful friends.
You are my last hope.
Click to expand...
Click to collapse
I don't get you very good. Just answer my questions so i understand your situation better.
1. How are u installing those roms?
2. Do u have a custom recovery?
3. If u have a custom recovery do u have a nandroid backup to restore your data?
4. If u are installing a new rom from here on xda, do u format system, data, cache? (full wipe)
5. If u still don't know. Read "INDEX/GUIDE, ALL Things RAZR I". Link under this. And go to "J". Read the instructions and read how to use RSD-Lite and were to download your latest firmware.
I have the feeling u are new to android. (maybe i am wrong, sorry) Just an advise for further things, always have a backup plan.
Hope this helps, i will hear it.
Hazou said:
I don't get you very good. Just answer my questions so i understand your situation better.
1. How are u installing those roms?
2. Do u have a custom recovery?
3. If u have a custom recovery do u have a nandroid backup to restore your data?
4. If u are installing a new rom from here on xda, do u format system, data, cache? (full wipe)
5. If u still don't know. Read "INDEX/GUIDE, ALL Things RAZR I". Link under this. And go to "J". Read the instructions and read how to use RSD-Lite and were to download your latest firmware.
I have the feeling u are new to android. (maybe i am wrong, sorry) Just an advise for further things, always have a backup plan.
Hope this helps, i will hear it.
Click to expand...
Click to collapse
Answers:
1 - Various shapes, tried by RSD 6.1.5 and also tried the 6.1.4, I have tried sideloading, and the Recovery of the XT890, both insalam not only the rom I mentioned above
2 - If by "Custom Recovery" you referred to CWM own the "CWM-based Recovery v6.0.1.5" version (Otherwise understand the fast stuff, just redirect me what you mean.)
3 - I do not have backups, just a backup I made before starting the procedures, then my build.prop is still without overwriting permissions
4 - Yes, always before any attempts, I place one Wipe data / factory reset, and still enter the sector of partitions and format the partitions, I'll mount / system, / cache, / data, / and the inside of virtual which is represented as a SDCARD format, all of them, and then install the ROM.
5 - As for reading, I'll check, As the experience in Android, I am not so layman, plus the more technical parts'm starting to learn now, as self-taught, I have extensive knowledge in the areas of computer science and a good reasoning, I believe it will be easy to be guided by you;
Thanks again for the attention paid to me. :good:
klizardstz said:
Answers:
1 - Various shapes, tried by RSD 6.1.5 and also tried the 6.1.4, I have tried sideloading, and the Recovery of the XT890, both insalam not only the rom I mentioned above
2 - If by "Custom Recovery" you referred to CWM own the "CWM-based Recovery v6.0.1.5" version (Otherwise understand the fast stuff, just redirect me what you mean.)
3 - I do not have backups, just a backup I made before starting the procedures, then my build.prop is still without overwriting permissions
4 - Yes, always before any attempts, I place one Wipe data / factory reset, and still enter the sector of partitions and format the partitions, I'll mount / system, / cache, / data, / and the inside of virtual which is represented as a SDCARD format, all of them, and then install the ROM.
5 - As for reading, I'll check, As the experience in Android, I am not so layman, plus the more technical parts'm starting to learn now, as self-taught, I have extensive knowledge in the areas of computer science and a good reasoning, I believe it will be easy to be guided by you;
Thanks again for the attention paid to me. :good:
Click to expand...
Click to collapse
okey, so u have some experience. I just misunderstood you then. my bad, sorry.
Even with a full wipe/format of everything and installing a custom rom u can't get it to boot. It will stay in a bootloop or even worse, don't go past the bootloader unlock screen.
With RSD-Lite (administrator) 6.1.6, 6.1.5 and 6.1.4 and all the drivers installed correctly and ready to run it won't recognize your phone when it is in (ap) fastboot mode. And if it recognizes your phone. At what part does it give an error, what is the error in rsd-lite/phone screen? Getvar error is more like a warning. We can disable that one.
Never seen this what u have. Because u can get into recovery, but the device won't boot. Will wait at your next post to confirm the above
Hazou said:
okey, so u have some experience. I just misunderstood you then. my bad, sorry.
Even with a full wipe/format of everything and installing a custom rom u can't get it to boot. It will stay in a bootloop or even worse, don't go past the bootloader unlock screen.
With RSD-Lite (administrator) 6.1.6, 6.1.5 and 6.1.4 and all the drivers installed correctly and ready to run it won't recognize your phone when it is in (ap) fastboot mode. And if it recognizes your phone. At what part does it give an error, what is the error in rsd-lite/phone screen? Getvar error is more like a warning. We can disable that one.
Never seen this what u have. Because u can get into recovery, but the device won't boot. Will wait at your next post to confirm the above
Click to expand...
Click to collapse
Yes, I have some experience, nothing more than apologize, who should apologize me for the inconvenience,
anyway ...
6.1.6 not tried, however, all other dao errors, and they are variable, depending on the rum,
Ex: Error 1/11, 6/12/8/10 and etc ...
already in CWM also varies, but with other command lines, and yes, even with all procedures, with pull and push the build.prop files, giving the command "chmod 644 build.prop" or even chmod 777 apparently can not the permiçoes there a way to delete the build, and relocate it on the partition / system?
also could not find any error like this, evil technology is that it seems that every problem is like a biological virus, mutates and hinders every time. LOL, since I do not know what to do: /
I look carefully your help friend.
* I've tried replacing build.prop, the original, by others, by the Galaxy S2, nothing more useless
as the part that mentioned at the end of your post, yes, I can do everything, however nothing stops the bootloop.
any suggestions?
klizardstz said:
Yes, I have some experience, nothing more than apologize, who should apologize me for the inconvenience,
anyway ...
6.1.6 not tried, however, all other dao errors, and they are variable, depending on the rum,
Ex: Error 1/11, 6/12/8/10 and etc ...
already in CWM also varies, but with other command lines, and yes, even with all procedures, with pull and push the build.prop files, giving the command "chmod 644 build.prop" or even chmod 777 apparently can not the permiçoes there a way to delete the build, and relocate it on the partition / system?
also could not find any error like this, evil technology is that it seems that every problem is like a biological virus, mutates and hinders every time. LOL, since I do not know what to do: /
I look carefully your help friend.
* I've tried replacing build.prop, the original, by others, by the Galaxy S2, nothing more useless
as the part that mentioned at the end of your post, yes, I can do everything, however nothing stops the bootloop.
any suggestions?
Click to expand...
Click to collapse
I have 2 more suggestions.
1. we manually flash/erase all things through mfastboot and see what happens.
2. We need a micro sdcard and we move the system partition from your phones internal memory to your sdcard, so it can boot from your sdcard. Because you have access to recovery and boot we can try this.
But i need some more time to write this up. especially the second thing. Never done it, but it is possible seen it before and read it. u can search around on the internet about those 2 things before we try anything. Will follow your post or edit this one with the worked out suggestions.
What i find weird about all this. U said u formatted all the partitions and even then with the right stock firmware from your mobile it wouldn't boot or anything. And the formatting off the partitions did work, so there should be no error anywhere normally. Because it does mean there is no memory error and the recovery can read and write stuff. U do have the xt890 and the right stock firmware (JB), don't u?
And next to that. After installing a new rom (with formatting of all partitions(system/cache/data)) u still try to change the build.prop. After a format it shouldn't be there anymore. Can u format everything (manually, not with full wipe, but with the options format system etc., again only system, cahce and ata or u can screw it even more ) again and see with adb through recovery if there is any file left on the system partition. Mount /system and do in adb shell in recovery a search for the build.prop. When in adb shell the command "ls system" should give u a list with all the files in it.
Hazou said:
I have 2 more suggestions.
1. we manually flash/erase all things through mfastboot and see what happens.
2. We need a micro sdcard and we move the system partition from your phones internal memory to your sdcard, so it can boot from your sdcard. Because you have access to recovery and boot we can try this.
But i need some more time to write this up. especially the second thing. Never done it, but it is possible seen it before and read it. u can search around on the internet about those 2 things before we try anything. Will follow your post or edit this one with the worked out suggestions.
What i find weird about all this. U said u formatted all the partitions and even then with the right stock firmware from your mobile it wouldn't boot or anything. And the formatting off the partitions did work, so there should be no error anywhere normally. Because it does mean there is no memory error and the recovery can read and write stuff. U do have the xt890 and the right stock firmware (JB), don't u?
And next to that. After installing a new rom (with formatting of all partitions(system/cache/data)) u still try to change the build.prop. After a format it shouldn't be there anymore. Can u format everything (manually, not with full wipe, but with the options format system etc., again only system, cahce and ata or u can screw it even more ) again and see with adb through recovery if there is any file left on the system partition. Mount /system and do in adb shell in recovery a search for the build.prop. When in adb shell the command "ls system" should give u a list with all the files in it.
Click to expand...
Click to collapse
I'll look around this friend, I wonder if I can really expect his return to the subject, you have been the one to support me here, and do not locate anything about the internet.
So your recommendation would be to wait or try to?
Because ruin even more ...
I have the sd card and just download the mfastboot-v2.zip
make a backup of the rom and try what then?
Is there any tutorial link, or can guide me trough this process?
If it is not possible to just show me that not of, and the way I try, the second part I do not know how to do, never read about it, but I will also look ...
Run the risk of damaging the hardware?
klizardstz said:
I'll look around this friend, I wonder if I can really expect his return to the subject, you have been the one to support me here, and do not locate anything about the internet.
So your recommendation would be to wait or try to?
Because ruin even more ...
I have the sd card and just download the mfastboot-v2.zip
make a backup of the rom and try what then?
Is there any tutorial link, or can guide me trough this process?
If it is not possible to just show me that not of, and the way I try, the second part I do not know how to do, never read about it, but I will also look ...
Run the risk of damaging the hardware?
Click to expand...
Click to collapse
Ok, to fast to much
First do this and post the results.
1. reboot in recovery
2. connect phone (in recovery mode) with usb to PC
3. check with adb if the pc can see the phone with the command: "adb devices". Should give u a device. Name should be a sequence of numbers
4. if in step 3 you get a phone. Type "adb remount" and enter
5. type: "adb shell" and enter
6. type: "mount /system" and enter
7. type: "ls /system" and enter
8. post the results of step 7.
We will see after this what to do next
Results
Hazou said:
Ok, to fast to much
First do this and post the results.
1. reboot in recovery
2. connect phone (in recovery mode) with usb to PC
3. check with adb if the pc can see the phone with the command: "adb devices". Should give u a device. Name should be a sequence of numbers
4. if in step 3 you get a phone. Type "adb remount" and enter
5. type: "adb shell" and enter
6. type: "mount /system" and enter
7. type: "ls /system" and enter
8. post the results of step 7.
We will see after this what to do next
Click to expand...
Click to collapse
So come on friends,
So ... to start already gave an error that bothered me before.
Post the picture, damn contradiction failed: Success
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And here's the result ....
hmm, that doesn't look bad.
We try the following steps to get you back to stock. Every step needs to give an 'OKEY' if not, report here.
For this we need to have mfastboot. So download it and set it up.
Download your latest official firmware (4.1.2) for your device. So coming from EU use EU, BR use BR etc. And extract it. Copy mfastboot into those files or copy all the files into the mfastboot directory file.
1. reboot in bootloader
2. do: 'mfastboot devices' and you get medfield******** device. If not, your drivers and mfastboot are not setup properly
3. do: 'mfastboot flash gpt gpt_signed' get 'OKEY'
4. do: 'mfastboot flash motoboot motoboot' get 'OKEY'
5. do: 'mfastboot flash boot boot_signed' get 'OKEY'
6. do: 'mfastboot flash recovery recovery_signed' get 'OKEY'
7. do: 'mfastboot flash motobp motobp' get 'OKEY'
8. do: 'mfastboot flash system sysem_signed' get 'OKEY'
9. do: 'mfastboot flash cdrom cdrom_signed' get 'OKEY'
10. do: 'mfastboot erase cache' get 'OKEY'
11. do: 'mfastboot erase userdata' get 'OKEY'
Report back with what u get. I hope that if u get any error we can fix it.
Hazou said:
hmm, that doesn't look bad.
We try the following steps to get you back to stock. Every step needs to give an 'OKEY' if not, report here.
For this we need to have mfastboot. So download it and set it up.
Download your latest official firmware (4.1.2) for your device. So coming from EU use EU, BR use BR etc. And extract it. Copy mfastboot into those files or copy all the files into the mfastboot directory file.
1. reboot in bootloader
2. do: 'mfastboot devices' and you get medfield******** device. If not, your drivers and mfastboot are not setup properly
3. do: 'mfastboot flash gpt gpt_signed' get 'OKEY'
4. do: 'mfastboot flash motoboot motoboot' get 'OKEY'
5. do: 'mfastboot flash boot boot_signed' get 'OKEY'
6. do: 'mfastboot flash recovery recovery_signed' get 'OKEY'
7. do: 'mfastboot flash motobp motobp' get 'OKEY'
8. do: 'mfastboot flash system sysem_signed' get 'OKEY'
9. do: 'mfastboot flash cdrom cdrom_signed' get 'OKEY'
10. do: 'mfastboot erase cache' get 'OKEY'
11. do: 'mfastboot erase userdata' get 'OKEY'
Report back with what u get. I hope that if u get any error we can fix it.
Click to expand...
Click to collapse
Glad for his preliminary Topic...
However, at the first command line can not, aliases, I tried the following, by having obtained the medfield by adb devices, however the following are recognized as command, however not result in anything ...
I downloaded several fastboot. put in the platform-tools, copied the files Adb & Co. as indicated on the internet, however to no avail, any suggestions?
Here's the Dammit CMD Lines.
U need to be in fastboot (bootloader) mode. From recovery u can get there by doing 'adb reboot bootloader' but the fastest way is just reboot your phone with the key combination volume down + power.
Fastboot mode is the mode before u enter recovery. It is also called bootloader.
Verstuurd van mijn GT-P5110
Youre rock!
Hazou said:
U need to be in fastboot (bootloader) mode. From recovery u can get there by doing 'adb reboot bootloader' but the fastest way is just reboot your phone with the key combination volume down + power.
Fastboot mode is the mode before u enter recovery. It is also called bootloader.
Verstuurd van mijn GT-P5110
Click to expand...
Click to collapse
My dear friend,
I have only two more questions for you,
1-How to turn you into a God?
HUEHUEHUE
2-How to increase your reputation?
- At first, the phone would not update the motoboot, however I had the idea to go giving procedure at all, and by the penultimate system, since it would give flash remake the build.prop. and then the motoboot was smoothly. like a feather on a cliff.
Really do not have words enough to thank you all this support that during all this time gave me.
Consider the topic as closed, and for others who have the same problem, I recommend reading it.
You are a Genius emerged from a magic lamp friend.
eternally Grateful
:good::victory:
1. Could be a problem, maybe if u have connections to Zeus, god, Allah or whoever XD
2. U can hit the thanks button under my posts if u want
Glad to hear all is fine now good luck with whatever u want to do now!
Verstuurd van mijn GT-P5110
Decided to OTA (not sure why) my Moto G LTE that was and was running stock but with an unlocked bootloader but have ran into issues and think i am now just digging a bigger hole for myself so I am asking for some help please.
I after the attempted update i started having issues with some apps not working and/or uninstalling themselves. Play store was the worst (tired wiping cache and data but no joy) then the camera decided it would uninstall and then any other camera apps in added wouldn't save pictures. Managed to get a fresh stock rom install.
So i though i'd update to CM13, downloaded the file, twrp and Gapps and set about booting into recovery to install twrp but initially i was unable to enter recovery and it stayed on the fastboot screen. Now i am getting the dead android and the red triangle but have a working stock rom.
I can now no longer use fastboot, all it does is start the rom as if i had just powered on normally.
Any help appreciated.
mclovin9091 said:
Decided to OTA (not sure why) my Moto G LTE that was and was running stock but with an unlocked bootloader but have ran into issues and think i am now just digging a bigger hole for myself so I am asking for some help please.
I after the attempted update i started having issues with some apps not working and/or uninstalling themselves. Play store was the worst (tired wiping cache and data but no joy) then the camera decided it would uninstall and then any other camera apps in added wouldn't save pictures. Managed to get a fresh stock rom install.
So i though i'd update to CM13, downloaded the file, twrp and Gapps and set about booting into recovery to install twrp but initially i was unable to enter recovery and it stayed on the fastboot screen. Now i am getting the dead android and the red triangle but have a working stock rom.
I can now no longer use fastboot, all it does is start the rom as if i had just powered on normally.
Any help appreciated.
Click to expand...
Click to collapse
You say you have working stock rom, so can you boot your phone to home screen? If so in ADB try using this command in CMD "mfastboot reboot bootloader" without the speech marks.
stonedpsycho said:
You say you have working stock rom, so can you boot your phone to home screen? If so in ADB try using this command in CMD "mfastboot reboot bootloader" without the speech marks.
Click to expand...
Click to collapse
Yes can get onto the home screen and use the phone (so far) without issue, get as far as the fastboot screen but then states 'fastboot' is not recognized as an internal or external command, operable program or batch file. That is given for any command including "reboot"
Stock ROMs do things like that to unlocked phones.
Check if you still have root access - I'm guessing you lost it, so you'll need to root again - Root Checker
Flash again the last and the proper TWRP tool (make sure you download for THEA) using the Rashr Flash Tool app if you can't access the fastboot screen.
Put your ROM on a SD card, erase everything and reinstall the system and the proper gapps (use at least MINI, so you could recover your old settings from your google account at first launch).
But think about ditching the stock - give Temasek a try. You will have to modify a couple of files to make the TITAN release work on your THEA, but it's worth aplenty.
Keep us posted.
mclovin9091 said:
Yes can get onto the home screen and use the phone (so far) without issue, get as far as the fastboot screen but then states 'fastboot' is not recognized as an internal or external command, operable program or batch file. That is given for any command including "reboot"
Click to expand...
Click to collapse
Have you enabled "usb debugging"? in developer settings (tap the build number 7 times) Do you have ADB installed? If so did you open CMD in the ADB folder?
FCorvin said:
Stock ROMs do things like that to unlocked phones.
Check if you still have root access - I'm guessing you lost it, so you'll need to root again - Root Checker
Flash again the last and the proper TWRP tool (make sure you download for THEA) using the Rashr Flash Tool app if you can't access the fastboot screen.
Put your ROM on a SD card, erase everything and reinstall the system and the proper gapps (use at least MINI, so you could recover your old settings from your google account at first launch).
But think about ditching the stock - give Temasek a try. You will have to modify a couple of files to make the TITAN release work on your THEA, but it's worth aplenty.
Keep us posted.
Click to expand...
Click to collapse
Cheers, any info on what files need modding?
Was rooted, managed to get adb to work last night and managed to reinstall twrp but now i can't get the rom to load and can't flash any CROM.
So used the all in one tool to re install stock 5.0.2.
Going to grab a brew and chill for a bit.
Aiight, once you downloaded the zip on your PC, go to:
1. ...titan.zip\META-INF\com\android
Drag the "metadata" file on a notepad page and replace 0x4882 with 0x4821 (your phone's bootloader code) and save.
2. ...titan.zip\META-INF\com\google\android
Drag the "updater-script" file on a notepad page, hit "Search and replace" for any of the XT's in there with yours, XT1072.
You will have 3 hits.
Example: Search and replace XT1069 with XT1072 ->
getprop("ro.product.device") == "XT1069"
getprop("ro.build.product") == "XT1069"
titan,titan_umts,titan_udstv,titan_umtsds,titan_retaildsds,XT1068,XT1064,XT1063,XT1069
will become:
getprop("ro.product.device") == "XT1072"
getprop("ro.build.product") == "XT1072"
titan,titan_umts,titan_udstv,titan_umtsds,titan_retaildsds,XT1068,XT1064,XT1063,XT1072.
(3 - while still here)
Search and replace the initial 0x4882 bootloader with yours, 0x4821.
Save the changes.
And... you're good to go.
Some native Moto apps won't show up in PlayStore because of this, but you can get all the Moto stuff from here (if you really love them).
Once installed, enjoy the full power of your brand new Android 6 phone.
Don't forget to do all the things you did as a kid once: activate the developer options as mentioned above, set the SuperSu permissions and so on.
However: screw-ups occur mainly because of conflicts between the new and the old, so you will have to perform a clean install as advised here, which means wiping everything you had - so you won't be able to return to your Lollipop Stock through any recovery.
So chill some more and consider everything thoroughly.
Cheers.
bloody phones, dunno ewhat happened but seems like reinstalling the SROM for the 2nd time allowed me to boot into recovery, twrp and load the CROM. Only issue this time was that apparently stock gapps was too big for the phone so had to download and install the mini version.
Will see how CM13 goes and download the Temasek for install later once im happy everythings working.
Where I can find official ROM for asus me375cl based on android 5.1.1?
Finaly, i find zip with official ROM on 4pda:
4pda-ru/forum/index.php?showtopic=799982
(put '.' (dot) instead '-' in url)
A special thank to alexoid79 for instruction.
little_pindos said:
Finaly, i find zip with official ROM on 4pda:
4pda-ru/forum/index.php?showtopic=799982
(put '.' (dot) instead '-' in url)
A special thank to alexoid79 for instruction.
Click to expand...
Click to collapse
Thank you so much for posting where you found this, this is exactly what I needed!!! You saved my tablet, it is much appreciated! :good:
Flashing Factory Image
The following instructions worked for me when trying to reflash the factory firmware for the ATT Asus MemoPad 7 LTE (ME375CL). I did originally try using the Asus Flash Tool and the raw firmware file (link below) but the tool said it could not unzip the package for some reason or another. So the steps below show how I did it using ADB with fastboot.
I ASSUME NO LIABILITY SHOULD THIS GO WRONG FOR YOU! However, it probably shouldn't matter if you are bricked, I doubt it will make it any worse Either way, I will not replace your tablet or be responsible for troubleshooting it should you mess it up more...
This scenario is based on the tablet stuck on the Asus boot screen and not going any further. I was trying some in depth rooting attempts and bricked it badly. I was then trying to install a custom recovery and that is why I could not reset it and bricked it.
PRE-REQS:
1. ADB installed - Download: https://drive.google.com/open?id=0B0fKccJIuWsna04wMjY1eG9YREU
2. Asus Drivers installed
3. Firmware - Download: https://drive.google.com/open?id=0B0fKccJIuWsnWGhwYzA0Vkluc2s (file is 1 Gb + in size, may take a bit)
SETUP:
If you already have a working ADB setup, do not download the one above. If you are using the one above, I extracted the folder into my C: drive, so the path for ADB would be C:\adb (to keep it simple and less typing).
MAKE SURE THE ASUS DRIVERS ARE INSTALLED! If you have plugged the tablet in to a pc before, they should already be there. Otherwise search, download and install the appropriate drivers.
INSTRUCTIONS:
Extract the firmware zip file to somewhere easily accessible like your desktop. In there, you should see the boot.img, recovery.img and system.img files, copy/paste those files to your ADB folder (for easier typing later on). There are also additional files like these but start with "unsigned_", do NOT use those!
1. Ensure you probably have at least 30% battery charge, I would still recommend more though.
2. Put the tablet in Fastboot mode by ensuring the tablet is completely powered down and then press/hold the VOLUME UP and POWER keys at the same time. When the Asus screen appears, let go of the POWER button but continue to hold the VOLUME UP button. Let go of the VOLUME UP button when the fastboot screen appears.
3. Plug the tablet in to the computer and then open a CMD prompt as administrator.
4. The following uses the ADB downloaded and placed in the folder as listed above, you may need to adjust the location path as needed if you already have ADB installed or located in a different path.
Type in the following without the quotes: "cd c:\adb" (this will change the path to the ADB files for the CMD prompt)
Type in the following without the quotes: "fastboot devices" (you should then see a device listed)
Type in the following without the quotes: "fastboot flash recovery recovery.img" (flashes the factory recovery image)
Type in the following without the quotes: "fastboot flash system system.img" (flashes the factory system image, may take a while to flash)
Type in the following without the quotes: "fastboot flash boot boot.img" (flashes the factory boot image)
5. Once those 3 images have been flashed, you should have seen a message that says "OKAY" after each one. You should be fine as long as you do not have any red error messages on your tablet.
Type in the following without the quotes: "fastboot reboot" (reboots device normally)
6. If all goes well, it should now boot to the Asus screen and then go to the ATT screen. If so, it will stay on the ATT screen for a while, just wait it out. Mine took about 12-15 minutes and then it opened to the new setup screen to set the tablet up as if its new!
This is how I was able to recover my bricked tablet, hopefully it can help someone else that may run into this.
John, thank you for the write-up. Just bought my ME375CL with 4.4.4.4.
When I try to flash the recovery partition, I get the following error:
C:\Users\Myself\Desktop\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11312 KB)...
OKAY [ 1.047s]
writing 'recovery'...
(bootloader) Official image.
FAILED (remote: flash_cmds error!
)
finished. total time: 2.344s
Click to expand...
Click to collapse
and on the tablet's screen:
FASTBOOT CMD WAITING...
RECEIVE DATA...
E:recovery flash failed!
FLASH FAILED!
RESULT: FAIL(flash_cmds error! )
Click to expand...
Click to collapse
I haven't tried the other commands for system.img or boot.img as I don't want to do anything out of order from the write-up. Ever run into this?
The firmware in the download is 5.1.1, not 4.4.4. That is probably the issue. If you are running good on that, I would try rooting it instead. If you are just wanting to upgrade, you will need to have an active AT&T SIM in the tablet to upgrade over the air. I am not sure if there is a flashable upgrade or not somewhere.
Oh ok John. I misread the title of the thread. I thought it was for updating from 4 to 5.
Quick question then: Is it possible, using the adb / fastboot tools, to backup the current 4.4.4.4 before I allow the tablet to update to Lollipop? After reading around, I understand that Lollipop can't be rooted but I have no real concern for it. But just in case I need the tablet to do something else in the future, I'd like to be able to return it to kit kat to be able to root.
Once you upgrade to lollipop, there is no downgrading for this tablet. There really is not much development for this device. I have kind of been working on a lollipop root when I can. Between my limited time and knowledge of android, I can't promise anything.
Overcoming red messages?
Dear John,
Thank you very much for your help. My device runs KitKat 4.4, I can't upgrade over the air, as I damaged my sim slot struggling to remove a stuck nano sim, which I had inserted before I realized that it required a micro sim. (I'd wrongly assumed that by now the world uses only nano).
I followed the steps above, which you wrote so clearly for lay men, thank you a lot.
The flash for recovery.img and system.img worked fine (no red error messages on device).
The flash for boot.img had a red error message.
Might you have an idea or workaround on how I can address this?
If it refuses, is it possible to factory reset?
Thank you very much again for any words of advice and kind regards.
Gor- said:
Dear John,
Thank you very much for your help. My device runs KitKat 4.4, I can't upgrade over the air, as I damaged my sim slot struggling to remove a stuck nano sim, which I had inserted before I realized that it required a micro sim. (I'd wrongly assumed that by now the world uses only nano).
I followed the steps above, which you wrote so clearly for lay men, thank you a lot.
The flash for recovery.img and system.img worked fine (no red error messages on device).
The flash for boot.img had a red error message.
Might you have an idea or workaround on how I can address this?
If it refuses, is it possible to factory reset?
Thank you very much again for any words of advice and kind regards.
Click to expand...
Click to collapse
Sounds odd that it did 2 out of 3 flashes. After you flashed those and rebooted, are you still on KitKat or did it actually update to Lollipop (5.1)? I ask because I assume the system image that flashed would be the operating system.
I still want to stress that this post is for recovering a bricked tablet that will not boot at all. I would not suggest using this as a flashing upgrade as I do not know if it will truly work. If you are still on KK (even after flashing) you could try installing the Asus Flash Tool and use the raw firmware that you downloaded and try it that way. It did not work for me so that is why I used fastboot. It might work for you.
Here is a link for the Asus Flash Tool:
https://drive.google.com/open?id=0B0fKccJIuWsndXJUa1FEbXVzTjA
johnkirchner said:
Sounds odd that it did 2 out of 3 flashes. After you flashed those and rebooted, are you still on KitKat or did it actually update to Lollipop (5.1)? I ask because I assume the system image that flashed would be the operating system.
I still want to stress that this post is for recovering a bricked tablet that will not boot at all. I would not suggest using this as a flashing upgrade as I do not know if it will truly work. If you are still on KK (even after flashing) you could try installing the Asus Flash Tool and use the raw firmware that you downloaded and try it that way. It did not work for me so that is why I used fastboot. It might work for you.
Here is a link for the Asus Flash Tool: ]
Click to expand...
Click to collapse
As a follow up on your question above, Tab restart stalled at a screen (after the Asus logo), presenting some options to do recovery, reboot, factory reset, etc. (factory reset did not help), and red error messages at bottom.
To the GOOD news for anyone interested. I used the Asus Flash Tool and the firmware zip for 5.1.1 (many thanks for the advice).
Note: Tool did not install correctly on Win10 pc, citing error in installing some devcon.exe or similar file (guess that may be a firewall/antivirus issue).
Flash tool took some 15 or so mins unzipping firmware, after which I saw some action on the tab. Another 15 mins, and it rebooted to the At&t logo, stayed here for another 15 mins and unraveled a whole new device on Android 5.1
Glad to hear it worked for you and that I guess you can use this to flash upgrade from kitkat!
There is working way to root our device on lollipop! It is for the other Asus model, but it works for our
http://4pda.ru/forum/index.php?s=&showtopic=640814&view=findpost&p=53047686
I will check this out!
The root works, installed without any issues and verified with a root checker!
Here is a direct download from my Drive folder: https://drive.google.com/open?id=0B0fKccJIuWsnN21ZbnZpc2F6b1E
1. Download the file above.
2. Extract the zip contents.
3. Plug your ME375CL tablet in to pc via usb cable.
4. Make sure you have enabled Developer Mode and allowed USB Debugging first!
5. Open the folder you extracted and double click the "Root-One-Click.cmd" file.
6. It should reboot to fastboot mode and flash the needed files and then reboot again.
You should now have root access. Verify this by installing a root checker app from the play store. Keep in mind, it may say root not installed on the first run. Sometimes it will take a moment for superuser to initially run or prompt for access.
Side note: the root uninstall did not seem to work, got an error...but oh well, the point is to have root!
Thanks go to @little_pindos for finding this file...you are a rockstar!
Anyone get xposed on LP?
ATT Boot Up Sound
Tired of the ATT boot sound? If you used the rooting method above, then you can get rid of the annoying ATT startup sound by doing the following:
1. Install a Root Browser app (I recommend Rom Toolbox Pro, it has a built in file manager)
2. Navigate to the following path:
root/system/media
3. Find the file named "powerup.wav"
4. Simply rename the file by adding .bak to the end (ex - powerup.wav.bak)
5. Make sure it took the name change (some file managers have issues with that)
6. Reboot and see if it got rid of the sound!
You can also use your own startup sounds as long as they are in a .wav format, I believe. Make sure that the name of the file is powerup.wav.
You can also change your boot animation with "boot animation" app.
Best tweak IMO is adding "ro.config.low_ram=true" to build prop, or installing the low ram device xposed module if we can get it to work (both do the same thing). You gain about 100mb more free RAM on average.
TimmyP said:
You can also change your boot animation with "boot animation" app.
Best tweak IMO is adding "ro.config.low_ram=true" to build prop, or installing the low ram device xposed module if we can get it to work (both do the same thing). You gain about 100mb more free RAM on average.
Click to expand...
Click to collapse
I'll have to try that!
AT&T no longer has updates in system for this tablet
Gor- said:
Dear John,
Thank you very much for your help. My device runs KitKat 4.4, I can't upgrade over the air, as I damaged my sim slot struggling to remove a stuck nano sim, which I had inserted before I realized that it required a micro sim. (I'd wrongly assumed that by now the world uses only nano).
I followed the steps above, which you wrote so clearly for lay men, thank you a lot.
The flash for recovery.img and system.img worked fine (no red error messages on device).
The flash for boot.img had a red error message.
Might you have an idea or workaround on how I can address this?
If it refuses, is it possible to factory reset?
Thank you very much again for any words of advice and kind regards.
Click to expand...
Click to collapse
AT&T removed the last update for this tablet months ago and no longer supports it. ASUS states AT&T has all the updates. Total cluster.