Hi,
Could someone please dump a system image for the 10.1? It's reeeealy easy
There are a few soft-bricks already due to people flashing the wrong image or to the wrong partition ( you know who you are, people! ) and you would be doing them a massive favour if you did.
If you already have busybox, all you have to do is run this:
Code:
dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
Then you can pick it up the system.img from /sdcard
Code:
adb pull /sdcard/system.img
ZIP it and upload it somewhere ( Dropbox ) and you're done!
TIA
BC
Http://droidbasement.com/galaxy/sys-backup
The system_extra backup contains extra stuff (from the 'tools' compilation).
Thanks. There are a couple of people who will really appreciate that
OT: I just repacked your su/busybox update with the boot.img from the Voda 10.1 and it works fine. Link to the Voda boot.img is here
Would it be possible to get the original system image without the extra tools? I am trying to flash this image however I keep getting a remote error when I do so. Could it have something to do with the fact that this image is 600MB compared to other system images that are around 200 MB like for the gt 10.1v? Thanks again for posting it.
the extra stuff is not making it 600mb (maybe 10-20). It is quite big on the IO.
In order to fastboot flash it you must have an unlocked bootloader to do so (which in unlocked by default on the IO).
Ok so my bootloader is unlock however every time I try flashing this image i get the following:
sending 'system' (591872 KB)...
FAILED (remote: (00000006))
finished. total time: 0.002s
I am able to flash other system images no problem however, this one seems to be giving me some issues. Any other ideas to flash this image successfully? Thanks.
nadewad said:
Ok so my bootloader is unlock however every time I try flashing this image i get the following:
sending 'system' (591872 KB)...
FAILED (remote: (00000006))
finished. total time: 0.002s
I am able to flash other system images no problem however, this one seems to be giving me some issues. Any other ideas to flash this image successfully? Thanks.
Click to expand...
Click to collapse
ill retake the dump and upload it. ill do it tonight. maybe some corruption ocurred, etc.
It might be the same trick where you have to create a sparse ext4 image instead of ripping the image straight, because fastboot transfers the entire image in RAM before flashing it...
Try
Code:
make_ext4fs -l 512m -s /sdcard/system.img /system
If anyone has created a system image but isn't quite sure if it is the correct one, I'll be glad to try it out as I am one of those people who soft bricked their device. Just PM me and I'll be more than happy to flash my device and verify the stability of the system image. Thanks.
Nader
bump? Did anyone end up getting a system image? Thanks.
Nader
Ok so I was able to get a hold of another system image however, it still failed with the same error.
ydaraishy mentioned something about using make_ext4fs to make a sparse image? How is this done exactly? Is this through the adb shell or is this a separate tool that can be used on a linux machine. Any help on bringing my device back to life would be greatly appreciated. Thanks.
nadewad said:
Ok so I was able to get a hold of another system image however, it still failed with the same error.
ydaraishy mentioned something about using make_ext4fs to make a sparse image? How is this done exactly? Is this through the adb shell or is this a separate tool that can be used on a linux machine. Any help on bringing my device back to life would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Run it on the device instead of using dd on the device.
ydaraishy said:
Run it on the device instead of using dd on the device.
Click to expand...
Click to collapse
He has a soft-bricked device so that's not an option unfortunately.
You can do a MD5 checksum of the file and get pershoot to check it against the original.
Otherwise, in the mean time, you can try this tool:
http://www.diskinternals.com/download/
You want the tool called "Linux Reader 2.0". It says it can only read ext2 and ext3, but I just tried it on my 10.1v system image which I created using the same method as pershoot, and it works fine.
...and see if you can mount it in Windows. If you can, the image is (probably) OK.
bcmobile said:
He has a soft-bricked device so that's not an option unfortunately.
Click to expand...
Click to collapse
Well, obviously, someone _else_ has to provide that image from a working device.
Same error here, while trying to flash the system.img. Any alternatives?
Thanks,
Eduardo.
I just received another system image from a friend of mine who created it using make_ext4fs. It does flash successfully however, it still leaves my device in a boot loop. Whats the button combination to get the device into recovery mode?
I find it funny that the boot, recovery and system images for the galaxy tab 10.1v actually work and the device runs. Although the accelerometer, camera and usb don't work though.
Eduardo if you would like, you can PM me and I can share with you the dropbox folder of the system image that actually flashed to see if it would work on your device.
I think at this point I may just throw in the towel and send my device back to Samsung to get repaired :/
Thanks to everyone on the xda forums who tried helping me out. You guys are truly awesome
nadewad said:
I just received another system image from a friend of mine who created it using make_ext4fs. It does flash successfully however, it still leaves my device in a boot loop. Whats the button combination to get the device into recovery mode?
I find it funny that the boot, recovery and system images for the galaxy tab 10.1v actually work and the device runs. Although the accelerometer, camera and usb don't work though.
Eduardo if you would like, you can PM me and I can share with you the dropbox folder of the system image that actually flashed to see if it would work on your device.
I think at this point I may just throw in the towel and send my device back to Samsung to get repaired :/
Thanks to everyone on the xda forums who tried helping me out. You guys are truly awesome
Click to expand...
Click to collapse
Samsung may charge you for the repair
Before you send it back, just have one more go at flashing the boot.img which smaskell provided from here. Just do a:
Code:
fastboot flash boot boot.img
The boot loop may be due to a different (incompatible) kernel if you still have the boot partition from the 10.1v
Failing that, if you're still up for it, do a:
Code:
adb logcat > %userprofile%\desktop\logcat-out.txt
...then open the locgat-out.txt file on your desktop and post the contents here or just zip and attach the file. That might give us something to work with
I am also not able to flash this system.img file. I get the same error.
I did remember to flash the boot image of the 10.1 over the 10.1v. However, even when the device is booting up I still can't get access to the adb shell. Any ideas as to why I cannot access the adb shell?
I did notice though that when I had typed in:
fastboot getvar product
It had returned GT-P7100 which is the product number for the Galaxy Tab 10.1v, however the Galaxy Tab 10.1 has the product number GT-P7510.
Could this be because I had accidentally flashed the 10.1v rom or that these devices both use the same version of fastboot etc?
nadewad said:
I did remember to flash the boot image of the 10.1 over the 10.1v. However, even when the device is booting up I still can't get access to the adb shell. Any ideas as to why I cannot access the adb shell?
I did notice though that when I had typed in:
fastboot getvar product
It had returned GT-P7100 which is the product number for the Galaxy Tab 10.1v, however the Galaxy Tab 10.1 has the product number GT-P7510.
Could this be because I had accidentally flashed the 10.1v rom or that these devices both use the same version of fastboot etc?
Click to expand...
Click to collapse
My tablet is showing P7100 as well. I tested with my employee's GT LE, and it shows the same. So, this is not the problem...
adb is not accessible to me as well.
Related
If you like that I'm doing this, then a thanks is cool, PLEASE DONATE, TIME OR MONEY BUT GIVE SOMETHING TO THESE DEVS!
http://tabletroms.com/forums/showthread.php?356-Honeycomb-on-the-Adam-(Updated)
New - No more partition editing required!
HC16JUN2011
HD Video
-Changelog
Like with any rom, YOU MUST WIPE CACHE, SYSTEM AND DATA, this rom especially, the is a pre alpha and has issues with cache, if you don't clear your info every time you will run into problems. I also clear Dalvik Cache and Battery Stats.
Old info on how to partition
STEP 1 – You need the new NVFlash click here for the unpartitioned onces(may need these)
NVflash edit- pretty simple you need to change the android fastboot full, you'll find that file towards the top of the nvflash folder or you can download my premade ones: (BUT I DIDN'T FORCE YOU TO DOWNLOAD THESE, IF YOU BRICK YOUR DEVICE BY USING THESE THEN YOU BRICKED IT NOT ME, YOU HAVE BEEN WARNED)
Sorry about the mega upload, working on getting my server up, also CWM is untested, it had some problems but I believe that was due to file size.
Clockwork Mod folder
Stock Recovery Folder
The section your looking for looks like this
[partition]
name=APP
id=9
type=data
allocation_policy=sequential
filesystem_type=yaffs2
size=209715200 <---(here is the money)
file_system_attribute=0
partition_attribute=0
allocation_attribute=0x10
percent_reserved=0
filename=system.img
minus the arrow and the here is the money you'll find the size listed as 209715200, you need to change that to 536870912, once you save go to here to setup your APX drivers and prepare to flash according to the link
STEP 1.1 – THIS IS FOR CLOCKWORK MOD RECOVERY ONLY Download Here
Make a copy of your nvflash folder, I name it PIXEL QI CW Mod
STEP 1.2 – THIS IS FOR CLOCKWORK MOD RECOVERY ONLY
Thank you darknao
Quick & Dirty method :
Extract the recovery.img from the clockwork.zip, and copy it to the nvflash folder(replace the original one).
Step 2
You need then to put your device into force recovery mode, so turn off your device, then power it on while holding the power + the volume down button till a orange and a yellow lite light up.
Step 3
Run the download.bat file described in the nvflash or unbrick your adam thread - now you can change the file name of the rom to update.zip and flash freely!
Reserved for other usage
Any idea when we'll get gapps working? Or you just linking to what they have done? Thanks for working to spread the word.
Amon Darthir said:
Any idea when we'll get gapps working? Or you just linking to what they have done? Thanks for working to spread the word.
Click to expand...
Click to collapse
Gapps are included however this build didn't have them, they had alot of problems with the sync feature, but in theory you should be able to use the latest gingerbread gapps, I will test that right now.
-OK I tested it out, the google setup frooze up on me, after restarting I was able to get into the initial setup, but I have the wifi only model, so I'm going to look into the gapp issue, see if I can find a way around.
-Tried a couple more copies of gapps including a HC edit for the nook sdk HC-- I would press more into this but with the rate of the updates I think its kinda pointless, for now Im going to adb push the market and see what I can get working, hopefully not in-vain since MrGuy and DJSteve move so fast with the updates.
after you use nvflash it will start to boot.. (this would be before flashing update zip) so should I power it down while its booting that first time in order to reboot to recovery and flash the zip?
I do but you don't have to if you use clockwork mod, it doesn't really matter, since you will be building your Dalvik cache once you install your rom.
$ ./download.sh
./nvflash: ./nvflash: cannot execute binary file
can anyone help me with this error i am getting when trying to run the downlaod script
jakobdroid said:
$ ./download.sh
./nvflash: ./nvflash: cannot execute binary file
can anyone help me with this error i am getting when trying to run the downlaod script
Click to expand...
Click to collapse
what operating system do you have? Is your adam in apx mode, and did you edit the android fastboot already? is it still a .bat file
osx, i already changed the file. what is apx mode? my adam has CWM on it, i understand that i am not supposed to have it for this HC rom. can i use the recovery image in the nvflash folder?
jakobdroid said:
osx, i already changed the file. what is apx mode? my adam has CWM on it, i understand that i am not supposed to have it for this HC rom. can i use the recovery image in the nvflash folder?
Click to expand...
Click to collapse
APX is the force recovery, the drivers are included with the NVflash, you must put your device into force recovery, with your device off you press volume down + power till you get your two lights to light up by the power cord, it'll be red and yellow, this is force recovery mode, I am using CW with it and I have listed above how to flash the CW with the increased partition. If you can't figure it out I will be adding the NVflash files with CW mode and non CW mode with the partition edits tonight. I will be turning the change log into a FAQ as well.
Just flashed the ROM and it is awesome. I was just wondering how to get a file managers working. I can't see my sd card. But otherwise, its amazing that honeycomb is up so fast.
okay my adam is in apx mode, i did your steps for using CWM, but im still getting the error:
./nvflash: ./nvflash: cannot execute binary file
i used chmod on the download.sh file, as well as nvflash. any idea whats going wrong?
jakobdroid said:
okay my adam is in apx mode, i did your steps for using CWM, but im still getting the error:
./nvflash: ./nvflash: cannot execute binary file
i used chmod on the download.sh file, as well as nvflash. any idea whats going wrong?
Click to expand...
Click to collapse
I'm downloading the file now, working on military lines so its slow to download but that way I can get a better idea of whats going on, also whats your operating system.
jakobdroid said:
okay my adam is in apx mode, i did your steps for using CWM, but im still getting the error:
./nvflash: ./nvflash: cannot execute binary file
i used chmod on the download.sh file, as well as nvflash. any idea whats going wrong?
Click to expand...
Click to collapse
Sounds like you're using linux like me. Are you on ubuntu. Cause I tried and tried and even with chmod and sudo and still got the same error. Consider this post though from: http://notioninkhacks.com/forums/viewtopic.php?f=90&t=1651&start=30
Hey gibson, thanks heaps for that! Actually, yourncomment before asking which folder I was in did it. Very strange, I had to run the commands from 2 folders above the extracted one, then symlink all the other files into the folder I was running from. Will post more later for people who run into similar issues, likely over at the unbricking thread. For now I've got a dualboot setup, and am running a minimal natty rootstock. I tried using the full omap4 image (ubuntu's default arm), but could only get it booting with lots of errors and no gui. Will be aiming to install the netbook desktop (unity 2d) in the next few days.
Re the post above, rayman's boot image already includes the kernel, so it's not needed in the rootstock command. Re the other options, probably will work, but remember rootstock is limited in what you can build... I.e., unless you have heaps of physical ram, you will probably only be able to build a few packages. Head over to xda, and the ubuntu on adam thread there for more info. We have experimented a lot with rootstock builds, and some of that might be useful.
Has anyone tried raymans boot.img with a natty rootstock? Did it work, and has anyone gotten a 2d unity gui up and running? My minimal natty rootstock boots fine, though I notice a few errors. Not sure if they are problematic or not. In any case, the build I made seems to be missing some important wireless tools, so I will likely rebuild it again with them in it soon. Am I likely to run into any problems using rayman's boot image, and steveh's kernel, with a natty build? Happy to post up my work if I get anything decent. Cheers.
osx 10.6.6, thank you!
jakobdroid said:
okay my adam is in apx mode, i did your steps for using CWM, but im still getting the error:
./nvflash: ./nvflash: cannot execute binary file
i used chmod on the download.sh file, as well as nvflash. any idea whats going wrong?
Click to expand...
Click to collapse
Also consider this: http://forum.xda-developers.com/archive/index.php/t-895388.html
Saved me some time thank you...
daiuton said:
Saved me some time thank you...
Click to expand...
Click to collapse
Don't know if the problem is solved yet but that doesn't take away from this honeycomb coolness. So happy to have so much use out of this Adam. Thanks.
that really didnt help, thanks though. i guess i will instal ubuntu in parallels and give it a shot...
Two problems here:
-How can i mount the adam with the computer? To move next updates and update in the next releases
-There is any gapps working (market,etc...)?
Hi all. Quick notice:
Usual disclaimers apply.
This is an Unsecure boot.img I made for Android 4.2 on the Nexus 4.
Okay cool... but what is an insecure boot.img?
An insecure boot.img allows the device to be booted with permissions to be mounted as root. This is a way of being able to push SuperSU/Superuser.apk to /system/app and the Su Binaries to /bin
adb shell
su
mount -o remount,rw /system
exit
See more here: External Link
_____________________________________________________________________________________________________________
To use this you must be unlocked, not familar with unlocking a Nexus device? Easy. In fastboot mode type "fastboot oem unlock" this wipes all data on the device (virtual sd included).
A nice article regarding this thread was published here: http://www.addictivetips.com/android/root-google-nexus-4-install-clockworkmod-recovery/
To boot this boot.img:
must be in the platform-tools folder in the android-sdk
must be in fastboot mode (power+vol-)
First use: fastboot boot "boot.img" (no ")
Why boot? I have not tested this image as I don't have a Nexus 4 as of yet.**
**Some users report flashing the image makes the phone in need of a fastboot stock flashing session, stick to booting for now.
Thank you for helping!
-fkrone
-Ranguvar
-USSENTERNCC1701E
This is mainly for development purposes to obtain root on this device, it will be an easier process when a recovery is published and you can flash a su.zip. (see attached)
DOWNLOAD HERE: http://www.androidfilehost.com/?fid=9390169635556426389
Note, this is in Nexus 7 folder as Nexus 4 does not have its own atm.
Click to expand...
Click to collapse
Please Lock!
Placeholder reserve
Harry GT-S5830 said:
Anyone able to get me recovery.fstab from recovery image and ill try make a cwm6 touch recovery for us.
I wouldn't be lazy and do it myself but PC is off
Sent from a phone
Click to expand...
Click to collapse
sgs2ext4 doesn't work on the recovery.img and the image isn't mountable by itself in Windows.
Too lazy to reboot into Linux, for now.. any other way to crack it open?
Ranguvar said:
sgs2ext4 doesn't work on the recovery.img and the image isn't mountable by itself in Windows.
Too lazy to reboot into Linux, for now.. any other way to crack it open?
Click to expand...
Click to collapse
Pull it apart in hex editor
Sent from my HTC Explorer A310e using xda app-developers app
Harry GT-S5830 said:
Anyone able to get me recovery.fstab from recovery image and ill try make a cwm6 touch recovery for us.
Sent from a phone
Click to expand...
Click to collapse
I've got the recovery.img, can I get the .fstab out without loop mounting? I don't have a linux machine set up right now.
USSENTERNCC1701E said:
I've got the recovery.img, can I get the .fstab out without loop mounting? I don't have a linux machine set up right now.
Click to expand...
Click to collapse
Old fashioned HxD
See here: http://forum.xda-developers.com/showthread.php?t=443994
I could probably do it without this, but it probably wouldn't mount data/media (what emulates the SD) so it would be relatively useless as that's where zips are
Also this might prove useful: http://forum.xda-developers.com/showthread.php?t=1494036 (requires Cygwin or Linux environment)
Harry GT-S5830 said:
Old fashioned HxD
See here: http://forum.xda-developers.com/showthread.php?t=443994
Click to expand...
Click to collapse
Hell, I wouldn't trust myself to rip it out with a hex editor. I'm setting up a VM right now, but I could just upload the recovery.img for you. I pulled it out of the stock image that google uploaded today.
USSENTERNCC1701E said:
Hell, I wouldn't trust myself to rip it out with a hex editor. I'm setting up a VM right now, but I could just upload the recovery.img for you. I pulled it out of the stock image that google uploaded today.
Click to expand...
Click to collapse
Cheers, that's where I had mine but I corrupted it :/ ill try pull it apart on the 600MHz wonder pico
Or perhaps not... 3.2" is too small for hex
Harry GT-S5830 said:
Cheers, that's where I had mine but I corrupted it :/ ill try pull it apart on the 600MHz wonder pico
Or perhaps not... 3.2" is too small for hex
Click to expand...
Click to collapse
Lol, I'm having a hell of a time getting Slax as a cooperative VM, might have to go all out with ubuntu
Got it!
Thanks for the tutorials. It was just fun to to something short after midnight (Germany). I was a little bit bored Would be nice if you can mention me in the people helped to create this recovery
http://www.mediafire.com/?mlv72phch1tgd5y Mediafire-Mirror
Dammit, beat me to it!
Serves me right for making dinner first
http://ompldr.org/vZ2ExYQ/recovery.fstab
Can i ask something as a future buyer of nexus 4 and older user of another phone...the fastboot is the "bootloader" (pink screen on my older phone) the state of the phone where i can connect it to my computer and see the folder containing the recovery.img boot.img...etc???
pikachukaki said:
Can i ask something as a future buyer of nexus 4 and older user of another phone...the fastboot is the "bootloader" (pink screen on my older phone) the state of the phone where i can connect it to my computer and see the folder containing the recovery.img boot.img...etc???
Click to expand...
Click to collapse
That's not quite how it works. These .img files we are talking about are pictures of the stock version of those paritions. Try reading this article for an explanation of Android partitioning.
There is also a great graphic here. The site is in Spanish, I haven't used Google to translate it, but the picture there is in English. Take your time with it, there's a lot of info there.
To get into Fastboot mode, do you just hold the volume down button while powering on? Never used a Nexus device before. Have been strictly on HTC up until now. I'm picking up my Nexus 4 in the morning and don't mind trying, as long as there's a way to undo anything in case something goes wrong.
Stryder5 said:
To get into Fastboot mode, do you just hold the volume down button while powering on? Never used a Nexus device before. Have been strictly on HTC up until now. I'm picking up my Nexus 4 in the morning and don't mind trying, as long as there's a way to undo anything in case something goes wrong.
Click to expand...
Click to collapse
Or you can enable adb and
Code:
adb reboot bootloader
The command
Code:
fastboot boot boot.img
is temporary. All it does is boot, one time only, the image you specify. Once you've mounted system as rw however, everything you do in /system before rebooting is permanent.
USSENTERNCC1701E said:
Or you can enable adb and
Code:
adb reboot bootloader
The command
Code:
fastboot boot boot.img
is temporary. All it does is boot, one time only, the image you specify. Once you've mounted system as rw however, everything you do in /system before rebooting is permanent.
Click to expand...
Click to collapse
So does adding the su binaries and the superuser apk give you permanent root after this then?
And exactly what binaries are needed to gain root? I've never gained root using that method before so am a little unfamiliar in this territory.
Stryder5 said:
So does adding the su binaries and the superuser apk give you permanent root after this then?
And exactly what binaries are needed to gain root? I've never gained root using that method before so am a little unfamiliar in this territory.
Click to expand...
Click to collapse
Woops, wrong thread.
Yes, if you push the su binary from a superuser flashable zip to /system/bin/ and chmod 0655, plus the superuser apk, you will have permanent root after.
Also, there is a recovery.img now, so you can test that out, if it works, flash it from fastboot, then flash a superuser zip from that recovery.
Thank you for getting it (recovery.fstab), looks like someone beat me to it though!
Sorry for late response I have to sleep as I'm in last school year
Ill cook up a recovery just to make your efforts worthwhile
It's in OP, its probably 99.9% the same as the other guys so i'm not going to make duplicate thread, use who evers recovery you wish.
____________________________________________________________________________________________________________________________________
Reason I say fastboot boot first is because it allows you to boot the image without permanently (well, unless you flash another over) flashing a partition without knowing it works.
Booted fine when I ran fastboot boot boot.img, but when I actually flashed it, it's giving me a boot loop now Booting back into fastboot shows secure boot still enabled. Any suggestions? Or do you have the original bootloader image?
Stryder5 said:
Booted fine when I ran fastboot boot boot.img, but when I actually flashed it, it's giving me a boot loop now Booting back into fastboot shows secure boot still enabled. Any suggestions? Or do you have the original bootloader image?
Click to expand...
Click to collapse
Not at my comp now or I'd upload it, bit of you rip open the fa Tory image from the Google servers you should find it
---------- Post added at 02:44 PM ---------- Previous post was at 02:43 PM ----------
On a side note, what possessed you to do that?
Can I just erase from settings to restore to default?
Sent from my XT1058 using XDA Premium 4 mobile app
our best bet is probably to follow this guide here...
http://forum.xda-developers.com/showthread.php?t=2446515
Or maybe easier would be just to...
fastboot flash system <nameofsystemfilehere>.img
I would have to double check my last bit of advice though.
Newbie help
is there anyway to do this without deleting my stuff. Sorry im a newbie at this. i orginialy installed the first root moto app and it had a unroot option. the new one doesnt and i really need to get back to stock without doing anything complicated
MarcusSi1516 said:
is there anyway to do this without deleting my stuff. Sorry im a newbie at this. i orginialy installed the first root moto app and it had a unroot option. the new one doesnt and i really need to get back to stock without doing anything complicated
Click to expand...
Click to collapse
Well...
fastbooting the system should not delete your user data. and its not really complicated.
Do you have ADB set up on your computer?
i think so
thepolishguy said:
Well...
fastbooting the system should not delete your user data. and its not really complicated.
Do you have ADB set up on your computer?
Click to expand...
Click to collapse
yah i do. but i origginaly downloaded root app as apk
MarcusSi1516 said:
yah i do. but i origginaly downloaded root app as apk
Click to expand...
Click to collapse
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
Okay - this is probably going to sound complicated but it is not that complicated...
First let's go over the easy version...
reboot into bootloader and...
fastboot flash system system.img
fastboot flash recovery recovery.img
####EDIT####
If fastboot will not flash the system.img use a different fastboot.exe created to flash the larger .img
arigi said:
The solution is to use the mfastboot.exe linked from here:
http://forum.xda-developers.com/showthread.php?t=2489249
Hope that helps someone trying to do this same thing.
Click to expand...
Click to collapse
And if you leave it named "mfastboot" then you must issue the commands with the "m"...
"mfastboot flash system system.img"
without the parenthesis of course
So that's the easy and short version. Do that and you have restored your phone to stock without losing your app data.
Now the complicated part is whether not you know what to do with that information? In fastboot if you type...
fastboot devices
...it should return you serial number. If it does not then you do not have the proper drivers installed. Install Motorola Device Manager and this should solve the problem http://goo.gl/DiRvpE
Then of course you need the system.img and the recovery.img http://sbf.droid-developers.org/ghost_rcica/list.php
MAKE SURE YOU DOWNLAOD THE FILES FOR THE RIGHT PHONE OR YOU ARE HOSED
Once you download that file you will have to unzip it with something like 7zip or Winrar and when you do you will find those files. Then the files have to be copied to the "platform-tools" folder of your android sdk (or the folder where your fastboot.exe is).
Then you can open a command prompt from that folder with your device attached and...
adb devices
...should return a serial number
adb reboot bootloader
...should reboot into bootloader
fastboot devices
...should return a serial number
fastboot flash system system.img
...should flash the system...
fastboot flash recovery recovery.img
...should flash the recovery...
fastboot reboot
...should reboot the device and you will enter set up but your user data will be preserved.
I am always nervous about helping people because if they break something they like to blame someone. I work a full time job and had a little time to do this write up. This is no guarantee that if you need help in the future that I will be able to help or even know how to help. Please make sure you understand that and are prepared to resolve your issue on your own.
thepolishguy said:
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
Okay - this is probably going to sound complicated but it is not that complicated...
First let's go over the easy version...
reboot into bootloader and...
fastboot flash system system.img
fastboot flash recovery recovery.img
So that's the easy and short version. Do that and you have restored your phone to stock without losing your app data.
Now the complicated part is whether not you know what to do with that information? In fastboot if you type...
fastboot devices
...it should return you serial number. If it does not then you do not have the proper drivers installed. Install Motorola Device Manager and this should solve the problem http://goo.gl/DiRvpE
Then of course you need the system.img and the recovery.img http://sbf.droid-developers.org/ghost_rcica/list.php
MAKE SURE YOU DOWNLAOD THE FILES FOR THE RIGHT PHONE OR YOU ARE HOSED
Once you download that file you will have to unzip it with something like 7zip or Winrar and when you do you will find those files. Then the files have to be copied to the "platform-tools" folder of your android sdk (or the folder where your fastboot.exe is).
Then you can open a command prompt from that folder with your device attached and...
adb devices
...should return a serial number
adb reboot bootloader
...should reboot into bootloader
fastboot devices
...should return a serial number
fastboot flash system system.img
...should flash the system...
fastboot flash recovery recovery.img
...should flash the recovery...
fastboot reboot
...should reboot the device and you will enter set up but your user data will be preserved.
I am always nervous about helping people because if they break something they like to blame someone. I work a full time job and had a little time to do this write up. This is no guarantee that if you need help in the future that I will be able to help or even know how to help. Please make sure you understand that and are prepared to resolve your issue on your own.
Click to expand...
Click to collapse
Just basic knowledge over here, but shouldn't that work for any carrier?
Sent from my Nexus 7 using xda app-developers app
Aarongauntt said:
Just basic knowledge over here, but shouldn't that work for any carrier?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes it should. Just got to make sure you grab the correct images for your carrier.
Aarongauntt said:
Just basic knowledge over here, but shouldn't that work for any carrier?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
should.
But I have a VZW MotoX and I dont want to jack anyone up.
As long as you are using the proper system and recovery. If you flash the ATT system to a VZW device you are going to have problems.
Aarongauntt said:
Just basic knowledge over here, but shouldn't that work for any carrier?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Worked perfect on my ATT Moto x
thepolishguy said:
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
Okay - this is probably going to sound complicated but it is not that complicated...
First let's go over the easy version...
reboot into bootloader and...
fastboot flash system system.img
fastboot flash recovery recovery.img
So that's the easy and short version. Do that and you have restored your phone to stock without losing your app data.
Now the complicated part is whether not you know what to do with that information? In fastboot if you type...
fastboot devices
...it should return you serial number. If it does not then you do not have the proper drivers installed. Install Motorola Device Manager and this should solve the problem http://goo.gl/DiRvpE
Then of course you need the system.img and the recovery.img http://sbf.droid-developers.org/ghost_rcica/list.php
MAKE SURE YOU DOWNLAOD THE FILES FOR THE RIGHT PHONE OR YOU ARE HOSED
Once you download that file you will have to unzip it with something like 7zip or Winrar and when you do you will find those files. Then the files have to be copied to the "platform-tools" folder of your android sdk (or the folder where your fastboot.exe is).
Then you can open a command prompt from that folder with your device attached and...
adb devices
...should return a serial number
adb reboot bootloader
...should reboot into bootloader
fastboot devices
...should return a serial number
fastboot flash system system.img
...should flash the system...
fastboot flash recovery recovery.img
...should flash the recovery...
fastboot reboot
...should reboot the device and you will enter set up but your user data will be preserved.
I am always nervous about helping people because if they break something they like to blame someone. I work a full time job and had a little time to do this write up. This is no guarantee that if you need help in the future that I will be able to help or even know how to help. Please make sure you understand that and are prepared to resolve your issue on your own.
Click to expand...
Click to collapse
This man deserves some props. Thanks for posting that.
Sent from my HTC One mini
thepolishguy said:
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
Okay - this is probably going to sound complicated but it is not that complicated...
First let's go over the easy version...
reboot into bootloader and...
fastboot flash system system.img
fastboot flash recovery recovery.img
So that's the easy and short version. Do that and you have restored your phone to stock without losing your app data.
Now the complicated part is whether not you know what to do with that information? In fastboot if you type...
fastboot devices
...it should return you serial number. If it does not then you do not have the proper drivers installed. Install Motorola Device Manager and this should solve the problem http://goo.gl/DiRvpE
Then of course you need the system.img and the recovery.img http://sbf.droid-developers.org/ghost_rcica/list.php
MAKE SURE YOU DOWNLAOD THE FILES FOR THE RIGHT PHONE OR YOU ARE HOSED
Once you download that file you will have to unzip it with something like 7zip or Winrar and when you do you will find those files. Then the files have to be copied to the "platform-tools" folder of your android sdk (or the folder where your fastboot.exe is).
Then you can open a command prompt from that folder with your device attached and...
adb devices
...should return a serial number
adb reboot bootloader
...should reboot into bootloader
fastboot devices
...should return a serial number
fastboot flash system system.img
...should flash the system...
fastboot flash recovery recovery.img
...should flash the recovery...
fastboot reboot
...should reboot the device and you will enter set up but your user data will be preserved.
I am always nervous about helping people because if they break something they like to blame someone. I work a full time job and had a little time to do this write up. This is no guarantee that if you need help in the future that I will be able to help or even know how to help. Please make sure you understand that and are prepared to resolve your issue on your own.
Click to expand...
Click to collapse
Thanks for this! It cleared up a whole bunch of things about rooting and locked/unlocked bootloaders for me that just hadn't "clicked" before.
Sent from my Moto X
thepolishguy said:
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
Okay - this is probably going to sound complicated but it is not that complicated...
First let's go over the easy version...
reboot into bootloader and...
fastboot flash system system.img
fastboot flash recovery recovery.img
So that's the easy and short version. Do that and you have restored your phone to stock without losing your app data.
Now the complicated part is whether not you know what to do with that information? In fastboot if you type...
fastboot devices
...it should return you serial number. If it does not then you do not have the proper drivers installed. Install Motorola Device Manager and this should solve the problem http://goo.gl/DiRvpE
Then of course you need the system.img and the recovery.img http://sbf.droid-developers.org/ghost_rcica/list.php
MAKE SURE YOU DOWNLAOD THE FILES FOR THE RIGHT PHONE OR YOU ARE HOSED
Once you download that file you will have to unzip it with something like 7zip or Winrar and when you do you will find those files. Then the files have to be copied to the "platform-tools" folder of your android sdk (or the folder where your fastboot.exe is).
Then you can open a command prompt from that folder with your device attached and...
adb devices
...should return a serial number
adb reboot bootloader
...should reboot into bootloader
fastboot devices
...should return a serial number
fastboot flash system system.img
...should flash the system...
fastboot flash recovery recovery.img
...should flash the recovery...
fastboot reboot
...should reboot the device and you will enter set up but your user data will be preserved.
I am always nervous about helping people because if they break something they like to blame someone. I work a full time job and had a little time to do this write up. This is no guarantee that if you need help in the future that I will be able to help or even know how to help. Please make sure you understand that and are prepared to resolve your issue on your own.
Click to expand...
Click to collapse
Thanks! This was very helpful. I got stuck in a bootloop from a rooted MotoX 4.2.2 whilst trying to accept the OTA to 4.4. I was able to erase the cache to stop the bootloop problem, but I wanted to accept the OTA. I followed this guide and it seemed to work.
For posterity, anyone on Win7 x64 might have had similar problems to me:
Code:
MX-17-57-X-1_CFC_1FF.xml>fastboot flash system system.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
sending sparse 'system' (777329 KB)...
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
OKAY [ 49.985s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
The solution is to use the mfastboot.exe linked from here: http://forum.xda-developers.com/showthread.php?t=2489249
Hope that helps someone trying to do this same thing.
arigi said:
Thanks! This was very helpful. I got stuck in a bootloop from a rooted MotoX 4.2.2 whilst trying to accept the OTA to 4.4. I was able to erase the cache to stop the bootloop problem, but I wanted to accept the OTA. I followed this guide and it seemed to work.
For posterity, anyone on Win7 x64 might have had similar problems to me:
Code:
MX-17-57-X-1_CFC_1FF.xml>fastboot flash system system.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
sending sparse 'system' (777329 KB)...
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
OKAY [ 49.985s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
The solution is to use the mfastboot.exe linked from here: http://forum.xda-developers.com/showthread.php?t=2489249
Hope that helps someone trying to do this same thing.
Click to expand...
Click to collapse
^^^^THIS^^^^
Thanks @arigi I added this to my original instructions.
I messed up the boot.img file on my new Nexus 6. Will someone that has the phone pull the boot.img from their phone for me? Google doesn't yet have the Factory image up yet, so I am hoping that someone can pull it for me, so I can get up and running quicker than waiting for the Factory image to be uploaded.
I would be eternally grateful. Thank you so much.
joelbon said:
I messed up the boot.img file on my new Nexus 6. Will someone that has the phone pull the boot.img from their phone for me? Google doesn't yet have the Factory image up yet, so I am hoping that someone can pull it for me, so I can get up and running quicker than waiting for the Factory image to be uploaded.
I would be eternally grateful. Thank you so much.
Click to expand...
Click to collapse
what do you need me to do to pull it? I'm assuming an adb command?
joelbon said:
I messed up the boot.img file on my new Nexus 6. Will someone that has the phone pull the boot.img from their phone for me? Google doesn't yet have the Factory image up yet, so I am hoping that someone can pull it for me, so I can get up and running quicker than waiting for the Factory image to be uploaded.
I would be eternally grateful. Thank you so much.
Click to expand...
Click to collapse
I also need this lol.
I'd be happy to help, but I can't figure out how to pull it off my of my device. I found an article describing it, but it doesn't work.
loggainsd said:
what do you need me to do to pull it? I'm assuming an adb command?
Click to expand...
Click to collapse
It should be "adb pull (folder location)boot.img
I don't know the location of the boot.img, though. Can anyone please provide the proper command and the location? Thank you very much.
mtpease said:
I'd be happy to help, but I can't figure out how to pull it off my of my device. I found an article describing it, but it doesn't work.
Click to expand...
Click to collapse
i'm looking into it as well. Thank you for responding in the first place.
---------- Post added at 03:02 PM ---------- Previous post was at 02:55 PM ----------
joelbon said:
It should be "adb pull (folder location)boot.img
I don't know the location of the boot.img, though. Can anyone please provide the proper command and the location? Thank you very much.
Click to expand...
Click to collapse
I'm not finding anything myself sadly. The only thing ive found with adb is "adb backup" but that may copy personal data that we dont need.
joelbon said:
I messed up the boot.img file on my new Nexus 6. Will someone that has the phone pull the boot.img from their phone for me? Google doesn't yet have the Factory image up yet, so I am hoping that someone can pull it for me, so I can get up and running quicker than waiting for the Factory image to be uploaded.
I would be eternally grateful. Thank you so much.
Click to expand...
Click to collapse
I am curious what you did to mess it up? Without factory images available, it's not wise to mess around too much. Just curious.
livinginkaos said:
I am curious what you did to mess it up? Without factory images available, it's not wise to mess around too much. Just curious.
Click to expand...
Click to collapse
i goofed and tried to flash a recovery that i thought was for the 6 and it hasnr started since lol.
You will need to pull it from the partition it's on. Maybe you can check /fstab.shamu or something to see where it is?
Something like this is what you'd wanna do;
dd if=/dev/block/mmcblk0p13 of=/sdcard/boot.img
Replacing if=/dev/block/mmcblk0p13 with if=<boot.img partition>
almost certain you need root to pull the boot.img i could b wrong though.
djkinetic said:
almost certain you need root to pull the boot.img i could b wrong though.
Click to expand...
Click to collapse
Looks like you're about right.
You can follow the path to /dev/block/platform/<msmsomethingmaybe>/by-name and it'll show you the symlinks for boot, recovery, etc. (You could use something like root explorer, or just a shell and do ls -l in the by-name directory). For example on the nexus 5 I'd see that recovery is mmcblk0p20 and boot is mmcblk0p19. Wherever boot is, that's the one you want to pull.
But it looks like you can't read any of that stuff unless you have root privileges (could do it from a recovery, if there is one), which begs the question - where da factory image at google?
bbedward said:
Looks like you're about right.
You can follow the path to /dev/block/platform/<msmsomethingmaybe>/by-name and it'll show you the symlinks for boot, recovery, etc. (You could use something like root explorer, or just a shell and do ls -l in the by-name directory). For example on the nexus 5 I'd see that recovery is mmcblk0p20 and boot is mmcblk0p19. Wherever boot is, that's the one you want to pull.
But it looks like you can't read any of that stuff unless you have root privileges (could do it from a recovery, if there is one), which begs the question - where da factory image at google?
Click to expand...
Click to collapse
rough, o well hopefully they release those images soon. Having my new brick is nice and all but having a phone would be even better lol
Could someone pull the system as well? System dump...
david279 said:
Could someone pull the system as well? System dump...
Click to expand...
Click to collapse
it looks like google has released the factory image
Factory Image is now live - https://developers.google.com/android/nexus/images
livinginkaos said:
Factory Image is now live - https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
having trouble getting it to flash though. I'm using minimal adb and fastboot.
ravath said:
having trouble getting it to flash though. I'm using minimal adb and fastboot.
Click to expand...
Click to collapse
Me as well. Take a look at my thread. The flash went well until the end when I got this message:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(1322,0xa0b121d4) malloc: *** mach_vm_map(size=1681272832) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1679592636 bytes
error: update package missing system.img
The package looks complete. Not sure what is missing.
Nucleonic said:
Me as well. Take a look at my thread. The flash went well until the end when I got this message:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(1322,0xa0b121d4) malloc: *** mach_vm_map(size=1681272832) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1679592636 bytes
error: update package missing system.img
The package looks complete. Not sure what is missing.
Click to expand...
Click to collapse
i got the same error!
I just tried performing this process manually. The flashing process seems to fail when this command gets executed: fastboot update image-shamu-lrx210.zip
You guys need to flash the imgs individually via command line
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.