Related
MAJOR Update 7/13/2010 15:48 PDT
Go to http://forum.xda-developers.com/showthread.php?t=724741 for the newer, confirmed root method
The following method is now outdated
Added optional instructions to flash Amon_RA's recovery image
Removed unnecessary steps (old step 6 and 7) because downloading the SDK folder in Step 2 already contains those files
Added .wav file of Tereg's cadence in the timing step
Added commands to Amon_RA's recovery image step
Added list of reported successes
Step 4 (Re-run SDK Setup) has been eliminated
Added 20th reported success with a new condition to try to test
Added YouTube video of user Dradien doing the count in the timing step
Added note in timing step about how long to wait after you see /!\ before you start the step over
Rearranged steps 2 and 3 since installing the USB driver after downloading Tereg's SDK folder might overwrite the modded .inf file
Added TODO note to at some point include instructions at various steps for other OS's where needed.
Tereg's testing has eliminated some extra steps, removed step 6 (the driver step), removed step 8 (maintaining a clean sd card, booting the phone back up, setting charge only, turning phone off), removed steps going into recovery where card DOES NOT HAVE TO BE IN when booting into FASTBOOT, therefore the timing step going from FASTBOOT to HBOOT has been removed.
Note about RUU OTA = Leak v3
More successes added with the new "60 partition" method explained by user anoek here: (http://forum.xda-developers.com/showpost.php?p=7089301&postcount=970)
Added 2 successes where both did not run loop.bat
Please note this process is experimental at best. While we have reported a number of successes, it has not been consistent and the success rate seems to be very low or non-existent for a number of users. We are doing the best we can to replicate this process in a more reliable way, and to continue testing for easier ways to achieve this.
**TODO**
Clarify/expand steps that need instructions based on user's OS
List of reported successes
If you find other people with reported successes, there are duplicates listed, or specific information needs to be added for an individual's case, please let Tereg or myself know.
1. Dc_striker (http://forum.xda-developers.com/showpost.php?p=6927162&postcount=1)
2. Hairson (http://forum.xda-developers.com/showpost.php?p=6942651&postcount=186)
3. tereg
4. a-wilcoxj (andirc) Also rooted another phone for another XDA member using his SD card
5. lame eris (http://forum.xda-developers.com/showpost.php?p=6974393&postcount=209)
6. kzoodroid (http://forum.xda-developers.com/showpost.php?p=6975283&postcount=225 and http://forum.xda-developers.com/showpost.php?p=6975440&postcount=228) Also rooted another phone for another person using his SD card
7. RKLamb2 (http://forum.xda-developers.com/showthread.php?p=6972493#post6972493)
8. Dradien (http://forum.xda-developers.com/showpost.php?p=6980387&postcount=318 and http://forum.xda-developers.com/showpost.php?p=6980491&postcount=320)
9. graphitedv (http://forum.xda-developers.com/showpost.php?p=6981435&postcount=334 http://forum.xda-developers.com/showpost.php?p=7011890&postcount=598) - Rooted a second phone, rooted using a Mac running 10.5.8 and the 2GB PNY card
10. djblade17 (http://forum.xda-developers.com/showpost.php?p=6981578&postcount=336) - Win 7 64 bit
11. xtreme3737 (http://forum.xda-developers.com/showpost.php?p=6985257&postcount=365)
12. reethewhat (http://forum.xda-developers.com/showpost.php?p=6987179&postcount=389) - Win7 64 bit
13. largerlager (http://forum.xda-developers.com/showpost.php?p=6988950&postcount=399)
14. Austinjs0102 (http://forum.xda-developers.com/showpost.php?p=6989397&postcount=405) - Windows XP SP3, 2GB PNY card
15. HaRdC0r3 (http://forum.xda-developers.com/showpost.php?p=6963059&postcount=457)
16. varkie (androidforums) (http://androidforums.com/htc-droid-eris/109901-how-many-successfully-went-leak-root.html#post1023198) - PNY 2GB National Geographic SD card
17. Pimpshit420 (http://forum.xda-developers.com/showpost.php?p=6990916&postcount=426)
18. rcharris (http://forum.xda-developers.com/showpost.php?p=6991694&postcount=437) -- Rooted using OS X. Originally tried in WinXP, switched to Mac OS X and got it rooted.
19. bpenney1 (http://forum.xda-developers.com/showpost.php?p=6993850&postcount=448) Had PNY card
20. davinci27 (http://forum.xda-developers.com/showpost.php?p=6996272&postcount=468 and http://forum.xda-developers.com/showpost.php?p=6996996&postcount=472)
21. Jdog94, on page 71, used airplane mode.
(http://forum.xda-developers.com/showpost.php?p=7034130&postcount=733)
22. NAA_Silent (androidforums) http://androidforums.com/htc-droid-eris/109865-leak-root-has-been-found-4.html#post1065772 -- "I tried about 30 times on my work machine running XP while using my Polaroid 16 gig card. I was not successful. Last night I tried again on my Win 7 64 laptop using the factory 8 gig card that came with my Eris. After about 5 attempts I hit the jackpot. I left the loop running instead of ctl+c after each attempt."
23. lostpilot28 (http://forum.xda-developers.com/showpost.php?p=7103114&postcount=1009 and http://forum.xda-developers.com/showpost.php?p=7113530&postcount=1038) - "I flashed the 60partitions.img file to my PNY 2GB SD card and did exactly as he said."
24. igot3ballz (http://forum.xda-developers.com/showpost.php?p=7104474&postcount=1013)
25. listyb01 (http://forum.xda-developers.com/showpost.php?p=7106183&postcount=1017)
26. homewmt (http://forum.xda-developers.com/showpost.php?p=7106822&postcount=1019) - Used anoek's dd image of 60 partition sd card
27. szgtr (http://forum.xda-developers.com/showpost.php?p=7122616&postcount=1055) - Used 4GB RiDATA card
28. lil_dez (http://forum.xda-developers.com/showpost.php?p=7142521&postcount=1087) - Did not run loop.bat
29. Nickboxer7 (http://forum.xda-developers.com/showpost.php?p=7143847&postcount=1088) - Did not run loop.bat
NEW thing to test "The last time I got /!\, I left the phone in the /!\ and popped the card out tand then right back in. Still had /!\ on the screen, but suddenly the device showed up in the loop." Also disable wifi, 3g, gps, bluetooth, and enable airplane mode.
Applications
-->Development-->and check the box titled "USB Debugging"
Video Tutorial by ECLIPS3 & Tereg
http://vimeo.com/album/250913
Prerequisites
Here is a dd image of teregs sdcard in a 7zip archive
http://www.multiupload.com/OT7SH4XNBP
1.Get the Java JDK
For the Java JDK go to http://java.sun.com/javase/downloads/index.jsp
Install Java Platform, Standard Edition, JDK 6 Update 20
2. Downloading Android SDK and running SDK_Setup
Go to http://developer.android.com/sdk/index.html and download the sdk for the platform you are using. Extract the folder contained in the .zip file to the C: drive. (In Windows's case, that would be C:\android-sdk-windows\).
Run SDK_Setup.exe from inside the android-sdk-windows folder.
*Note: you may get a prompt saying that it can't download the repository.xml*
To fix that error close the warning box and click on "Settings" on the left hand side and then check the box that says "Force Https://... sources to be fetched using http://"
Go to Available Packages, the list should now be populated, expand the list by clicking the little + next to https://dl-ssl.google.com/...
*Note: it is not necessary to download the SDK Platforms
Check the box marked "USB Driver Package" at the very bottom of the list
Click Install selected on the lower right corner of the window.
Click the Accept All Radio button on the lower right window that was brought up, and then click the Install button on the lower right corner.
To make sure you are on the right track you should now see in the list of installed packages two total packages:
Android SDK Tools, revision 6
USB Driver package, revision 3
3. Overwrite the android-sdk-windows folder with all the files you need
**TODO** (Include instructions for Mac and Linux SDK downloads)
Here you can download Tereg's complete SDK with all the files used http://www.multiupload.com/01Q1UXGLOF
Unzip the folder to C:
In our setup we have extracted the Android SDK to C:\android-sdk-windows
Root Process
Tereg's analysis has shown that RUU OTA = 2.1 Leak v3. If you have Leak v3 on your phone, then you probably do not have to do this step.
4. Flash the RUU OTA Update
Go to: http://shipped-roms.com/shipped/Des...WWE_2.36.605.1_release_signed_with_driver.exe and download the RUU OTA executable.
WARNING: THIS WILL WIPE YOUR PHONE. IF YOU HAVE ROOT YOU WILL LOSE ROOT. BACKUP THE CONTENTS OF YOUR SD CARD AND APPS YOU HAVE INSTALLED BEFORE YOU CONTINUE WITH THIS STEP.
If you need to backup the content of your SD Card, mount your phones SD card as a disk drive, open the drive within My Computer, and copy/paste all folders into a new folder. Copy the contents somewhere safe, we are not responsible for any lost data.
In addition to backing up your SD card, you should find a way to back up your phone (apps, settings, etc) using any method available (like MyBackup or Astro File Manager, etc). You will have a stock, wiped phone when you are finished with this step.
Execute the .exe and go through the wizard process.
5. Make sure USB Debugging is turned on on the phone
From the Home screen, press the Menu button -> Settings. Tap Applications -> Tap Development -> Make sure that USB Debugging is CHECKED.
Open a command prompt by going to Start -> Run. Type cmd in the text box, click OK.
If using Linux, open a terminal prompt and change your working directory to the android SDK tools folder and execute the "adb devices" command.
Execute these commands
Code:
cd \
If you don't see
Code:
C:\>
then type and execute
Code:
c:
Execute the following commands
Code:
cd android-sdk-windows
cd tools
adb devices
If you see the following
Code:
List of devices attached
HTxxxxxxxxxx device
where xxxxxxxxxx is some alphanumeric value, then you have done this step successfully.
Note: Old Step 6: Updating drivers for devices has been tested as unnecessary
6. Mounting the SD Card as a Disk Drive and formatting
Mount the SD card as a disk drive from within the phone. To do this, drag the notification bar down and tap the Ongoing notification (either Charge Only or HTC Sync) section. Tap the Disk Drive option (Mount as disk drive), and tap Done.
If you don't still have Computer Management open, click the "Start" button on your computer, RIGHT click on "My Computer", click "Manage", then Click "Disk Management" which is under "Storage" on the left pane and you will see all your drives.
Find your SD Card in the lower half of the right-hand pane. If you do not see your SD card, go to the Action menu and select "Refresh". If you bought the SD Card listed here, the size of the partition is 1.83 GB. Right click on this partition, and select "Format...", and click the "Yes" button that you are sure you want to do this.
Make the volume label blank, pick FAT32 as the file system, and select the allocation unit size 4096
DO NOT do a quick format.
Click the format button on the bottom right corner, then click OK to confirm the format.
Let it format, DO NOT eject the card while formatting.
When the format is complete, power off the phone.
Note: Old Step 8: Maintaining a clean SD card has been tested as unnecessary
7. Booting into recovery (the timing step)
.wav file of Tereg doing the count in this step: http://www.multiupload.com/IRL99EH394
NEW: Dradien has uploaded a video doing the count - http://www.youtube.com/watch?v=2bRl2ul7GdA
Note: The SD card does not have to be in. It can be out before you boot into FASTBOOT. Therefore, you do not need to press down on the SD card while in FASTBOOT, press Vol Down, then remove the SD card.
Make sure that the SD card is OUT before you begin this step.
Boot into FASTBOOT mode by pressing and holding the Send+Power buttons.
Go into HBOOT by pressing the Vol Down button.
NOTE: Running the loop is just for convenience purposes. It is not mandatory for this method to work.
Start -> Run -> type cmd in the box, click ok.
In the command prompt type
Code:
cd C:\android-sdk-windows\tools
Type
Code:
loop
and press enter
Position your right hand over the sd card and the left hand over the Volume Up button. As soon as you press Volume Up, starting counting "1-1000, 2-1000, 3-1000, 4-1000", which in Tereg's case took approximately 2.5-3.5 seconds. As soon as you finish counting, press the SD card into the phone.
Watch the command prompt. If it works it should display
List of devices attached
HTxxxxxxxxxx recovery
over and over again where xxxxxxxxxx is some alphanumeric value
If this succeeded you can stop the loop by pressing Ctrl+C
Important Note: After you see the /!\, you will need to wait for several seconds before you restart this step. You will need to wait for Device Manager to stop flickering before you pull the battery. Wait at least 10-15 seconds after you see the /!\ icon before you start this step over.
If this did not succeed, make sure that Device Manager is not flickering, then pull the battery to turn off the phone. Stop the loop in the command prompt by pressing Ctrl+C, and repeat this step again starting with the phone off.
8. Pushing files in recovery, and getting #
Next on the phone press Volume UP + Power at the same time, which will bring up a menu in Recovery.
Then select "Apply sdcard:update.zip"
THIS STEP WILL FAIL, don't worry, we expect it to.
Once the update has failed we need to go back to our command prompt (the one we stopped the loop in) and type
Code:
adb push ota.zip /sdcard/update.zip
and press enter, then type
Code:
adb push root.zip /sdcard
and press enter.
After each command, ensure there is no error message after executing the command.
The status for success will be something like
Code:
xxx KB/S (x bytes in xxxx.xxxs)
At the next prompt, type this command but DO NOT execute it yet.
Code:
adb push update.zip /sdcard
This is another timing step. You will need to scroll down to "Apply sdcard:update.zip", and press the Power button then look for a very faint, dim progress bar near the bottom of the screen. The progress bar will be green.
AS SOON AS YOU LOCATE THIS PROGRESS BAR, you need to execute the command you typed.
If successful you should see the Clockwork Mod Recovery along the top of the phone.
Go to the Partitions menu on your phone by rolling the trackball down and pressing the trackball to select it.
Then select "mount /system" once.
Scroll down to +++++Go Back+++++ and select it.
Scroll and select "Install zip from sd card". Then, scroll and select "Choose zip from sdcard", then scroll and select "root.zip"
Once this is done, select Reboot System from the menu, and let it boot normally.
After the phone comes back up to Sense UI, in the command prompt execute this command
Code:
adb install Superuser.apk
Again, you should see something like:
Code:
xxx KB/s (x bytes in xxx.xxxs)
pkg: /data/local/tmp/Superuser.apk
Success
underneath the command where x is some number
Once this step is done, make sure the phone is unlocked, awake and not asleep.
Type
Code:
adb shell
then type
Code:
su
You will get a prompt on the phone from superuser asking for permission. Allow this.
the $ symbol will change to #, which indicates you have root.
[Optional] Step 11. Flashing Amon_RA's recovery image
This step is optional. Follow these steps if you would like to flash Amon_RA's recovery image after you have achieved a root prompt.
Open the command prompt and change your working directory to C:\android-sdk-windows\tools exactly as you did in Step 12.
Execute these commands (Note: When you see $ or #, that does NOT mean you type $ or # respectively in the command. It means that is the prompt you should see at the time you are executing these commands.
If you extracted the android-sdk-tools folder in Step 3, you have all the files you need for this step.
Code:
adb shell
$ su
#mount -o rw,remount /dev/block/mtdblock3 /system
# exit
$ exit
adb push recovery.img /sdcard
adb push flash_image /data/local
adb shell
$ su
# chmod 755 /data/local/flash_image
# /data/local/flash_image recovery /sdcard/recovery.img
# reboot recovery
If you do these commands, you should be able to see Amon_RA's recovery.
At the bottom of the screen it should say "Build: RA-eris-v1.6.2", and you should have the following menu options.
Code:
- Reboot system now
- USB-MS toggle
- Backup/Restore
- Flash zip from sdcard
- Wipe
- Partition sdcard
- Other
- Power off
Note: If you are getting Permission Denied errors while doing any of these steps and you still have Clockwork's Recovery partition installed, user Dradien has reported success with the "Fix Permissions" function within Clockwork's Recovery main menu. Dradien reported that that function took about 5 minutes and afterwards was able to flash Amon_RA's recovery image.
Afterward
One thing to note, there is a step we did not do that Slide Root method did which is install a full root.zip that allows you complete root access when you execute an "adb shell ..." command.
i.e. if you run adb shell as the following example command prompt
Code:
C:\>adb shell
you will see a $ prompt, not a # prompt.
Therefore, any commands you are executing (at least for the moment) that require root access (like to flash Amon RA's recovery for instance):
Code:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
you will need to do this in the following manner
Code:
adb shell
$su
#mount -o rw,remount /dev/block/mtdblock3 /system
So, if you are getting permission denied errors from a regular command prompt while executing commands (adb shell mount..., adb flash_image..., etc) that require root access, you will most likely need to drop into shell manually, su into root, then cut off the first part of the command, put the rest of the command into the prompt and execute it.
Example:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
becomes
mount -o rw,remount /dev/block/mtdblock3 /system
Look at other tutorials on how to flash roms, if you have any questions pm me (Captainkrtek) or join us on irc.andirc.net #droideris & #leakroot and ask for any of the opers or Tereg for help.
Below are pictures and tools Tereg used, and how he oriented the phone and positioned his hands and screwdriver over the Vol Down/Vol Up buttons with left hand and over the SD card with the right hand during the SD card timing steps.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well written, thank you for writing this guide.
Also, the easiest way to get on irc is to go to http://chat.andirc.net/ and make a nick.
char561 said:
Also, the easiest way to get on irc is to go to http://chat.andirc.net/ and make a nick.
Click to expand...
Click to collapse
Join #leakroot to discuss it
Congrats Tereg, and CaptainKrtek. Tereg your crazy to flash RUU, thank you for trying again and proving
I should note, just remembered, I had Wi-Fi, Mobile Network and GPS all turned off during the entirety of this process.
Wow yeah great guide, people report your success with it and stuff. I'm trying it soon.
Sent from my Eris using XDA App
Great guide hopefully more people start getting root using this method, I currently have root (s-0ff) may try and root the brother in laws phone now he has leakv3. Welcome to the party leakers.
I feel completely crazy for unrooting (and that process is now done), but that's kind of where my mind is. I really want this process to be repeatable.
Hey where is the modified Inf file?
jvward said:
Hey where is the modified Inf file?
Click to expand...
Click to collapse
oops my fault, uploading now! thanks!
EDIT: In the tutorial now
ok so, i t may be a bit early, but once we are rooted from this method, can we unroot using the standard unroot method, or does nobody know that yet?
jrhoades858 said:
ok so, i t may be a bit early, but once we are rooted from this method, can we unroot using the standard unroot method, or does nobody know that yet?
Click to expand...
Click to collapse
Yes i believe you can, tereg just unrooted his phone to try this method again
Awesome! Trying in about an hour. Thank you!
Sent from my Eris using XDA App
trying right now, and yea i deleted all the adk and everyhting to start fresh =P so when i got the the part to download modded.inf i was like where the link but i remembered i didnt delete my downloads folder so i still had tht file =D haha
edit: O and fat32 with no quick format is taking forever!!!
Is there any chance this will work with the stock Eris microSD? I would prefer not to go out and buy a new one but if I absolutely have to I will today.
To unroot once you do this all you have to do is use the ruu that is posted here and that will set it back to exactly how it was.
zigzackattack said:
Is there any chance this will work with the stock Eris microSD? I would prefer not to go out and buy a new one but if I absolutely have to I will today.
Click to expand...
Click to collapse
There is a slight chance though pretty much no. Everyone who has tried it with the stock card has failed so your best bet is to go buy a $12 card
Yea I also am wondering if the stock 8 GB on Eris will work. Please let us know or test it out leakers.
MyFixofAndroid said:
Yea I also am wondering if the stock 8 GB on Eris will work. Please let us know or test it out leakers.
Click to expand...
Click to collapse
I do not believe it will. Everyone who has tried has failed.
Before we start, ROOT access, along with the "usb debugging" to be enabled on your phone for this unlock to be successful. Your phone must be connected to the computer.
UPDATE:One-click unlock for PC & MAC Created: http://forum.xda-developers.com/showthread.php?t=761751
The first step requires ADB which is a console that comes with the Android SDK, and is located in the C:\ Drive.
You can create a easy script to access adb by creating a text file and copying the following information:
Code:
@echo off
cd c:\android-sdk-windows\Tools
adb devices
pause
adb shell
NOTE: The android sdk must be in the C:\ drive for the script to work, and you can rename the "android-sdk-windows" to something else if you have an alternate name for your android sdk folder.
name the script ADB, and rename the .txt extension to .bat (enable view hidden file extensions in folder options) and run it for quick, and easy access to adb.
Now that problem is solved, lets get on to extracting the actual file from the internal sd card, to your computer for the purpose of extracting the unlock code.
Run adb.bat to open up adb, or any other method you might use and you should see a cmd promt with A list of the devices attached along with your device.
Press any key, and you should see a $ -----> type "su" (without the quotation marks) and press [ENTER]. If your device has already granted "su" or Superuser permissions to your desktop adb console, then you should see a # now you type
the following:
cat /efs/nv_data.bin >> /sdcard/nv_data.bin
press [ENTER] and you should see a repetition of the command you just typed with the difference being that the "#" is not before it, but under it.
You have successfully transferred the file to your internal sd card!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now to transferring the file that we will obtain the unlock code, to the computer to extract said code.
On your phone (while still connected to the computer) you must mount the USB storage to extract the file off the internal SD card, (to do this drag the notification bar down while connected, and click the "usb connected" button, which will prompt a pop up for "Mount" and "Don't Mount", we'll be mounting the sd card to extract the file)
now check "my computer" and look for the storage disk of the internal sd card for your phone (not the external!)
then move the "nv_data.bin" file to your C:\ drive
Now you need to download the "sgux.exe" unlock code finder, you can find it at the following:
http://www.mediafire.com/?js8dgn3nic5asb0 or http://www.multiupload.com/2IAYWWGF8A
after downloading the file from either mirror (the media fire one is zipped, which means you need to extract it) you need to move the sgux.exe file to your C:\
Now onto the last step:Obtaining the Code!
after having both the sgux.exe, and nv_data.bin file in the C:\ drive
Run your command promt (run>cmd or if you have a "windows key" press the windows key+r) in the command prompt type "cd C:\" (without the quotation marks) then sgux.exe nv_data.bin and voila the proccess should generate your own 8-digit unlock code!!
Now give yourself a pat on the back for your hard work ;P
HOW TO LOCK SAMSUNG GALAXY S - FOR WARRANTY AND ALTERNATIVE "UNLOCK"
After you get the NCK code using the method above, enter: *7465625*638*#
There will be a pop-up box.
Complete the first field (MCC/MNC) with the network you want your phone locked to (eg. 226 10 where 226 = romania; 10 = orange etc.) and the second field (Control Key) with the NCK extracted from the .bin file.
Press OK and your phone should relock.
This method can also be used in the case where the universal unlock code doesn't work, this is done by "locking the device to the carrier+sim" so someone who uses Rogers in Canada, would use the NETWORK "MCC" for their Country (302) and MNC for the carrier (720) so you use 302 720 with the instructions above to lock the phone to Rogers in Canada, thus allowing you to use the sim card. This is a "unlock" in terms that you can use it with another carrier, but not a "universal" unlock that can be used with any carrier without the hassle of repeating the above method.
Here are the MCC/MNC country codes:
http://en.wikipedia.org/wiki/Mobile_Network_Code
HOW TO UNLOCK AFTER PLACING DIFFERENT SIM
After inserting new sim, you should be prompted to enter unlock code, if not then to unlock your phone just use the code: #7465625*638*# and enter your NCK in the pop-up box. Press OK. Phone should get unlocked .
Click to expand...
Click to collapse
NOTE: Below I have attached the "adb.bat script, and the sgux.exe" files in zips, for those who want to download it directly from here.
I have flashed to JM5 and with Samset 1.9f, It comes pre-rooted but does not have a terminal emulator yet and Id like to give this a try on my locked Galaxy S, but Im not familiar with how to get ADB for my computer.. maybe you can add the steps or post another link for ADB ?
EarlZ said:
I have flashed to JM5 and with Samset 1.9f, It comes pre-rooted but does not have a terminal emulator yet and Id like to give this a try on my locked Galaxy S, but Im not familiar with how to get ADB for my computer.. maybe you can add the steps or post another link for ADB ?
Click to expand...
Click to collapse
I've included all the instruction for running ADB , but in that case make sure you have the android sdk installed
You can download it at the following:
http://dl.google.com/android/android-sdk_r06-windows.zip
Extract the zip, and then just follow my instructions in my original post.
I've also included a script to run it directly, it's attached in the first post and is called "adb.zip" that has the adb.bat script inside.
UPDATE:
You can also use the original method
http://forum.xda-developers.com/showpost.php?p=7776555&postcount=1
but instead of the adb code in there which is the following:
Code:
adb shell
su
dd if=/dev/block/bml3 of=/sdcard/bml3.bak
the above is the original method, but for some adb consoles there's a VITAL step missing!
the actual dev directory.
So below is the fix for the first method to work (use this)
Code:
adb shell
cd /dev/block
su
dd if=/dev/block/bml3 of=/sdcard/bml3.bak
Bowsa2511 said:
UPDATE:
You can also use the original method
http://forum.xda-developers.com/showpost.php?p=7776555&postcount=1
but instead of the adb code in there which is the following:
Code:
adb shell
su
dd if=/dev/block/bml3 of=/sdcard/bml3.bak
the above is the original method, but for some adb consoles there's a VITAL step missing!
the actual dev directory.
So below is the fix for the first method to work (use this)
Code:
adb shell
cd /dev/block
su
dd if=/dev/block/bml3 of=/sdcard/bml3.bak
Click to expand...
Click to collapse
the cd /dev/block shouldn't matter but I will add it to the guide
dagentooboy said:
the cd /dev/block shouldn't matter but I will add it to the guide
Click to expand...
Click to collapse
In my case (along with others) it wouldn't recognize and direct to the directory automatically, causing the creation of the nv_data.bin method.
The simple fix was directing adb to that directory XD
Bowsa2511 said:
In my case (along with others) it wouldn't recognize and direct to the directory automatically, causing the creation of the nv_data.bin method.
The simple fix was directing adb to that directory XD
Click to expand...
Click to collapse
ok sounds good. I found the nv_data.bin method by tracing where bml3 was being mounted. It turns out bml3 is mounted at /efs .... that is probably why you need su to copy bml3 because it is in use.
guys, could you please explain how to sim unlock but with some easier methods
these ADB and so on just have eaten my brains
spent 3 hours and 0 result
using mac os + windows 7 as virtual machine
DarkVasyaK said:
guys, could you please explain how to sim unlock but with some easier methods
these ADB and so on just have eaten my brains
spent 3 hours and 0 result
using mac os + windows 7 as virtual machine
Click to expand...
Click to collapse
Check out the original thread here. I updated it with an automatic script to generate the code.
It Worked.............great................Thank you so much.......
thansk for this!
Instructions worked perfectly ... got my code!
Now just have to find a foreign SIM to complete the job ...
Thanks to all that made this possible. AT&T was being a real PITA about unlocking.
Bowsa2511 said:
Before we start, ROOT access, along with the "usb debugging" to be enabled on your phone for this unlock to be successful. Your phone must be connected to the computer.
The first step requires ADB which is a console that comes with the Android SDK, and is located in the C:\ Drive.
You can create a easy script to access adb by creating a text file and copying the following information:
Code:
@echo off
cd c:\android-sdk-windows\Tools
adb devices
pause
adb shell
NOTE: The android sdk must be in the C:\ drive for the script to work, and you can rename the "android-sdk-windows" to something else if you have an alternate name for your android sdk folder.
name the script ADB, and rename the .txt extension to .bat (enable view hidden file extensions in folder options) and run it for quick, and easy access to adb.
Now that problem is solved, lets get on to extracting the actual file from the internal sd card, to your computer for the purpose of extracting the unlock code.
Run adb.bat to open up adb, or any other method you might use and you should see a cmd promt with A list of the devices attached along with your device.
Press any key, and you should see a $ -----> type "su" (without the quotation marks) and press [ENTER]. If your device has already granted "su" or Superuser permissions to your desktop adb console, then you should see a # now you type
the following:
cat /efs/nv_data.bin >> /sdcard/nv_data.bin
press [ENTER] and you should see a repetition of the command you just typed with the difference being that the "#" is not before it, but under it.
NOTE: Below I have attached the "adb.bat script, and the sgux.exe" files in zips, for those who want to download it directly from here.
Click to expand...
Click to collapse
Thank you for your step by step sir, very helpful, as i was trying to figure out how to get ADB running on my PC.
Thanks again.
not working...tried all methods for pc
tried adb method and cannot create nv_data.bin file system is read-only
tried unlocker app and it says NO CODES FOUND, and also says are you sure your using a samsung galaxy S.
my phone is samsung i897 captivate under att contract, never had to enter a code in the past, but now the phone is locked and i cant retrieve the code, any ideas?
Help please
i´ve tried to unlock have searched der nv_data.bin with a root explorer app, copied this to sd and from there in my folder c:\hack, where the sgux.exe is also
I run it and following i see if its ready:
Opening file <nv.bata.bin>....
Searching code block....
Found
Searching Code...
C:\hack>
where is my code?
Please help
Awesome guide! Can't wait to get my phone monday
I tried adb, and when I type su I get a reply superuser denied, don't understand why, need help
bump......
After running sgux.exe nv_data.bin, this is what show up:
MCC/MNC lock :00101
Any idea?
I'm on att, but currently roaming in China...
after I type su, it say's "Permission denied" what am I doing wrong? Can some please help me
I was deleting unused apps from my phone and, like an idiot, I deleted my only installed launcher. The phone boots and I can access the settings. I have a launcher installed and it shows up in menu/ settings/ app but it wont start and I don't know how to start it. I do have adb and fastboot though I don't have wireless internet. This device is not activated and there is no gmail account linked to this device. I did create a zip of a launcher and tried to flash it through recovery but that didn't work. I do not have a custom recovery installed but I did root the device. Is there a way to get a launcher installed and working so I can use this device again?
Grab the APK file for the stock launcher (or any launcher of your choice), connect your phone to the computer via USB with debugging on and install the launcher using this ADB command:
adb install launcher.apk
Make sure to replace launcher.apk with the exact name of the APK file, of course. You might need to copy the launcher to your SDK's platform-tools folder and run this command while in that directory as well, if the folder hasn't already been added to your PATH variable.
Once done, reboot your device. You can then use any root-enabled file manager to simply copy the launcher's APK file into /system/app to make sure you have one installed as a system app all the time, though make sure to fix its permissions to rw-r--r-- (644).
HQRaja said:
Grab the APK file for the stock launcher (or any launcher of your choice), connect your phone to the computer via USB with debugging on and install the launcher using this ADB command:
adb install launcher.apk
Make sure to replace launcher.apk with the exact name of the APK file, of course. You might need to copy the launcher to your SDK's platform-tools folder and run this command while in that directory as well, if the folder hasn't already been added to your PATH variable.
Once done, reboot your device. You can then use any root-enabled file manager to simply copy the launcher's APK file into /system/app to make sure you have one installed as a system app all the time, though make sure to fix its permissions to rw-r--r-- (644).
Click to expand...
Click to collapse
Thank you for your reply.
I already pushed the the launcher apk through adb and it installed on my phone from everything I can see. However even though it installed I do not know how to start it. I do not know how to gain access to a file manager as I do not access to any of my apps through the app drawer. Is there a way to activate and use an app without being able to access it in the drawer?
That's weird. Did you restart your phone? Upon every restart, Android looks for any installed launcher apps and if there's only a single one installed, it automatically loads it up. In case there are multiple launchers installed, Android loads a default one if set, or offers you to select one if you haven't set any as default. If you have installed a launcher via ADB by now, it should be loading upon device reboot. Try a different launcher's APK maybe? If it still doesn't work, try fixing permissions manually via ADB, or via recovery. Also, try installing it as a system app i.e. adb push Launcher.apk /system/app/ and don't forget to fix permissions to rw-r--r-- (644).
HQRaja said:
That's weird. Did you restart your phone? Upon every restart, Android looks for any installed launcher apps and if there's only a single one installed, it automatically loads it up. In case there are multiple launchers installed, Android loads a default one if set, or offers you to select one if you haven't set any as default. If you have installed a launcher via ADB by now, it should be loading upon device reboot. Try a different launcher's APK maybe? If it still doesn't work, try fixing permissions manually via ADB, or via recovery. Also, try installing it as a system app i.e. adb push Launcher.apk /system/app/ and don't forget to fix permissions to rw-r--r-- (644).
Click to expand...
Click to collapse
I will get right to doing that, and see how it turns out thank you and please stay tuned.
Update: I attempted the command to push it to the system/app and my return read "failed to copy 'apex.apk' to ' /system/app/apex.apk': Read-only file system"
It sounds to me upon reading that, that if I fix permission to make the file system read/write then this command will work. However, I do not know the commend to make that change.
No, you don't get read/write access by fixing permissions. The error that you get asically means you don't have system write access via ADB at the moment. Try this:
Code:
adb remount
adb push Launcher.apk /system/app/
adb shell
su
chmod 644 /system/app/Launcher.apk
exit
exit
adb reboot
The above method should work if your current kernel is an insecure one (i.e. it allows ADBD running as root and thus, the use of adb remount command for full system read/write access). If that doesn't work, try this:
Code:
adb push Launcher.apk /sdcard/
adb shell
su
mount -o remount,rw /system
mv /sdcard/Launcher.apk /system/app/Launcher.apk
chmod 644 /system/app/Launcher.apk
exit
exit
adb reboot
HQRaja said:
No, you don't get read/write access by fixing permissions. The error that you get asically means you don't have system write access via ADB at the moment. Try this:
Code:
adb remount
adb push Launcher.apk /system/app/
adb shell
su
chmod 644 /system/app/Launcher.apk
exit
exit
adb reboot
The above method should work if your current kernel is an insecure one (i.e. it allows ADBD running as root and thus, the use of adb remount command for full system read/write access). If that doesn't work, try this:
Code:
adb push Launcher.apk /sdcard/
adb shell
su
mount -o remount,rw /system
mv /sdcard/Launcher.apk /system/app/Launcher.apk
chmod 644 /system/app/Launcher.apk
exit
exit
adb reboot
Click to expand...
Click to collapse
I will try both commands and report back thank you!
These are my returns:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You could also try installing a launcher from the Google Play website and hopefully it will install on your phone. Then once you have a working launcher you could more easily restore the factory one.
spunker88 said:
You could also try installing a launcher from the Google Play website and hopefully it will install on your phone. Then once you have a working launcher you could more easily restore the factory one.
Click to expand...
Click to collapse
I can't use Google play because this I have not had this phone registered at all. I only used it to play games and media and never had my account linked to it. I now wish I would have because I agree with you, having done that would ahve made this entire thing a non situation I think.
That's kinda weird. Try the same command with 'cp' instead of 'mv', perhaps that'll help.
According to adb it worked, however I can not access home and the launcher is no longer in my list of installed apps. Very confusing to me
It seems then that you have deleted some other system-critical APK as well, perhaps. A good idea would be to reinstall the ROM now. If you are already running a custom ROM, you can do so without the need to wipe data, by installing the same ROM. In case of stock ROM, you should find a flashable zip file of the same version or a later update, and flash it without wiping data too. Though if that doesn't work either, a ROM flash followed by a full data+cache+dalvik-cache wipe should do it.
Oh speaking of that, try wiping cache and dalvik cache from recovery and rebooting to see if it helps, before you attempt the above.
HQRaja said:
It seems then that you have deleted some other system-critical APK as well, perhaps. A good idea would be to reinstall the ROM now. If you are already running a custom ROM, you can do so without the need to wipe data, by installing the same ROM. In case of stock ROM, you should find a flashable zip file of the same version or a later update, and flash it without wiping data too. Though if that doesn't work either, a ROM flash followed by a full data+cache+dalvik-cache wipe should do it.
Oh speaking of that, try wiping cache and dalvik cache from recovery and rebooting to see if it helps, before you attempt the above.
Click to expand...
Click to collapse
I was already thinking that so I finally found a stock firmware file and am currently attempting to flash it now. I will report back with the results.
Update: The results are in and.....it is now working! This is what I wanted to do from the start but I had a very hard time finding a good link to a stock rom. Mr. Raja I am very thankful for all your help and time you spent with me on this issue.
kingnarkissos said:
I was deleting unused apps from my phone and, like an idiot, I deleted my only installed launcher. The phone boots and I can access the settings. I have a launcher installed and it shows up in menu/ settings/ app but it wont start and I don't know how to start it. I do have adb and fastboot though I don't have wireless internet. This device is not activated and there is no gmail account linked to this device. I did create a zip of a launcher and tried to flash it through recovery but that didn't work. I do not have a custom recovery installed but I did root the device. Is there a way to get a launcher installed and working so I can use this device again?
Click to expand...
Click to collapse
you need to simply install the launcher..
adb install apex.apk
that is all.
kingnarkissos said:
I was already thinking that so I finally found a stock firmware file and am currently attempting to flash it now. I will report back with the results.
Update: The results are in and.....it is now working! This is what I wanted to do from the start but I had a very hard time finding a good link to a stock rom. Mr. Raja I am very thankful for all your help and time you spent with me on this issue.
Click to expand...
Click to collapse
I'm glad it worked out for you. You must have deleted some other system-critical APK as well, otherwise simply reinstalling the launcher via ADB should have worked just fine. In the future, it'll be a good idea not to delete any APKs from /system/app that you aren't absolutely sure about. =)
jimmydafish said:
you need to simply install the launcher..
adb install apex.apk
that is all.
Click to expand...
Click to collapse
That was the first thing I did and it did not work. The app did show up under the installed apps list, but I could not get it to start so it was never running. Therefor I couldn't gain access to it or any area of the device other than settings when the phone booted up. I stated such in the first post of this thread. Believe me I tried all the easy stuff first.
Mr.Raja I do agree with you. I must have deleted more than I thought I did because I agree with you and everyone else who is saying a simple adb flash will work. It should have worked. So whatever I did to it forced me to reflash a rom onto it. I am just thankful to you and everyone else who tried to help me. I appreciate the time spent assisting me.
How I fixed this issue was RSDlite and the rom from this link http://forum.xda-developers.com/showthread.php?t=2017200 and it worked like a charm.
This issue is resolved!
Hi ,
I wanted to modify the build.prop on my nexus4 , and i requested r/w permissions , i was using es file explorer, and the only way to do this , was to remount the partition from R/O to R/W , then it let me modify the file , and change permissions on that file, but i forgot to re-mount the partition as R/O before rebooting my phone. now it wont boot up , and i dont know how to change the permissions back to R/O , or how to fix this issue.
Hope this makes any sense. Thanks
Ikran said:
Hi ,
I wanted to modify the build.prop on my nexus4 , and i requested r/w permissions , i was using es file explorer, and the only way to do this , was to remount the partition from R/O to R/W , then it let me modify the file , and change permissions on that file, but i forgot to re-mount the partition as R/O before rebooting my phone. now it wont boot up , and i dont know how to change the permissions back to R/O , or how to fix this issue.
Hope this makes any sense. Thanks
Click to expand...
Click to collapse
All the mount point are reset upon reboot, so it won't be affecting your system or whatsoever. However, the problem seems due to permission of your build.prop or it could be the settings that you added to the build.prop
If you have custom recovery installed, try Fix permissions. If it doesn't work, you can either re-flash the ROM or use adb to push back original build.prop into /system.
ksilver89 said:
All the mount point are reset upon reboot, so it won't be affecting your system or whatsoever. However, the problem seems due to permission of your build.prop or it could be the settings that you added to the build.prop
If you have custom recovery installed, try Fix permissions. If it doesn't work, you can either re-flash the ROM or use adb to push back original build.prop into /system.
Click to expand...
Click to collapse
i replaced( overwrite) the modified build.prop that i had on the phone with the original build.prop file, then rebooted the phone. and now it wont start up at all. i have a custom recovery from the nexus tool kit ( i think its cwm) . but that one works only if i can connect my phone to the pc , then boot in recovery mode, which i cant, since the phone wont start now. only recovery that i have now is that with a dead droid, which i can bypass and after that i got 4 options reboot , wipe or format, install files abd something and another option. i would gladly reflash my phone if you can tell me how
What modifications have you done to the build.prop?
Sent from my Nexus 4 using Tapatalk 4
Ikran said:
i replaced( overwrite) the modified build.prop that i had on the phone with the original build.prop file, then rebooted the phone. and now it wont start up at all. i have a custom recovery from the nexus tool kit ( i think its cwm) . but that one works only if i can connect my phone to the pc , then boot in recovery mode, which i cant, since the phone wont start now. only recovery that i have now is that with a dead droid, which i can bypass and after that i got 4 options reboot , wipe or format, install files abd something and another option. i would gladly reflash my phone if you can tell me how
Click to expand...
Click to collapse
No fix can be done without a PC now, unless you have a nandroid backup (clearly you don't have it right now).
Hold vol down + power key to enter bootloader mode. Connect the phone to your PC.
1. If your bootloader is locked, unlock the bootloader.
Code:
fastboot oem unlock
This is important, if you don't format the cache, all your data will be wiped upon reboot!
Code:
fastboot format cache
2. Download & flash cwm or twrp. Boot into recovery.
3. Use fix permissions.
OR
Mount system partition with the recovery interface. Then run this adb command on your PC.
Code:
adb shell chmod 644 /system/build.prop
adb reboot
andyabc said:
What modifications have you done to the build.prop?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
i had this line there qemu.hw.mainkeys=1 , but i replaced the build.prop which had this line in, with the original build.prop, rebooted the phone , and now it wont boot up ( as i said, in doing this i have mounted the system partition from ES File Explorer from R/O to R/W, and forgot to turn them back to R/O before reboot) so my guess is that this happened because i didnt remounted back the partition with R/O permissions
Ikran said:
i had this line there qemu.hw.mainkeys=1 , but i replaced the build.prop which had this line in, with the original build.prop, rebooted the phone , and now it wont boot up ( as i said, in doing this i have mounted the system partition from ES File Explorer from R/O to R/W, and forgot to turn them back to R/O before reboot) so my guess is that this happened because i didnt remounted back the partition with R/O permissions
Click to expand...
Click to collapse
You don't really need that since you already have softkeys anyway.
The remount is not the case at all, the issue is either the permissions or the property itself.
Which recovery do you have?, if you have TWRP then you can fix it for sure with it's special feature.
Sent from my Nexus 4 using Tapatalk 4
occupied icinme
andyabc said:
You don't really need that since you already have softkeys anyway.
The remount is not the case at all, the issue is either the permissions or the property itself.
Which recovery do you have?, if you have TWRP then you can fix it for sure with it's special feature.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
i think i have twrp but i could boot into it only when the phone was connected to the pc and from the nexus 4 tool kit
Ikran said:
i think i have twrp but i could boot into it only when the phone was connected to the pc and from the nexus 4 tool kit
Click to expand...
Click to collapse
Then you are just booting to it (not flashed) but anyway one you get on there you have to TWRP, Advanced and then Terminal command.
Go to the system folder and type the following commands IF you have the backup:
rm build.prop
mv build.prop.bak build.prop
Sent from my Nexus 4 using Tapatalk 4
ksilver89 said:
No fix can be done without a PC now, unless you have a nandroid backup (clearly you don't have it right now).
Hold vol down + power key to enter bootloader mode. Connect the phone to your PC.
1. If your bootloader is locked, unlock the bootloader.
Code:
fastboot oem unlock
This is important, if you don't format the cache, all your data will be wiped upon reboot!
Code:
fastboot format cache
2. Download & flash cwm or twrp. Boot into recovery.
3. Use fix permissions.
OR
Mount system partition with the recovery interface. Then run this adb command on your PC.
Code:
adb shell chmod 644 /system/build.prop
adb reboot
Click to expand...
Click to collapse
but how can i run these commands since my phone wont boot up so i can connect it to my pc ? and my bootloader is unlocked + rooted nexus
Ikran said:
but how can i run these commands since my phone wont boot up so i can connect it to my pc ? and my bootloader is unlocked + rooted nexus
Click to expand...
Click to collapse
Go to the bootloader, it has Fastboot from there.
EDIT: Oh you where talking about ADB, try using the method I posted on the previous page.
Sent from my Nexus 4 using Tapatalk 4
Ikran said:
but how can i run these commands since my phone wont boot up so i can connect it to my pc ? and my bootloader is unlocked + rooted nexus
Click to expand...
Click to collapse
From my understanding, this is your current situation and phone setup, correct me if I'm wrong.
Bootloader: Booted
Recovery: Stock/Original
ROM: Running, but now Bootloop <-- You are here.
Now, because it is now in the "ROM" states, the animation continues to play on and on, you need to turn OFF your phone, just hold the power button for more than 8 secs until the screen goes off.
IF holding the power button doesn't work, hold VOLUME DOWN + POWER key for more than 8 secs instead.
IF your phone already turned off, you can skip this step.
After you power down your phone, hold VOLUME DOWN + POWER key, your phone will enter "Bootloader" mode.
Bootloader: Fastboot <--- You are here.
Recovery: Stock/Original
ROM: Not Running
Now you can connect your phone to your PC with USB cables. Go to android-sdk\platform-tools folder, hold Shift + Right click and select Open command window here, enter this command:
Code:
fastboot devices
IF you don't see your device in the list, your PC will need "driver" to communicate with your phone, download it here: http://developer.android.com/sdk/win-usb.html
Open Device Manager, update the driver.
There, you need to get a custom recovery, get either TWRP or CWM, because you need them to run the SHELL command. Get them installed and boot into recovery.
Bootloader: Booted to recovery
Recovery: CWM/TWRP <--- You are here.
ROM: Not Running
In the command window, now type "adb shell" and enter.
Try the command posted by andyabc, reboot.
ksilver89 said:
From my understanding, this is your current situation and phone setup, correct me if I'm wrong.
Bootloader: Booted
Recovery: Stock/Original
ROM: Running, but now Bootloop <-- You are here.
Now, because it is now in the "ROM" states, the animation continues to play on and on, you need to turn OFF your phone, just hold the power button for more than 8 secs until the screen goes off.
IF holding the power button doesn't work, hold VOLUME DOWN + POWER key for more than 8 secs instead.
IF your phone already turned off, you can skip this step.
After you power down your phone, hold VOLUME DOWN + POWER key, your phone will enter "Bootloader" mode.
Bootloader: Fastboot <--- You are here.
Recovery: Stock/Original
ROM: Not Running
Now you can connect your phone to your PC with USB cables. Go to android-sdk\platform-tools folder, hold Shift + Right click and select Open command window here, enter this command:
Code:
fastboot devices
IF you don't see your device in the list, your PC will need "driver" to communicate with your phone, download it here: http://developer.android.com/sdk/win-usb.html
Open Device Manager, update the driver.
There, you need to get a custom recovery, get either TWRP or CWM, because you need them to run the SHELL command. Get them installed and boot into recovery.
Bootloader: Booted to recovery
Recovery: CWM/TWRP <--- You are here.
ROM: Not Running
In the command window, now type "adb shell" and enter.
Try the command posted by andyabc, reboot.
Click to expand...
Click to collapse
In TWRP there is a Terminal Command menu where you can do commands from so you can do modification's to the OS.
Sent from my Nexus 4 using Tapatalk 4
It is worth mentioning that the command "fastboot oem unlock" will actually erase all the personal data (should also include sdcard folder) and make it a blank phone! Use with cautions!
andyabc said:
In TWRP there is a Terminal Command menu where you can do commands from so you can do modification's to the OS.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
so the phone when i turn it on, the logo from google appears and under that the unlocked lock , next, the 4 colored lines of nexus should appear . my phone doesnt gets to that, after the image of google disappears , its just a black screen , think is that bootloop you were saying.
BUT i managed to install cwm 6.0.3.5 on the phone and i am able to boot into recovery now . twrp wouldnt load for some reason, just frozen on the google logo when it was suppose to load .
so at this point i am here as you said:
Bootloader: Booted to recovery
Recovery: CWM/TWRP <--- You are here. ( cwm 6.0.3.5 )
ROM: Not Running
in cmd i did: adb devices >result:
C:\Program Files (x86)\WugFresh Development\data>adb devices
List of devices attached
00765833628b346b recovery
after that: adb shell > result :
C:\Program Files (x86)\WugFresh Development\data>adb shell
~ # adb shell chmod 644 /system/build.prop
adb shell chmod 644 /system/build.prop
/sbin/sh: adb: not found
~ # chmod 644 /system/build.prop
chmod 644 /system/build.prop
chmod: /system/build.prop: No such file or directory
~ # cd /system
cd /system
/system # chmod 644 build.prop
chmod 644 build.prop
chmod: build.prop: No such file or directory
/system # chmod 644 /system/build.prop
chmod 644 /system/build.prop
chmod: /system/build.prop: No such file or directory
/system # adb shell chmod 644 /system/build.prop
adb shell chmod 644 /system/build.prop
/sbin/sh: adb: not found
Ikran said:
after that: adb shell > result :
C:\Program Files (x86)\WugFresh Development\data>adb shell
~ # adb shell chmod 644 /system/build.prop
adb shell chmod 644 /system/build.prop
/sbin/sh: adb: not found
~ # chmod 644 /system/build.prop
chmod 644 /system/build.prop
chmod: /system/build.prop: No such file or directory
~ # cd /system
cd /system
/system # chmod 644 build.prop
chmod 644 build.prop
chmod: build.prop: No such file or directory
/system # chmod 644 /system/build.prop
chmod 644 /system/build.prop
chmod: /system/build.prop: No such file or directory
/system # adb shell chmod 644 /system/build.prop
adb shell chmod 644 /system/build.prop
/sbin/sh: adb: not found
Click to expand...
Click to collapse
Great, you're almost there. Now in the CWM, there is a menu item called "Mount and storage", you need to mount /system partition in order for the command to work.
Tips: If you already run "adb shell", you are already "inside" the shell, so you don't need to type "adb" anymore. Notice the #? Just use chmod directly.
Tips 2: If you successfully corrected the permission but it didn't work, you will have to replace the build.prop with your original one.
ksilver89 said:
Great, you're almost there. Now in the CWM, there is a menu item called "Mount and storage", you need to mount /system partition in order for the command to work.
Tips: If you already run "adb shell", you are already "inside" the shell, so you don't need to type "adb" anymore. Notice the #? Just use chmod directly.
Tips 2: If you successfully corrected the permission but it didn't work, you will have to replace the build.prop with your original one.
Click to expand...
Click to collapse
thanks it worked, i had to mount the /system partition for the shell command to work, the phone booted up now, and it works, but for some reason everything is wiped from the phone i had some backup , i will see if i can restore anything from it. if not c'est la vie.
Thanks again
Guys, I have a similar kind of issue,
After flashing a Custom ROM in my Nexus 4, my phone is stuck on a bootloop, \
I have tried flashing almost everything, but still the bootloop exists,
If someone is willing to help me,
Just reply to this my "Yes" and I shall elaborate my whole issue here,
Thank you.
Rockstar600 said:
Guys, I have a similar kind of issue,
After flashing a Custom ROM in my Nexus 4, my phone is stuck on a bootloop, \
I have tried flashing almost everything, but still the bootloop exists,
If someone is willing to help me,
Just reply to this my "Yes" and I shall elaborate my whole issue here,
Thank you.
Click to expand...
Click to collapse
Yes, maybe.
Nuu~ said:
Yes, maybe.
Click to expand...
Click to collapse
Okay,
Let me quote my problem,
I also posted it on MSkip's Toolkit thread,
I did search but wasn't able to find a proper solution,
I was on a 4.3, with latest TWRP installed,
I flashed a ROM that was 4.2.2 after I flashed the phone was not booting up, and was stuck on Google logo,
I did wipe in the TWRP and even re-installed the ROM, had the same issue again,
So, I thought to flash 4.2.2 Google Factory Image via this toolkit,
I downloaded the Factory Image from Google and placed it in the folder which says "Put factory image here"
Followed all the procedures, and flashed the 4.2.2 factory image in my phone,
Now the phone is stuck on the X logo,
I tried going into the stock recovery and did a factory reset, but again the same thing,
The phone isn't booting up,
Also one thing i noticed, while the phone is booting the "Google" logo stays around a minute, and then the X boot animation appears,
Any clue what to do??
I tried pushing the factory image via toolkit several times, but again I'm stuck at the same boot animation,
Please help me regarding this,
I'm at work, trying to search and find information as much as I can,
I can now boot on 4.2.2 but in settings the phone says that the base band is unknown, IMEI is gone,
And I cannot even see the internal storage when I connect my phone to PC.
Here is what I'm facing.
Also check this,
I got this error too, unable to post the image so posting the link http://imageshack.us/photo/my-images/9/jys1.jpg
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you need any other details, please just do ask me, I will try my best to answer you properly.
Thank you.
Temp CWM-recovery
1. Download and put the UPDATE-SuperSU-vX.Xx.zip on internal/external SdCard
2. Download, extract the folder IntelAndroid-FBRL and put on the C drive
3. Follow this guide (Use the option T3)
This is new version fixed by social-design-concepts (Please support its work with donations)
Now backup kernel with recovery too:
View attachment IntelAndroid-FBRL-01-17-2015.7z
Root, backup & restore on the external card works well:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bodivas said:
Temp CWM-recovery
1. Download and put the UPDATE-SuperSU-vX.Xx.zip on internal/external SdCard
2. Download, extract the folder IntelAndroid-FBRL and put on the C drive (do not use other versions)
3. Follow this guide (Use the option T3)
View attachment 3107550
Backup & restore on the external card works well
Click to expand...
Click to collapse
Maybe I could get you to send dumps of this device it be nice to get to the bottom of why the the updated version doesn't work on this device.
Sent from my XT907 using XDA Free mobile app
social-design-concepts said:
why the the updated version doesn't work on this device.
Click to expand...
Click to collapse
Perhaps because the new version lacks the table mount points in recovery.zip/etc:
View attachment fstab.rar
Thanks for the great work!! 2P810+++++79361W
bodivas said:
Perhaps because the new version lacks the table mount points in recovery.zip/etc:
View attachment 3107582
Thanks for the great work!!
Click to expand...
Click to collapse
Give me moment I like to get the dump of fastboot.img recovery.fstab should be generated from the fstab droidboot / fastboot uses to handle partitions I'm making changes to the recovery.fstab generation so like to include fixes for this if their using other name or something.
If you could this should dump boot recovery fastboot and system
https://www.androidfilehost.com/?fid=95887005526788692
Sent from my XT907 using XDA Free mobile app
social-design-concepts said:
If you could this should dump boot recovery fastboot and system
https://www.androidfilehost.com/?fid=95887005526788692
Click to expand...
Click to collapse
I saw that when starting new version generates mount point right (mmcblk1p1) but fails to mount internal sd card the same. I added recovery.fstab in recovery.zip/etc and your new version 12-29-2014 works without problems!
All versions of yoga 2 (8,10,13) there year numbers and partitions sizes equal ..
For the kernel, recovery and fastboot, I had to use:
Code:
dd if=/dev/block/mmcblk0p3 of=/sdcard/boot.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/recovery.img
dd if=/dev/block/mmcblk0p5 of=/sdcard/droidboot.img
Download dump_yoga2_830L
This is full stock firmware
Can we use this to dual boot with Yoga 2 tablet with Windows?
bodivas said:
I saw that when starting new version generates mount point right (mmcblk1p1) but fails to mount internal sd card the same. I added recovery.fstab in recovery.zip/etc and your new version 12-29-2014 works without problems!
All versions of yoga 2 (8,10,13) there year numbers and partitions sizes equal ..
For the kernel, recovery and fastboot, I had to use:
Code:
dd if=/dev/block/mmcblk0p3 of=/sdcard/boot.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/recovery.img
dd if=/dev/block/mmcblk0p5 of=/sdcard/droidboot.img
View attachment 3107675
Download dump_yoga2_830L
This is full stock firmware
Click to expand...
Click to collapse
Thanks I'll download and see if i can resolve the issue
Sent from my XT907 using XDA Free mobile app
redhern said:
Can we use this to dual boot with Yoga 2 tablet with Windows?
Click to expand...
Click to collapse
First you have to have the dump of bios..
Is the bios available? I havent seen it mentioned in any of the posts.
redhern said:
Is the bios available? I havent seen it mentioned in any of the posts.
Click to expand...
Click to collapse
BIOS is present here but you have to know where to put. And then the windows do not care so much - I want CMmod
Here the guide for ONDA V975i
I do not want to risk (I've already lost imei on my 830L) with these experiments
successfully rooted but... no adb root nor adb remount
Hello,
I successfully rooted my 1050F device following this guide
Now I'd like to run adb as root and to be able to remount rw /system to put and remove staff there but the usual method don't work.
I tried adb root and adb remount but lenovo adb cannot run as root in production build.
I tried installing adb-insecure 2.0 which usually do the trick but when I patch the kernel from the app and use adb insecure demon the device is not seen by the PC with adb .
I also tried to remount with "sudo mount -o remount rw /system" but I cannot write in the /system partition
any suggestion?
thanks,
Dario
blackdir said:
Hello,
I successfully rooted my 1050F device following this guide
Now I'd like to run adb as root and to be able to remount rw /system to put and remove staff there but the usual method don't work.
I tried adb root and adb remount but lenovo adb cannot run as root in production build.
I tried installing adb-insecure 2.0 which usually do the trick but when I patch the kernel from the app and use adb insecure demon the device is not seen by the PC with adb .
I also tried to remount with "sudo mount -o remount rw /system" but I cannot write in the /system partition
any suggestion?
thanks,
Dario
Click to expand...
Click to collapse
adb shell
su
mount -o rw,remount /system
vampirefo said:
adb shell
su
mount -o rw,remount /system
Click to expand...
Click to collapse
sure, that will work, but if you need to push several files it is very tim consuming as you need to copy to a temporary location on the device and then move them to /system
if you are able to get adb insecure you can create a batch file that you can run from the PC
Any idea about the reason why dab insecure is not working on this device?
Is it because the device is intel based and not Arm?
(if this is a stupid question, please forgive me as it is my first experience on Android Intel development)
blackdir said:
sure, that will work, but if you need to push several files it is very tim consuming as you need to copy to a temporary location on the device and then move them to /system
if you are able to get adb insecure you can create a batch file that you can run from the PC
Any idea about the reason why dab insecure is not working on this device?
Is it because the device is intel based and not Arm?
(if this is a stupid question, please forgive me as it is my first experience on Android Intel development)
Click to expand...
Click to collapse
Correct you need a adbd binary for intel fully rooted meaning its always root, or you need to have an unlocked bootloader, that allows flashing of modified boot.img.
I updated the system via OTA and root again but it said Failed: too many links or something like that but it continued and cwm is installed. Is this ok?
redhern said:
Is the bios available? I havent seen it mentioned in any of the posts.
Click to expand...
Click to collapse
Have you tried flashing the bios yet or did you find any other ways to run windows on this tablet?
bodivas said:
BIOS is present here but you have to know where to put. And then the windows do not care so much - I want CMmod
Here the guide for ONDA V975i
I do not want to risk (I've already lost imei on my 830L) with these experiments
Click to expand...
Click to collapse
bodivas, could you post a guide on how to install windows on external sd card? The guide you posted when translated to english it is very hard to understand, and the onda is built on a different chipset, slower ones, so we would need to find intel baytrail drivers for it to work right. Also would the bios for the 1050 work on the 1350?
Rooted my Yoga 2 10" with the Jan. 10 OTA update installed, worked like a charm and the next best thing to a one-click root for noobs like me!
Thanks!
Here the same. 1380F with last OTA and root is rock solid [emoji106]
I have a problem
After I root my YT2-1050f, I can't enter recovery mode.