Related
Good news everyone!
Here is the rooting method for 2.3.6 ROM's, that I decided to call PreinstalameEsta (roughly translated to PreinstallThis)
This method doesn't change any user data. The sbf that is flashed during the procedure only modifies the /preinstall partition (CG66), in which exists a security problem that I exploited to get the root access.
Files needed:
PreinstalameEsta's Files: https://github.com/downloads/nicofff/preinstalameEsta/nicofff-preinstalameEsta-v0.9-4-gce4da6b.zip
ADB, RSD lite, drivers, etc.
Procedure:
1) Unzip the PreinstalameEsta's Files
2) Plug your phone, and switch on USB debugging
3) Run the rootMM2_en.bat file (or runme_en.sh on linux)
3) When asked to flash the new sbf file, reboot the phone into bootloader mode (turn on while pressing the up arrow on the keyboard)
4) Open RSD lite, select the fixed.sbf file and flash it into the phone. (if on linux, use the sbf_flash app included)
5) When it finishes flashing, and reboots, continue executing the rootMM2.bat file.
6) After a few reboots more, the batch file will finish and the phone should be rooted.
In case you want to contribute code, translations, etc.:
https://github.com/nicofff/preinstalameEsta
For an explanation (in spanish) on how i found the root, check here:
http://nicofff.blogspot.com.ar/2012/06/historia-de-un-rooteo-y-todo-lo-que.html
Original Thread on GA: http://www.grupoandroid.com/topic/49338-root-ginger-de-personal-claro-movistar-vivo-y-tigoretail/
Happy Rooting
Nicofff
Update 05/08/2012:
I got my phone stolen last night (In San Telmo, Buenos Aires). Just in case it ends in the hands of a good soul and they happen to come here, i humbly ask them to return it.
The way to identify it: Under the battery, there is a sticker from AFIP that is slightly burnt.
Thanks
Hello my friend, I made all steps and I couldn't make it
I have milestone 2 (brazilian version)
45.2.2710.A953.Latam.en.01 (retail R01)
I think I'll be forever with this rom !
Any idea ?!?!
Thanks !!
Gauzo said:
Hello my friend, I made all steps and I couldn't make it
I have milestone 2 (brazilian version)
45.2.2710.A953.Latam.en.01 (retail R01)
I think I'll be forever with this rom !
Any idea ?!?!
Thanks !!
Click to expand...
Click to collapse
Try again.. All people in Argentina could do it using this tutorial.. Just look at the original thread
Sorry for my english
Gauzo said:
Hello my friend, I made all steps and I couldn't make it
I have milestone 2 (brazilian version)
45.2.2710.A953.Latam.en.01 (retail R01)
I think I'll be forever with this rom !
Any idea ?!?!
Thanks !!
Click to expand...
Click to collapse
What errors did you get?
Paste the output from the script and from RSDlite
argentina personal
Did it work on argentina personal ? :crying:
makipn said:
Did it work on argentina personal ? :crying:
Click to expand...
Click to collapse
Yes it does! 300 Downloads from GrupoAndroid and counting!
I flashed fixed.sbf with rsdlite, everything was fine... after that when I tried to use the root_mm2_en, it was saying that couldn't change, like other roots (doomlord v4, superoneclick,...)
What can I do ? Later I'll post my error
Thanks a lot !
gb vivo 2.3.6 & windows 7
when i run rootMM2-en.bat it opens a window where there is written " press a button to continue" when i press it, it start to work and appers this message :
0 KB/s (105 bytes in 1.000s)
Without closing this window, shutdown the phone
and restart it in bootloader mode (power + UP key in the keyboard)
Once inside the bootloader mode, flash the fixed.sbf from rsdlite
after it restarts, enable USB debugging and press enter to continue...
Premere un tasto per continuare . . .
Waiting for Phone
Syntax error: Unterminated quoted string
than the phone switch off by itself and i had turn it on in bootloader mode, i have flashed the fixed sbf and than the it show me this message
remount failed: Operation not permitted
failed to copy 'su' to '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
link failed Read-only file system
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
/sbin/hotplug > /sys/kernel/uevent_helper
The End
is it a bug or i had make a mistake ?
sminatore said:
is it a bug or i had make a mistake ?
Click to expand...
Click to collapse
It's a bug because of the translation... I've found it:
Code:
adb shell "echo 'doing something on adb, otherwise it doesn't work'"
Should change to
Code:
adb shell "echo 'doing something on adb, otherwise it does not work'"
@nicofff the ' in "don't" caused a syntax error
sminatore said:
gb vivo 2.3.6 & windows 7
when i run rootMM2-en.bat it opens a window where there is written " press a button to continue" when i press it, it start to work and appers this message :
0 KB/s (105 bytes in 1.000s)
Without closing this window, shutdown the phone
and restart it in bootloader mode (power + UP key in the keyboard)
Once inside the bootloader mode, flash the fixed.sbf from rsdlite
after it restarts, enable USB debugging and press enter to continue...
Premere un tasto per continuare . . .
Waiting for Phone
Syntax error: Unterminated quoted string
than the phone switch off by itself and i had turn it on in bootloader mode, i have flashed the fixed sbf and than the it show me this message
remount failed: Operation not permitted
failed to copy 'su' to '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
link failed Read-only file system
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
/sbin/hotplug > /sys/kernel/uevent_helper
The End
is it a bug or i had make a mistake ?
Click to expand...
Click to collapse
do this:
adb shell "rm /data/preinstall_md5/*"
and then run the script again, but when instead of rebooting into bootloader mode and flashing, just reboot it normally
thx for answer
but....i'm a noob... where i should type this : adb shell "rm /data/preinstall_md5/*" ??
I had the same problem, I'll try to do this ! let's see guys !
Caesarivs said:
It's a bug because of the translation... I've found it:
Code:
adb shell "echo 'doing something on adb, otherwise it doesn't work'"
Should change to
Code:
adb shell "echo 'doing something on adb, otherwise it does not work'"
@nicofff the ' in "don't" caused a syntax error
Click to expand...
Click to collapse
Just updated the POST pointing to the fixed version
sminatore said:
thx for answer
but....i'm a noob... where i should type this : adb shell "rm /data/preinstall_md5/*" ??
Click to expand...
Click to collapse
Gauzo said:
I had the same problem, I'll try to do this ! let's see guys !
Click to expand...
Click to collapse
Just download the latest version (v0.9-4) from github: https://github.com/nicofff/preinstalameEsta
The bug is fixed
still doesnt work, i have downloaded the last version and than follow again the instructions written in firts post, but if i turn on the device on bootmode it give me always the same error, and if i turn on the phone normally i cant flash the sbf file ....
sminatore said:
still doesnt work, i have downloaded the last version and than follow again the instructions written in firts post, but if i turn on the device on bootmode it give me always the same error, and if i turn on the phone normally i cant flash the sbf file ....
Click to expand...
Click to collapse
Run rootMM2.bat, do you get the same error?
rootMM2_en.bat
im trying on linux now... lets see
sminatore said:
rootMM2_en.bat
im trying on linux now... lets see
Click to expand...
Click to collapse
There are two .bat files... rootMM2_en.bat and rootMM2.bat... run rootMM2.bat and tell us if you get the same error... because the bug is fixed, it should be something else
Hey Guys !!! thanks it's working now !!!
Just try to use Rootmm2.bat not the other one with EN....
Thanks a LOT !!!!!
oh **** it works!!!!!!
(have done the same step i have done with rootMM2_en.bat)
THANKS!
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.
Hi all,
I made a small change to the com.android.server.telecom.CallActivity class (e.g. Log.i("I am here") ). I entered "mm" to build to the project under /packages/services/Telecomm and got an updated apk file in out/target/product/aosp_arm/system/priv-app/Telecom/Telecom.apk . And then I installed the apk by typing "adb install -r /path/to/Telecom.apk". The installer confirmed "success". I rebooted the device and logcat my added log line while making a phone call. However, I saw nothing.
On the other hand, if I do a full build by typing "make -j8" from the root of the repo tree and flash the image zip file using flashall.sh or update.sh, I can see my added log line.
What did I miss? I am sure there must be a way to make changes in the Telecom package w/o a full rebuilt everytime.
Thank you!
jameslhb said:
Hi all,
I made a small change to the com.android.server.telecom.CallActivity class (e.g. Log.i("I am here") ). I entered "mm" to build to the project under /packages/services/Telecomm and got an updated apk file in out/target/product/aosp_arm/system/priv-app/Telecom/Telecom.apk . And then I installed the apk by typing "adb install -r /path/to/Telecom.apk". The installer confirmed "success". I rebooted the device and logcat my added log line while making a phone call. However, I saw nothing.
On the other hand, if I do a full build by typing "make -j8" from the root of the repo tree and flash the image zip file using flashall.sh or update.sh, I can see my added log line.
What did I miss? I am sure there must be a way to make changes in the Telecom package w/o a full rebuilt everytime.
Thank you!
Click to expand...
Click to collapse
Do command "adb root /adb remount / adb pull Telecom.apk /system/priv-app/Telecom" work? I often use the command to update telephony code.
he_arslan said:
Do command "adb root /adb remount / adb pull Telecom.apk /system/priv-app/Telecom" work? I often use the command to update telephony code.
Click to expand...
Click to collapse
I think you meant adb push instead of pull. And yes, I tried adb push followed by killing the telecom process and it worked!! Thank you very much. :good: I am curious why adb install failed, though.
I am trying to sideload the new 7.1.1 OTA image from Google. When I run the command adb sideload [PATH TO UPDATE]\updatefile.zip it comes back with:
loading: 'update.zip'
* cannot read 'update.zip' *
File Permissions are all OK
The platform-tools have been updated using sdk-manager
ADB devices shows the device.
The phone is encrypted (I am guessing this is the issue)
Any help would be appreciated.
hideous said:
I am trying to sideload the new 7.1.1 OTA image from Google. When I run the command adb sideload [PATH TO UPDATE]\updatefile.zip it comes back with:
loading: 'update.zip'
* cannot read 'update.zip' *
File Permissions are all OK
The platform-tools have been updated using sdk-manager
ADB devices shows the device.
The phone is encrypted (I am guessing this is the issue)
Any help would be appreciated.
Click to expand...
Click to collapse
Just checking the obvious....but updatefile.zip is in your computer that's executing the ADB command, not on you phone, correct?
edit: Also, is your ota file actually named updatefile.zip?
Phone's encryption doesn't matter here.
Yes, I am running this from my computer. I have tried the original name for the OTA (also tried downloading it multiple times)
Also the phone is completely stock with a locked bootloader.
EDIT:
I turned on Tracing and this is the full error:
c:\Users\user\Nexus6P\ROMS\OTA>adb sideload angler-ota-nmf26f-61b4a915.zip
adb I 15200 3428 adb_trace.cpp:169] Android Debug Bridge version 1.0.36
adb I 15200 3428 adb_trace.cpp:169] Revision 302830efc153-android
adb I 15200 3428 adb_trace.cpp:169]
loading: 'angler-ota-nmf26f-61b4a915.zip'adb I 15200 3428 sysdeps_win32.cpp:145] load_file: could not allocate 1331770063 bytes
* cannot read 'angler-ota-nmf26f-61b4a915.zip' *
Are you on Windows 10? Experienced this issue yesterday and I also searched a long time.
In the device manager, my device showed up as "LeMobile Android Device", because this seems to be the newest Android driver. ADB is not working correctly with the LeMobile drivers. Had to switch back via "Use previous drivers" to the Nexus 6P drivers, then it worked like a charm.
The OTA image needs to be in the platform-tools folder along with the adb executable. Then Shift/right- click in the folder and select "Open command prompt here". Next type the command "adb sideload angler-ota-nmf26f-61b4a915.zip" without the quotes, this after selecting "Apply update from ADB" from the recovery menu. You may need to unplug your phone, and then plug it back in if the command fails.
Hello, I just received my leeco, But I received it with a modified rom
I have try to install TWRP recovery, for recovery its good It is installed
But since the phone dosent started he stay on the logo leeco android As if there were no rom
So I tried to push a rom via ADB but I have a closed error, and Since the recovery I can not mount the system or the SD on my PC for copy rom
i try this :
C:\Program Files (x86)\Minimal ADB and Fastboot> adb sideload leco.zip
loading: 'leco.zip'
* cannot read 'leco.zip' *
C:\Program Files (x86)\Minimal ADB and Fastboot> adb push leco.zip /data/media/0/
adb: error: connect failed: closed
I do not know what to do
EDIT : in recovery he says me he have not rom installed, so i think usb debuging is desactivated
thanks
k3npachi said:
Hello, I just received my leeco, But I received it with a modified rom
I have try to install TWRP recovery, for recovery its good It is installed
But since the phone dosent started he stay on the logo leeco android As if there were no rom
So I tried to push a rom via ADB but I have a closed error, and Since the recovery I can not mount the system or the SD on my PC for copy rom
i try this :
C:\Program Files (x86)\Minimal ADB and Fastboot> adb sideload leco.zip
loading: 'leco.zip'
* cannot read 'leco.zip' *
C:\Program Files (x86)\Minimal ADB and Fastboot> adb push leco.zip /data/media/0/
adb: error: connect failed: closed
I do not know what to do
thanks
Click to expand...
Click to collapse
The First error "cannot read leco.zip" looks like a typo maybe it's called leeco.zip?
Otherwise for me it looks like a adb problem or somehow a connection problem with adb
You sure installed all the drivers? Or has your cable a connection problem?
These are my theories, try some of them...
Antisound said:
The First error "cannot read leco.zip" looks like a typo maybe it's called leeco.zip?
Otherwise for me it looks like a adb problem or somehow a connection problem with adb
You sure installed all the drivers? Or has your cable a connection problem?
These are my theories, try some of them...
Click to expand...
Click to collapse
No leco.zip its the good name.
But before is locked adb working good, it's only since blocked
He have not solution for Mount internal storage since TWRP ?
Thanks
k3npachi said:
No leco.zip its the good name.
But before is locked adb working good, it's only since blocked
He have not solution for Mount internal storage since TWRP ?
Thanks
Click to expand...
Click to collapse
Maybe you have to try the EDL
venezolano69 said:
Maybe you have to try the EDL
Click to expand...
Click to collapse
sorry but what is EDL ?
k3npachi said:
sorry but what is EDL ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/redmi-note-3/help/flashing-locked-phone-via-edl-mode-t3373275/page1
venezolano69 said:
http://forum.xda-developers.com/redmi-note-3/help/flashing-locked-phone-via-edl-mode-t3373275/page1
Click to expand...
Click to collapse
ok thanks i test that
Haha i have find how to, If it can help some
http://www.gizmochina.com/2016/11/20/leeco-x820-max-2-super-unbrick-guide/
u find Qualcomm Drivers to download ?