Related
So to change the splash screen of your android phone 1st you need to Set up ADB if you already haven't..
Set up ADB from Here:
http://droidination.wordpress.com/2012/02/01/how-to-set-up-adb/
Now after setting up the ADB you need to Follow these instructionsto change your splash screen:
1.First you need to copy a cmd.exe file to Heimdall’s Folder like this
2.Now put your phone into download mode and open the file ZADIG in the drivers folder.
3.Install The drivers now
4.Now open Cmd and type the foll command:
heimdall flash –param /location/of/param.lfs
5.Now your phone will be rebooted and you will see the Download mode logo instead of your orignal logo
6.Now create your own logo using Photoshop or any other Photo Editor and make sure its in the ratio 480×800..
7.put the logo file in the platform tools folder in android sdk..
8.Paste and open the cmd in the platform tools folder..
9.Put your phone in download mode and Connect it to the computer..
10.Type in the following command in the CMD window:
adb push Logo.jpg /mnt/.lfs
adb reboot
11.You Will Now see your logo file Instead of the orignal one..
You Can Check out the orignal Post from here:
http://droidination.wordpress.com/2...e-splash-screen-of-your-galaxy-s-easiest-way/
Click the thanks button if i helped..
so...can I just make a logo.jpg and put into mnt/.lfs by root explorer?
(btw,and its funny to see i9003 and docomo logos in .lfs file)
Yes 1st u have to make a logo.jpg of resolution 480*800 only..
u can make it using Photoshop..
Then just open terminal emulator in your GTi9000.. if u dont have it download it from the android market..
Copy the logo.jpg file in the root of your SDCARD..
and type the following command:
"cp /mnt/sdcard/logo.jpg /mnt/.lfs" [Without Quotations]
Reboot your phone now..
now you will see your logo.jpg file as the boot image/splash screen..
It would not replace it by root explorer.."
Yes i was also shocked to see the i9003 and docomo logos..
click the thanks button if i helped..
I just made the splash screen by removing samsung logo from the original
(hey samsung you have made a big enough logo on our phones! no need to put one on boot!)
saved as /mnt/sdcard/logo.jpg 800×480 of course
opened terminal emulator, typed
Code:
cp /mnt/sdcard/logo.jpg /mnt/.lfs
and get the following code without logo.jpg replaced
Code:
cp: can't create '/mnt/.lfs/logo.jpg': File exists
also tried copying with root explorer, but it also turns out to be the original image
(even deleteing the original and put new logo.jpg to /mnt/.lfs)
(of course I have a backup of original image)
will this be something wrong with busybox?
EDIT:it seems everything that gets into /.lfs can't be deleted by RE or terminal emulator. weird...
First u have to type su to enable superuser access then type that command..
make sure u have busybox installed..!! if not just download the terminal IDE app from market then do the same thing this will work 4 sure..!!
To be clear, I have root, busybox 1.19.3 , superuser permitted terminal IDE,
typed su this time but still no luck.
(and when I tried to rm a accidentally copied jpg from /mnt/.lfs , terminal IDE even says 'operation not permitted' . WHAT? I have already "su"ed!)
Doubt that I must go through download mode in order to write in movinand.
Anyway thanks for providing all the info on splash screen replacement. Cheers.
playerzking said:
To be clear, I have root, busybox 1.19.3 , superuser permitted terminal IDE,
typed su this time but still no luck.
(and when I tried to rm a accidentally copied jpg from /mnt/.lfs , terminal IDE even says 'operation not permitted' . WHAT? I have already "su"ed!)
Doubt that I must go through download mode in order to write in movinand.
Anyway thanks for providing all the info on splash screen replacement. Cheers.
Click to expand...
Click to collapse
I second that. I am root and mounted /system as rw, it does not allow me to rm or even mv the /mnt/.lfs/logo.jpg to anywhere. Even root explorer cannot rename the default logo.jpg. Operation not permitted is the error I get. I am using gingerbread 2.3.6 GINGERBREAD.JPKPE build. Dont know if they added some second layer of protection...
See my previous post before in post#2
This is a simple batch file using ADB..
With this you can use ADB to manage your file or APK , Backup, Push Your File to device, or pull file from device..
ADB Work on Stand by Mode (Home Screen) or in Recovery Mode, just set it up..
Extract ADBTOOLSv1.0.1.zip and you will find :
command.bat : Windows Batch Command
_BACKUP_OUT : folder where your backup process done and made
_FLASHING_OUT:
folder for flashing your :
kernel (place your boot.img here)
recovery (place your recovery.img here),
modem (place your modem.bin here)--only for gt p7300
_MODDING_FILE: Folder where your file were created by PULL process
Folder where file for PUSH process should be here
_BATCH_INSTALL : place your APK here for batch install
tools: ADB.exe and busybox binary
success_APK : A folder created for All apk from _BATCH_INSTALL move here after instalation.
Click to expand...
Click to collapse
Notes:
ADB can access all file from device from CWM Recovery, especially CWMR 5.5.0.4
ALL you need to do is:
From Recovery menu, you need to mount /data and /system for ADB working..
THEN, From Command Prompt set ADB Mode to "recovery".(This Batch File set ADB mode to "Home Screen" by default)
So when you use ADB from Online device ( I mean a stand by device).. you dont need to change ADB Mode..
After you set up, you can use ADB as you like..
Code:
=============================================================================
:::: ADB TOOLS FOR GT P7300 and P7310 by suwandiapr
-----------------------------------------------------------------------------
| [*] Before use read this:
| --make sure you have installed adb drivers for your device
| --enable "USB DEBUGGING"
| from (Menu\Settings\Applications\Development)
| --enable "UNKNOWN SOURCES"
| from (Menu\Settings\Applications)
| --increase screen timeout to 10 minutes
| --connect USB cable to PHONE and then connect to PC
| --MAKE SURE YOU HAVE A ROOTED DEVICE AND BUSYBOX
| --Place the right file in the right folder
| --Some feature like Flashing need more tester..so please be aware
| --If you use adb recovery feature, set ADB Mode to recovery
| mount /data and /system from your device recovery
| --If you use adb from homescreen, set ADB Mode to HomeScreen
| --All you Do is your own Risk, use with carefull
-----------------------------------------------------------------------------
****Turn on the screen and allow superuser permission when asked!****
_____________________________________________________________________________
| Current MODDING FILE: NONE | ADB MODE :HomeScreen | sdcard path: /sdcard/|
=============================================================================
:::: ADB PULL ::::
=============================================================================
0 Pulling file from /data ( see result in _MODDING_FILE)
1 Pulling file from /system partition ( see result in _MODDING_FILE)
2 Pulling file from SDcard ( see result in _MODDING_FILE)
3 Backup recovery ( see result in _BACKUP_OUT)
4 Backup Kernel ( see result in _BACKUP_OUT)
5 Backup modem (for P7300 only-see result in _BACKUP_OUT)
6 Backup /system (tar format-see result in _BACKUP_OUT)
7 Backup /efs (tar and .img format-see result in _BACKUP_OUT)
8 Backup APK from /data/app (tar format-see result in _BACKUP_OUT)
=============================================================================
:::: ADB PUSH ::::
=============================================================================
9 Pushing file to /data ( from _MODDING_FILE to device)
10 Pushing file to /system ( from _MODDING_FILE to device)
11 Flashing recovery ( from _FLASHING_OUT to device)
12 Flashing Kernel ( from _FLASHING_OUT to device)
13 Flashing modem for GT P7300 ( from _FLASHING_OUT to device)
=============================================================================
:::: Setting ::::
=============================================================================
14 Set current working File ( for PUSH and PULL )
15 Install busybox on device (need root)
16 Set ADB mode (if you on recovery mode)
17 Install apk ( from _MODDING_FILE to device)
18 Install batch apk ( from _BATCH_INSTALL to device)
=============================================================================
:::: Reboot Menu ::::
=============================================================================
19 Reboot System
20 Boot Into Recovery
21 Reboot Bootloader
22 Quit
My previous post
inspiration from congox case
when you got a problem with bootlop and you forget make a nandroid backup
only have file from other ROM with flashable.zip and need to push the file from your computer to device
you have a recovery support with mount /system and mount /data (tested on CWM 5.5.0.4 and overcome CWM 5.1.2.6) and you can enter this menu while bootloop happen..
STEP 1 : MANUAL
Connect your device with computer
From device, Go to recovery - mounts and storage - mount /system and mount /data
From your computer go to adb terminal and type this
Code:
adb shell "ls /data/media/"
If you can see list of file from your device sdcard, so you make adb work for your device ..
Place your zip file on your path, says on C://backup.zip and you want to copy the file to /sdcard/download/ and type this code
Code:
adb push backup.zip /data/media/download/.
wait for copying progress done..
After you done with moving file to device sdcard, check content of your sdcard with this code
Code:
adb shell "ls /data/media/download/"
When you found your file from list, you can flash backup.zip from recovery
STEP 2 : WINDOWS BATCH FILE
I made a simple Batch File for windows (sorry i dont have MAC or LINUX distro) , this file will make a folder with name "emergency" in SDCARD and with your files inside that.
Extract the FLASHER.rar somewhere on your Local folder,example: on your " Desktop" Folder
in folder "FLASHER" you will find runme.bat and folder "files"
Rename your file ((flashable.zip files you want to send through ADB) to "backup.zip" and then Put your file into this path /FLASHER/files/myfiles/ (just replace the existing "backup.zip" with files from yours)
Connect your tab with Computer
Reboot into Recovery Menu from your device
From menu Mounts and Storage choose mount /system and /data
From your Computer go To Folder flasher and klik runme.bat
Follow the instruction on window untill copying process done and device reboot to recovery again (copying process will take a minutes depend on your file size)
Now you can flash a emergency ROM from recovery
Window instruction
Code:
-----------------------------------------------------------------------------
ADB EMERGENCY COPYING TOOL for TAB 8,9
created by SUWANDIAPR
-----------------------------------------------------------------------------
[*] This script will:
(1) COPY YOUR FILE FROM COMPUTER TO SDCARD/emergency/*
(2) CHECKING YOUR CONNECTED DEVICE DIRECTORY
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) make sure u have installed CWM 5.5.0.4 ON YOUR DEVICE
(3) connect USB cable to PHONE and then connect to PC
(4) Rename your Flashable .zip file with "backup.zip"
and place inside "myfiles" folder on your Computer
(5) from Recovery Menu, Choose "Mounts and storage" then
-mount /system and -mount /data
(6) CONNECT YOUR TAB WITH PC WHILE ON RECOVERY MENU
---------------------------------------------------------------
CONFIRM ALL ABOVE
Sorry for my Bad english, if there is somebody want to correct every words i use , im very welcome and will change with the proper words and sentence..
Hope this help someone..
Nice guide, thanks!!
I needed some help with mounting the system using adb through a batch file.
I use this command
adb -d shell mount -o remount rw /system
But the mounting fails (I have a rooted phone )
pleas help me I know this is off topic
2 possible reasons for this command to fail:
- /default.prop (on the phone) contains the following line: "ro.secure=1". Then you need another boot.img (in fact just a modified ramdisk). look for "unpack-bootimg.pl" or "unpackbootimage" you may find a guide how to do this manually (not too easy). A rooted kernel would also do the trick.
you can check your default prob with this command "adb shell cat /default.prop".
- in some cases mount requires more parameters. try "adb shell mount" and look for the line containing "/system". In front of system is the "device-name". in my case the mount command would look like this:
mount -o remount,rw /block/dev/mmcblk0p24 /system
hope this helps and sorry for answering off-topic questions....
nail16 said:
I needed some help with mounting the system using adb through a batch file.
I use this command
adb -d shell mount -o remount rw /system
But the mounting fails (I have a rooted phone )
pleas help me I know this is off topic
Click to expand...
Click to collapse
you can use busybox and call the binary from the shell
i assume that your device in normal mode ( in home screen)..
here some example..
Code:
su
adb push busybox /tmp/.
adb shell "chmod 755 /tmp/busybox"
adb shell "tmp/busybox mount -o remount,rw /system"
after you type "su" superuser will prompt a request, choose "allow".
glitschi667 said:
2 possible reasons for this command to fail:
- /default.prop (on the phone) contains the following line: "ro.secure=1". Then you need another boot.img (in fact just a modified ramdisk). look for "unpack-bootimg.pl" or "unpackbootimage" you may find a guide how to do this manually (not too easy). A rooted kernel would also do the trick.
you can check your default prob with this command "adb shell cat /default.prop".
- in some cases mount requires more parameters. try "adb shell mount" and look for the line containing "/system". In front of system is the "device-name". in my case the mount command would look like this:
mount -o remount,rw /block/dev/mmcblk0p24 /system
hope this helps and sorry for answering off-topic questions....
Click to expand...
Click to collapse
yes you right glistchi, samsung lock adb root on new firmware on my SG- Note..
And make me flash an older firmware for rooting..
new update
Never mind, got it to work
i want to push same file in data system (/data/data) but my tab is not root. can i??
if from cwm recovery, yes you can.. if from stand by mode (home screen) the answer is no... you need root to make it happen..
i got this error
please help
So, I've been trying to force over the 4.2 update to my N7 with adb. And every time I try to sideload the update, I get "adb cann't ready sideload"
I don't understand why it won't work. Every other adb command works fine. I'm on rev. 21 for sdk tools and 16 for platform tools. I literally just downloaded the SDK.
Any ideas?
UpsideDownAce said:
So, I've been trying to force over the 4.2 update to my N7 with adb. And every time I try to sideload the update, I get "adb cann't ready sideload"
I don't understand why it won't work. Every other adb command works fine. I'm on rev. 21 for sdk tools and 16 for platform tools. I literally just downloaded the SDK.
Any ideas?
Click to expand...
Click to collapse
I've been wondering the same thing.... No one seems to know or care to help. Bump this post...
uncleswoop said:
I've been wondering the same thing.... No one seems to know or care to help. Bump this post...
Click to expand...
Click to collapse
Just to be sure, you've apply sideload from adb in the recovery, correct?
ducatic said:
Just to be sure, you've apply sideload from adb in the recovery, correct?
Click to expand...
Click to collapse
I'm in the same boat! I tried, today, several times to sideload the update but I'm constantly getting the cannot read sideload error message. I guess I'm off to other sites to see what the fix is.
I had this problem too, but solved it this way:
Place the file you're trying to sideload is in the same adb directory, f.i. C:\Android
And when in the CMD window, change the active directory to this directory before you type: adb sideload [name of file]
So:
- run CMD window
- change your active directory to adb C:\Android
Code:
cd\
cd android
- type:
Code:
adb devices
(List of devices should indicate a number of the connected device)
- type:
Code:
adb sideload [name of file]
YES! i have found the solution. i just registered to share it to anyone with the same problem. i spend HOURS and HOURS, literally sweat and frustation like i've never experienced before to update this POS. i was ready to smash my one week old Nexus 7.
the solution is so simple and stupid that i want to smash my forehead on my keyboard.
i was using this video as a guide to manually update the N7 youtube /watch?v=iQhyerPfGes
what it doesn't say is that you DON'T HAVE TO UNZIP THE FIRMWARE!!!
You have to issue the command from the platform-tools folder (or the directory in which adb.exe resides). Right-click n the folder window and choose "open command prompt here." Then type
adb sideload 094f6629314a.signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
Click to expand...
Click to collapse
remember, don't unzip the firmware
my Nexus 7 still doesn't finish the update because it say something about an error, but that's another problem
but at least i'm not getting "cannot read sideload" anymore :laugh:
I might be just an idiot but why are you guys trying to SideLoad a system update?
AFAIK... sideload is merely to install apps into your rom that Jellybean or the Playstore doesn't like.
I think you guys want to use "ADB Fastboot" commands instead. Get a guide before you attempt to do this though. I used Wugs Toolkit to install the bootloader from 4.2.2 update.
fede01_8 said:
what it doesn't say is that you DON'T HAVE TO UNZIP THE FIRMWARE!!!
Click to expand...
Click to collapse
:laugh: true
For clarity:
- adb sideload can used for installing zip updates from PC, as an alternative for using the ROM/recovery manager on your tablet/phone.
Code:
adb sideload update.zip
- fastboot flash is used for installing img files to a specific partition (boot, recovery, system)
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fac851 said:
I had this problem too, but solved it this way:
Place the file you're trying to sideload is in the same adb directory, f.i. C:\Android
And when in the CMD window, change the active directory to this directory before you type: adb sideload [name of file]
So:
- run CMD window
- change your active directory to adb C:\Android
Code:
cd\
cd android
- type:
Code:
adb devices
(List of devices should indicate a number of the connected device)
- type:
Code:
adb sideload [name of file]
Click to expand...
Click to collapse
Thank you!!! Spending hours trying to figure it out, so simple. Although not sure why the toolkit didn't work, but using CMD did work.
fac851 said:
I had this problem too, but solved it this way:
Place the file you're trying to sideload is in the same adb directory, f.i. C:\Android
And when in the CMD window, change the active directory to this directory before you type: adb sideload [name of file]
So:
- run CMD window
- change your active directory to adb C:\Android
Code:
cd\
cd android
- type:
Code:
adb devices
(List of devices should indicate a number of the connected device)
- type:
Code:
adb sideload [name of file]
Click to expand...
Click to collapse
fede01_8 said:
YES! i have found the solution. i just registered to share it to anyone with the same problem. i spend HOURS and HOURS, literally sweat and frustation like i've never experienced before to update this POS. i was ready to smash my one week old Nexus 7.
the solution is so simple and stupid that i want to smash my forehead on my keyboard.
i was using this video as a guide to manually update the N7 youtube /watch?v=iQhyerPfGes
what it doesn't say is that you DON'T HAVE TO UNZIP THE FIRMWARE!!!
You have to issue the command from the platform-tools folder (or the directory in which adb.exe resides). Right-click n the folder window and choose "open command prompt here." Then type
remember, don't unzip the firmware
my Nexus 7 still doesn't finish the update because it say something about an error, but that's another problem
but at least i'm not getting "cannot read sideload" anymore :laugh:
Click to expand...
Click to collapse
I've tried both of these, I still get the cannot read sideload FML why is this keep happening? :crying:
teaclarke said:
I've tried both of these, I still get the cannot read sideload FML why is this keep happening? :crying:
Click to expand...
Click to collapse
I was getting that message because my zip file already was a zip file and I named the file update.zip. Had to remove .zip from the file name then it worked.
brandnewyc said:
I was getting that message because my zip file already was a zip file and I named the file update.zip. Had to remove .zip from the file name then it worked.
Click to expand...
Click to collapse
This is what got me on the right trail. I opened the command prompt, navigated to the correct folder, used the sideload command and copied the name of the update file into the command prompt window, but it wasn't until I appended it with the .zip extension that it finally worked.:victory:
Hey guys! I don't have the sideload problem anymore, but, I get this error. cannot read '(name of file).zip'
I am either really dumb or this isn't working! I have it connected to adb device number and all working fine. I have the zip in platforms-tools cmd window opened etc. when i go to adb sideload and then top of cmd window edit paste the name of the file add .zip and it says can not read file!
Please help!!
Same problem...fixed
I had the same cannot read sideload problem.
The problem was when I renamed the update package (so i don't have to type in the ridiculously long file name), i renamed it as "kk.zip".
Because this was done in windows, the file system recognized it as "kk.zip.zip".
Just rename the file without ".zip" (just "kk")
then try again - in my example: adb sideload kk.zip
it works~
jihoon526 said:
I had the same cannot read sideload problem.
The problem was when I renamed the update package (so i don't have to type in the ridiculously long file name), i renamed it as "kk.zip".
Because this was done in windows, the file system recognized it as "kk.zip.zip".
Just rename the file without ".zip" (just "kk")
then try again - in my example: adb sideload kk.zip
it works~
Click to expand...
Click to collapse
So I had a similar experience. when I tried to use
Code:
adb push
, it would say error:closed. This was weird since the device showed up when I ran
Code:
adb devices
.
When I tried to do
Code:
adb sideload xxx.zip
I would get the
Code:
cannot read sideload
error. I have Windows set to show file extensions, but decided to rename the file and remove the extension. Then I renamed it again and re-added the extension. After that, sideload worked like a charm. I have no idea what changed (if anything), but it worked for me!
Fix
For me all that worked was using an aosp for the sideload, and then copying the real rom once I had android booted.
hkleiner said:
For me all that worked was using an aosp for the sideload, and then copying the real rom once I had android booted.
Click to expand...
Click to collapse
are you on the same directory as your file?
teaclarke said:
I've tried both of these, I still get the cannot read sideload FML why is this keep happening? :crying:
Click to expand...
Click to collapse
Try addind ".zip" at the end of the file name in CMD. So if the name in the directory is ROM, type into cmd "adb sideload ROM.zip"
DigitalOSH said:
So I had a similar experience. when I tried to use
Code:
adb push
, it would say error:closed. This was weird since the device showed up when I ran
Code:
adb devices
.
When I tried to do
Code:
adb sideload xxx.zip
I would get the
Code:
cannot read sideload
error. I have Windows set to show file extensions, but decided to rename the file and remove the extension. Then I renamed it again and re-added the extension. After that, sideload worked like a charm. I have no idea what changed (if anything), but it worked for me!
Click to expand...
Click to collapse
oddly this helped me a lot with another device. i was having the exact same problem and found this topic in searching for a solution. but after removing the extension, renaming, then renaming and re-adding the extension it worked. i also had to type adb sideload fielanme.zip.zip to get it working.
Enter recovery and sideload CN ROM
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-CN-3_2_23_182.zip
To return to WW rom its a litle complicated becouse when you try to sideloade ww version it gives error for not having inough space. So you need to give command to recovery to instal zip from location you want.
1. root with rootzenfone.apk
http://23pin.logdown.com/posts/230216-root-rootzenfone-14r
2. turn on usb debuging
3. download ww rom and rename it update.zip
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-WW-3_2_23_182.zip
4. download es or some other file menager that has root access.
5. go to / (root) and manualy copy update.zip to /data folder
6. Download https://drive.google.com/file/d/0B6...drivesdk&resourcekey=0-W0btfSuQS9kq5iNNsCuWgQ and copy command file to cache/recovery folder
6. open ADB and type line by line:
adb remount
adb shell
su
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/data/update.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
after this reboot to recovery and automaticly instal ww rom
This is fantastic, and smart move making a new thread...
Thanks,
sutekh137
And if you're not bricked, but can't update from the old software version. Copy and paste the commands in terminal emulator to force the update. Worked out great. Thanks for the tip.
slayeralive said:
Enter recovery and sideload CN ROM
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-CN-3_2_23_182.zip
To return to WW rom its a litle complicated becouse when you try to sideloade ww version it gives error for not having inough space. So you need to give command to recovery to instal zip from location you want.
1. root with rootzenfone.apk
http://23pin.logdown.com/posts/230216-root-rootzenfone-14r
2. turn on usb debuging
3. download ww rom and rename it update.zip
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-WW-3_2_23_182.zip
4. download es or some other file menager that has root access.
5. go to / (root) and manualy copy update.zip to /data folder
6. open ADB and type line by line:
adb remount
adb shell
su
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/data/update.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
after this your device will reboot to recovery and automaticly instal ww rom
Click to expand...
Click to collapse
I'm having a lil problem here. Could you elaborate a little more, like in /root. <-- What does this mean? Do i write root or am I to go to root of the tablet's memory? And should I use adb on my PC connecting by usb cable to the tablet? I'm having a little problem understanding some of the steps.
(Remember, it's my sex life that it's in danger here)!
bravesoul said:
I'm having a lil problem here. Could you elaborate a little more, like in /root. <-- What does this mean? Do i write root or am I to go to root of the tablet's memory? And should I use adb on my PC connecting by usb cable to the tablet? I'm having a little problem understanding some of the steps.
(Remember, it's my sex life that it's in danger here)!
Click to expand...
Click to collapse
I would assume root of the device itself as the next step is to put update.zip in /data
(Get me in on the fun. I helped. )
I tried terminal emulator to write adb remount, but just after I wrote it, it gives me an error.
I've put the the update.zip in data folder. but there's like two data folders in my tablet's memory root. Do I put it after mnt or before (I,m using root browser v2.3)? Like in the real root of everything? Another question. Must I use the zip inside another zip of the asus ww rom, or just the unzipped zip file. (LOL, confusing, i know).
(I dunno JerBear, they're very peculiar about what/who they blow)!!
bravesoul said:
I tried terminal emulator to write adb remount, but just after I wrote it, it gives me an error.
I've put the the update.zip in data folder. but there's like two data folders in my tab memory's root. Do I put it after mnt or before?
Click to expand...
Click to collapse
They should be symlinked to the same thing. Let me check...
Well. I only have the data folder that's in the root. Peculiar.
As for the zip file question, go for trial and error. Worst case scenario recovery rejects it.
(We'll work around it )
This is what I get in terminal emulator:
Me176c
bravesoul said:
This is what I get in terminal emulator:
Click to expand...
Click to collapse
You need that command only when you are using ADB over PC
Thanks, but I have other issues.
What zip file should I use? The original we download from ASUS or the zip file inside the original.
JerBear told me to try one or another, but he doesn't know I'm in a place where Internet speed is like 50 Kbps... Which means it takes about two hours to download the original file.
However,(and this will sound strange), if anyone can give me the original names of both the original .182 zip file and the one inside the original, I think I can use a previously (and renamed) downloaded .182 ROM.
Me176c
bravesoul said:
Thanks, but I have other issues.
What zip file should I use? The original we download from ASUS or the zip file inside the original.
JerBear told me to try one or another, but he doesn't know I'm in a place where Internet speed is like 50 Kbps... Which means it takes about two hours to download the original file.
However,(and this will sound strange), if anyone can give me the original names of both the original .182 zip file and the one inside the original, I think I can use a previously (and renamed) downloaded .182 ROM.
Click to expand...
Click to collapse
Use zip inside original.
slayeralive said:
Use zip inside original.
Click to expand...
Click to collapse
So to be clear. I'll use ES File Manager to rename the file (update.zip) and copyit into Root->Data->Turn off the tablet and on again->enter into recovery->in PC I'll use adb->type adb remount and other commands->The tablet will reboot and update into the WW.182 ROM.
Right?
Me176c
bravesoul said:
So to be clear. I'll use ES File Manager to rename the file (update.zip) and copyit into Root->Data->Turn off the tablet and on again->enter into recovery->in PC I'll use adb->type adb remount and other commands->The tablet will reboot and update into the WW.182 ROM.
Right?
Click to expand...
Click to collapse
No man can you read? Do not turn of. Connect to pc and use adb or use terminal. If you are using terminal skip adb commands and start at "su" command. After typing last command it will automaticly reboot to recovery and start instalation than just wait...
slayeralive said:
No man can you read? Do not turn of. Connect to pc and use adb or use terminal. If you are using terminal skip adb commands and start at "su" command. After typing last command it will automaticly reboot to recovery and start instalation than just wait...
Click to expand...
Click to collapse
Ok, ok. Don't get your intelligence in a twist.
Thanks for helping me with my absurd noobiness. :good:
bravesoul said:
Ok, ok. Don't get your intelligence in a twist.
Thanks for helping me with my absurd noobiness. :good:
Click to expand...
Click to collapse
Have fun with your "reward"
Not yet I'm afraid. I've tried via terminal emulator and indeed it goes to recovery, but afterwards, it just reboots into the CN version untouched.
(And JerBear, i'm kidding about the chicks...They aren't 3. It's only one).
Try again you did somethin wrong
Folow the steps download->extract->rename to update.zip->copy to /data folder->type in terminal
bravesoul said:
Not yet I'm afraid. I've tried via terminal emulator and indeed it goes to recovery, but afterwards, it just reboots into the CN version untouched.
(And JerBear, i'm kidding about the chicks...They aren't 3. It's only one).
Click to expand...
Click to collapse
If you missd or typed wrong one character in terminal it wont work. Try again.
bravesoul said:
Not yet I'm afraid. I've tried via terminal emulator and indeed it goes to recovery, but afterwards, it just reboots into the CN version untouched.
(And JerBear, i'm kidding about the chicks...They aren't 3. It's only one).
Click to expand...
Click to collapse
From the top, you must be rooted and you must know what that is.
I used the file from inside the download. I believe it has user in the name.
Rename this file to be update.zip.
Place update.zip into the data folder in the root directory, ie. root/data/update.zip.
Back out of that when it's finished and find the original post with the instructions, touch it and touch the message symbol like you are going to reply.
Copy all of the commands from after su, to the end.
Open terminal emulator, Type su and give root permission at the prompt, touch and paste, you should see what you copied, if you don't, do it again. If you do, touch enter and the process will begin.
Do not do anything until the device reboots COMPLETELY. It will go through several reboots, just wait.
Viola, you will be updated.
GOT TROUBLE WHILE INSTALLING A RECOVERY? YOU MAY HAVE FLASHED A PREROOTED ZIP WITH RECOVERY BUT LOST THE RECOVERY? GET A WORKING TWRP RECOVERY AFTER 2 MINUTES ON YOUR XPERIA Z2 D6503/D6502:
Instructions:
open any root explorer app like ES FILE MANAGER
Delete /system/etc/mm_twrp_recovery folder
Go to /system/bin/ folder
Look for the "chargemon.stock" file - If it's present, delete this one: chargemon - and now, rename the chargemon.stock to chargemon
Look for the "taimport.stock" file - If it's present, delete this one: taimport - and now, rename the taimport.stock to taimport
Reboot
download "recovery fix.zip" from mega.nz
extract the file and run "adbrecoveryfix.exe" the .exe file will install some needed files (normally into C:\Minimal ADB and Fastboot\ )
copy the files from the folder "RECOVERY FILES" into the "Minimal ADB and Fastboot" Folder
connect your xperia with the pc
open the "Minimal ADB and Fastboot" folder and then SHIFT+RIGHT CLICK to open a command window
now type:
adb shell
su root
mount -o remount,rw /system
exit
exit
install.bat
Click to expand...
Click to collapse
don´t forget to press enter after "adb shell", "su root" and so on!
now your recovery will install again without any errors!
DOWNLOAD:
https://mega.nz/#!NoVSlK5T!CPJDueW8nXiHEv-jjqo7U-CrrEa1nE2JTE8mWjn3NEs
YOU HAVEN`T INSTALL ANDROID MARSHMALLOW YET BECAUSE YOU WANT TO KEEP ROOT RIGHT, XPOSED AND THE RECOVERY?
THEN CHECK OUT THIS THREAT
http://forum.xda-developers.com/xper...7#post66513485
Another simple Method: thanks @meer_mortal
Deleted folders and rename chargemon etc
Plugged phone into computer with dev settings, debugging etc
Open root explorer to make / -RW
Run install.bat with CMD
Boom! MM with TWRP
To get in into recovery reboot press down after green LED
Click to expand...
Click to collapse
THIS WORKS WITH ALL XPERIA MARSHMALLOW BUILD NUMBERS SUCH AS THE NEW VERSION 23.5.A.1.291
enjoy the fix
DOWNLOAD
MEGA.nz https://mega.nz/#!NoVSlK5T!CPJDueW8nXiHEv-jjqo7U-CrrEa1nE2JTE8mWjn3NEs
FOR A PRERROTED 23.5.A.1.291 FOR YOUR XPERIA Z2 CHECK OUT THIS LINK:
http://forum.xda-developers.com/xperia-z2/general/sony-z2-d6503-prerooted-customized-au-t3432625
FOR A PREROOTED 23.5.A.0.575 FOR YOUR XPERIA Z2 CHECK OUT THIS LINK:
http://forum.xda-developers.com/xperia-z2/general/z2-pre-rooted-twrp-3-0-0-2-xposed-t3390498
THESE TWO PREROOTED ANDROID MARSHMALLOW VERSIONS ARE FOR LOCKED AND UNLOCKED BOOTLOADER.
thanks @rakeshbro
thanks @freaky2xd