Related
Hello all,
I'm having a problem with the stock recovery. I have tried installing G.O.T. Open Recovery 2.01 and the install is OK, and I can do stuff in the menus, but every time I reboot, the stock recovery comes back. I followed the instructions by nadlabak on how to remove the script that reinstalls the stock recovery (android.doshaska.net/rootable, sorry the forum isn't allowing me to post the actual link as I'm a new user), but it doesn't work. There is no error message, just nothing happens. Can someone help? Thanks.
Xenobio said:
Hello all,
I'm having a problem with the stock recovery. I have tried installing G.O.T. Open Recovery 2.01 and the install is OK, and I can do stuff in the menus, but every time I reboot, the stock recovery comes back. I followed the instructions by nadlabak on how to remove the script that reinstalls the stock recovery (android.doshaska.net/rootable, sorry the forum isn't allowing me to post the actual link as I'm a new user), but it doesn't work. There is no error message, just nothing happens. Can someone help? Thanks.
Click to expand...
Click to collapse
Can you describe in detail what you did?
Method 1: command line
1. Booted into recovery
2. Installed GOT Open Recovery
3. Immediately after that (without rebooting, as it would have caused the stock recovery to be reinstalled) went into console and typed "rm -f /system/etc/install-recovery.sh"
4. Nothing happens, the command line # symbol just appears on the next line
5. Went back to main menu and rebooted, stock recovery came back
Method 2: script
1. Downloaded the "Disable_recovery_check_by_OTA.zip" file from the page mentioned previously
2. Unzipped and copied the .sh file to my sdcard in the OpenRecovery scripts folder
3. Step 1 and 2 like above
4. Went to the "Miscellaneous > Run script" menu
5. Ran "Disable_recovery_check_by_OTA.sh"
6. It says "-- Shell script..." then the path and filename of the script, then it says "Done" on the next line
7. Went back to main menu and rebooted, stock recovery came back
I also tried something after removing the install-recovery.sh...if I reboot into recovery (press and hold X immediately after selecting "Reboot" from the GOT main menu), I get Open Recovery back. But, if I reboot into Android and then turn it off and then boot into recovery, it's the stock recovery.
But every time you can use openrecovery right? If so, that's normal behavior. We can't replace recovery.
did you try to put the script into the init folder? I'm not sure anymore if its that one, but one of these folders contains a bunch of script that will be executed on boot up.. it worked for me (once) before i bricked my phone.. lol
Xenobio said:
Hello all,
I'm having a problem with the stock recovery. I have tried installing G.O.T. Open Recovery 2.01 and the install is OK, and I can do stuff in the menus, but every time I reboot, the stock recovery comes back. I followed the instructions by nadlabak on how to remove the script that reinstalls the stock recovery (android.doshaska.net/rootable, sorry the forum isn't allowing me to post the actual link as I'm a new user), but it doesn't work. There is no error message, just nothing happens. Can someone help? Thanks.
Click to expand...
Click to collapse
I am sure there is a way. OpenRecovery from G.O.T is slightly differrent, try to use the one from nadlabak and see what happens....?
I currently have a bell Samsung galaxy s ( I-9000 ) and after I updated to 2.2 JL2 I was unable to root my phone or install programs from recovery but after a long time of fooling around I was able to figure out what works.
------
Disclaimer : This is what worked for me on my SGS, do this at your own risk and make sure you follow the instructions in order
------
******
Before you do ANY of this test that you can get into download mode and recovery mode.
Test recovery:
When the phone is off push Volume up, Home (middle button in the bottom) and then power and the same time when the boot screen comes up, let go.
Test download
When the phone is off push Volume down, Home (middle button in the bottom) and then power and the same time when the boot screen comes up, let go.
If at any time you mess up your phone, enter download mode and flash the old rom back on the phone via odin3 which is at the bottom
*****
1) Turn on USB debugging
Unplug USB -> Settings -> Development -> check USB debugging -> plug in USB
2) Root phone
Download : http://forum.xda-developers.com/showthread.php?t=803682
unzip in a folder -> run SuperOneClick.exe -> click root
3) Install modified 3e recovery (allows unsigned installs)
Download : http://forum.xda-developers.com/showthread.php?t=833423
unzip in a folder -> run install.bat -> reboot phone
------
you can stop here if that is all you want to do on this rom - if you want to install a custom rom feel free to follow along the rest of the steps
------
4) Install Clockworkmod
Go into the market -> search for clockworkmod -> download ROM Manager
5) Install CWM Recovery
Open Rom Manager -> click "Flash CWM Recovery"
6) Download rom
Put the rom you wish to flash and put it in the "internal" SD (the 16GB one, not the microSD one you can put in yourself)
7) Boot into Recovery
Volume up + Home + Power wait till the logo comes up and let go
Select reinstall packages (I believe it is called) and you might have to do it twice and you will boot into CWM recovery
8) CWM Recovery
choose to flash rom from SD and accept it and you are done.
--
Questions
I will try to answer any questions that I had during my search to the best of my knowledge, i might be off the mark a bit but close enough to get the idea.
What is to root?
Rooting gives your phone access to the system files and allows you to make changes to them, meaning the phone can be damaged if something changed something important but also gives you freedom to change things like install custom rom. It is a good idea to unroot the phone if you are not doing any changes to it or don't want to mess stuff up.
What is recovery or 3e recovery?
Recovery is a way of loading certain programs directly into the phone, the file to do this is called "update.zip". Once booted into recovery you can tell the phone to install the file.
The issue is that the old version 2e allowed unsigned programs (meaning any program could be installed) but 3e allowed only signed programs to be installed so it would not let us install programs like CWM to flash a rom.
SOo in short the 3e modification lets us install unsigned programs like 2e did.
What is Rom Manager / ClockworkMod?
It is a program to flash a rom on the phone, the rom manager is booted in via 3e recovery.
Does it matter which Rom version I install?
Not really the last 3 letters ( JYP / JL2 ) are just version numbers and you can flash any rom that in within your product, soo i would just suggest keeping within any the roms in this thread : http://forum.xda-developers.com/forumdisplay.php?f=665
Extra files
Odin3 : http://forum.xda-developers.com/attachment.php?attachmentid=405389&d=1285090568
Samsung firmware : http://www.samfirmware.com/ (can login with Gmail account)
Hi All:
My Sprint Tab P100 got some strange problems.
It's a second hand P100, Once i turn on the tab, it will warning with 3 Beebee, and nook & Amaza Mp3 & Market will report error.
Below warning will show up:
Amazon MP3_nook
“The application XXX has stopped unexpectedly, pls try again”
Market
"Attention:
An Error has occured, Please try again later."
After check, i found the original usr information still there.
(Gmail/Facebook account will try to sync with previous owner's ID. and i can not remove the account.)
What i have tried:
1) I have tried to WIPE using system recovery, after WIPE both data & Cache partition, issue still exist.
2) Perform the Samsung factory reset by enter *2767*3855# in the Memo, problem still there.
3)Format the SD card with Phone & Windows, still got problem
4) Flashed with the stock EA24 Rom from XDA(with Modem,using Odin), the problem still remain the same.
5)Flashed with DJ30, the problem still exist(Base/Fireware EA24).
6)Tried to install CWM, failed to boot up(Rooted before install CWM, after flash the Zimage to Kernal or recovery, some strings flush in the screen, then the tab hung at Samsung logo and reboot.)
I guess those problem was caused by some program information still remain in the internal storage, even after factory reset or flash with other ROM.
Can somebody help on this? Also prefer someone can help on how to install CWM
I am interesting that the OVERcome 2.01 Rom got a version to WIPE the internal storage, but the OVERcome rom are designed for GSMer. Can i tried to use it to clear my internal storage?
just installed Astro, the program will crashed when launch it
Can some one help on this topic?
I am suspecting my internal storage was locked to Non-Writable.
This might result CWM can not access the internal memory caused the failure of the installation.
Is it related to the Flash lock option in the Odin?
Check this thread..
http://forum.xda-developers.com/showthread.php?t=1133053
That has the stock files, and instructions to get root and CWM installed with the stock software. Using Odin to put the stock firmware (EA24) should wipe anything and everything off the tab and restore it to as if it were new out of the box. You also might want to wipe your sd card as it can cause issues with the CWM ext4 conversion.
Hi pvtjoker42 & All:
During the process of Kernel with CWM Recovery, i has been stopped @ step7
1) Download the zip file here
2) Unzip the file. You will need the file named zimage only.
3) Open Heimdall Frontend
4) Select Browse under Kernel and navigate to the file you downloaded in step 1 and select it
5) Press Start
6) The Tab will reboot, but will freeze on the Samsung logo. Turn it off and boot into recovery (Vol Up + Power)
~~~~~~~~~~~~~~~~~~~~
my tab failed here, no matter what you pressed, it doesn't go to CWM. Do u have any idea?
~~~~~~~~~~~~~~~~~~~~
7) CWM Recovery will attempt to back your tab up, but will fail. Don't fret.
8) Do a factory reset in CWM Recovery and reboot
9) You'll freeze on the Samsung logo again Turn it off and boot into recovery.
10) CWM Recovery will back your Tab up successfully.
11) You now have a CWM backup. Reboot.
12) Your auto rotate is broken.
13) Download the rotation file
14) Put it in /system/lib/hw and change the permissions to match the other items.
Can someone helps?
Today i tried 1 more things, Use a update.zip to update the tab from EA24 to EB28,before try this, i have tried OTA to EB28, it never success.
i download the update.zip from <forum.sdx-developers.com/index.php?PHPSESSID=99sdnmh5pm4rtuv39hk80f7du6&topic=13104.0;nowap> it seems to be official one, and the recovery is the stock version, but it failed again.
I start to believe that my internal storage has been locked, and data can not write in.
Is it possible to due to Fstab issue?
Pls helps to save my tab....
There is only one thing to do : return to stock. Carefully follow the guide. Don't do anything else to your tab, until you go through the restock steps :
http://forum.xda-developers.com/showthread.php?t=1133053
[SPRINT] Sprint Tablet Owners Thread (Root, ROM, Flash to stock, CWM Recovery)
The process reformats/repartitions your internal sd card, and sets the correct permissions. If this process fails, there is probably something wrong with the tab.
you might also try to select the option to repartition in Odin when going back to EA24. Then try the steps to get EB28 OTA update, and once you've got that up and running, you can try the update.zip to get to EF17 (gingerbread, as long as you don't need root)
I wouldn't. Try a different sd card
Sent from my Nexus S 4G using Tapatalk
Hi All:
Thanks for the advice.
I have tried to back to stock EA24 using odin, but the situation still ramain the same.
And it fail to OTA to EB28, the EB28 upgrade program will reboot the machine, and enter recovery model. but it will complete the program. also i have tried to put EB28 update.zip in the SD card, but also fail to upgrade to EB28.
I have repartition the phone by P100 serveral time using odin, also tried update Pit file. All failed.
I have format the SD card in Windows & then in Android, useless.
Now i have some clues:
In P1000 rom Roto-JME, there is Movinand.bin, this one got same name as the internal storage IC from samsung. i am thinking that file could be a file similar to partition table.
Can someone help to dump a "movinand.bin" for me from P100?
steps:
1)Get back to stock EA 24
2)Wipe Cache & factory data
3) Root it (Using superone click , you can find it here http://forum.xda-developers.com/showthread.php?t=803682)
4)Install terminal (i use better terminal) or using a ADB to connect to shell.
5)Type "su", check whether "$" change to "#" in the shell
6) Type “dd if=/dev/block/mmcblk0p2 of=/sdcard/movinand.bin bs=4096”
7) Find the Movinand.bin in the SD card
You can sent it to me by drop a email to [email protected]
If there is anything wrong, pls help to correct me
Thanks in advance
as some people is asking how did i fix the issue, just publish the information here.
I fixed the issue by replaced the internal storage (the chip), cost about US$ 30(RMB 200)
If anyone have better solution, just post here to share
Hey guys!
I've been having a lot of problems with a Samsung Galaxy S Plus recently. After my girlfriend entered the wrong picture password a number of times in a row, the phone locked down. I tried to activate data connection using the power menu (hold power button), which I had deactivated before it locked down. My attempts to log in failed when the device returned either 'invalid username' or 'invalid password' (they are - of course - neither). This is apparently a known problem. I then followed the following instructions to trick the device into thinking the google account had been verified: droidwiki .de/Muster_vergessen#Muster_l.C3.B6schen (warning, that site is in German). For this I successfully managed the following steps:
1.) Installation of ADB tools
2.) Installation of ClockwordMod using Odin in order to accomplish the ...
3.) Activation of USB debugging.
4.) Rooting the phone using these instructions: androiddrole .com/how-to/how-to-easily-root-samsung-galaxy-s-plus-i9001
All these steps worked as expected. Then however, the trouble started: When trying to set the number of failed pattern attempts to 0, the following command failed: "cd /data/data/com.android.providers.settings/databases" ("can't cd to /data/data/com.android.providers.settings/databases"). Additionally I could no longer boot into android as the phone kept booting directly into CWM (This is apparently also a known problem). I proceeded to install a newer version of ClockworkMod Touch (using zip on sd card) hoping this would allow me to break the loop. It didnt. So I replaced ClockwordMod with TeamWin Recovery Project (TWRP). This did finally allow me to exit the recovery mode only to get stuck in a full-out reboot loop: Samsung logo -> black screen -> Samsung logo -> black screen. In order to get out of this reboot loop I used Odin to flash boot_loader.tar and the original version of ClockwordMod onto the device. After a number of failed attempts this suddenly worked - kinda:
The current situation is this: The phone no longer boots directly into recovery mode (good). It doesnt boot into android either though. It just reboots over and over again - this can be stopped however by using 'Volume Down' + 'Home' + 'Power' to access ClockwordMod.
My hopes of getting my phone unlocked and working as before again are rather slim at this point. I would still like to save my substantial collection of photographs from the media folders on the device, before I wipe the entire thing (or buy a new phone).
Therefore my question to you:
Is it possible to extract the photos (stored in the standard media locations of android 2.3) to a PC using only USB-Debugging/Odin/ClockwordMod (being unable to boot into android)?
I tried to pull the media files using the 'adp pull' command, but I couldnt get it to work (maybe because I didnt get the command or the file-paths correctly). Any suggestions would be GREATLY appreciated.
Solution
Attention: If you want your media files, backup your current state first. Go to backup and restore -> backup. Then do steps written below. Backup will be in CWM folder on your sdcard.
This is called a soft-brick. It's good that you can access download and recovery mode using 3 button combinations. First, download a stock Gingerbread ROM for your device model and put it on your sdcard. Boot into CWM and select Wipe user data -> Yes. Wipe Cache Partition -> Yes. Go to Advanced menu and select Wipe Dalvik cache -> Yes. Now return to previous menu and select install zip from sdcard -> choose zip from sdcard -> select name.of.downloaded.rom.zip -> Yes -> Wait 1-2 minutes to flash -> Wipe user data -> Wipe Cache Partition -> Wipe Dalvik Cache. Then select Reboot system now from main menu, and wait 4-5 minutes for it to boot first time.
DaniTheMan said:
Hey guys!
I've been having a lot of problems with a Samsung Galaxy S Plus recently. After my girlfriend entered the wrong picture password a number of times in a row, the phone locked down. I tried to activate data connection using the power menu (hold power button), which I had deactivated before it locked down. My attempts to log in failed when the device returned either 'invalid username' or 'invalid password' (they are - of course - neither). This is apparently a known problem. I then followed the following instructions to trick the device into thinking the google account had been verified: droidwiki .de/Muster_vergessen#Muster_l.C3.B6schen (warning, that site is in German). For this I successfully managed the following steps:
1.) Installation of ADB tools
2.) Installation of ClockwordMod using Odin in order to accomplish the ...
3.) Activation of USB debugging.
4.) Rooting the phone using these instructions: androiddrole .com/how-to/how-to-easily-root-samsung-galaxy-s-plus-i9001
All these steps worked as expected. Then however, the trouble started: When trying to set the number of failed pattern attempts to 0, the following command failed: "cd /data/data/com.android.providers.settings/databases" ("can't cd to /data/data/com.android.providers.settings/databases"). Additionally I could no longer boot into android as the phone kept booting directly into CWM (This is apparently also a known problem). I proceeded to install a newer version of ClockworkMod Touch (using zip on sd card) hoping this would allow me to break the loop. It didnt. So I replaced ClockwordMod with TeamWin Recovery Project (TWRP). This did finally allow me to exit the recovery mode only to get stuck in a full-out reboot loop: Samsung logo -> black screen -> Samsung logo -> black screen. In order to get out of this reboot loop I used Odin to flash boot_loader.tar and the original version of ClockwordMod onto the device. After a number of failed attempts this suddenly worked - kinda:
The current situation is this: The phone no longer boots directly into recovery mode (good). It doesnt boot into android either though. It just reboots over and over again - this can be stopped however by using 'Volume Down' + 'Home' + 'Power' to access ClockwordMod.
My hopes of getting my phone unlocked and working as before again are rather slim at this point. I would still like to save my substantial collection of photographs from the media folders on the device, before I wipe the entire thing (or buy a new phone).
Therefore my question to you:
Is it possible to extract the photos (stored in the standard media locations of android 2.3) to a PC using only USB-Debugging/Odin/ClockwordMod (being unable to boot into android)?
I tried to pull the media files using the 'adp pull' command, but I couldnt get it to work (maybe because I didn't get the command or the file-paths correctly). Any suggestions would be GREATLY appreciated.
Click to expand...
Click to collapse
I received as gift a samsung watch, that come with Tizen, I will describe how to do all the steps to install the custom rom.
I have a lot of problem and I write this to help all in special noobs like me.
(no wondershare, no root, no phone needed)
Things I used:
Odin 3.12 - Will write into rom of your device, in this case gear.
Stock Rom (Go to Sammobile, you will have to do a account) - "Rom original to install".
Null rom (don't get the 27, the last version is 23)
ADB
Samsung Drivers
In some cases:
SDB
Downgrade Tizen To Android
I will write the other steps bellow it's just too much things to do it.
I will came back to say all steps. and putting links and forum I was based.
Process
Steps
[Step USB Debuging](Gear)
[Preparation 1 - ADB and verify android](Windows)
[Preparation 1.1 - In case you have tizen installed](Windows)
[Preparation 2 - Intall custom recovery](Windows)
[Preparation 3 - Copying null_23 to sdcard](Windows)
[Installing Null rom 23](Gear)
[Step USB Debuging]
Unlock you phone, and enable usb debuging
You don't need to use a phone to do it. At any version of SO installed you can go without a phone.
In case you think you need the phone to go to configuration you don't need.
Press the touchscreen on the version of your watch, at least 10 times, then press and hold where is writed gear, and you will unlock the phone.
Go to configurations, about the phone select usb debuging.
If you are not seeing the usb debuging, then go to the menu and click 7 times on version, and will unlock the usb debuging.
Go back and enable usb debuging. If you having problems I do a tutorial, but send a picture of your watch and screen.
[Preparation 1](Windows)
First thing you need to know if you are using Android or Tizen OS.
Install Samsung Drivers, to recognize your gear, connect the gear to computer.
Install ADB, or download it.
Then open a terminal, windows + R type cmd and press enter.
Navigate ADB folder, and type adb devices, if no device is show and you have gear plugged and dock and at pc with the right part of gear at the dock, and Samsung drivers, maybe you are using Tizen.
You can't go on until you see the device at adb devices.
[Preparation 1.1](Windows)
In case you wanna see if you are using Tizen then:
Install SDB, or download it.
Then open a terminal, windows + R type cmd and press enter.
Navigate SDB folder, and type sdb devices, if are showing devices you are using Tizen and need to do a Downgrade to Android to continue the installation.
Download the downgrade, unzip and do as I say, because I was doing wrong and my touch stopped working, then I need to reinstall the stock rom.
[Go to download option]Hold power button for 10 seconds, than press it at least 10 times, press until download and then press for 3 seconds and released.
Open Odin, connect you gear to pc.
You have to see [com:X] to see that your gear is connect.
Than select the pit tab, select the file .pit inside the folder you unziped.
Select the file at AP that started with 1.
Uncheck all, and leave only Reset time and Repartion checked.
WAIT until you see PASS, don't remove it at RESET.
Please now you don't go again to download option, you have to go to recovery, if you don't do it your touch will not work, and you will need to reinstall stock and restart full proccess.
[Go to recovery option] Hold power button for 10 seconds, than press it at least 10 times, press until recovery and then press for 3 seconds and released.
[Black screen]You now have to see the lack screen of death to continue, it say you have to connect to Kies and stuff(Just don't do it).
Now at this black screen you can continue.
Close Odin, and open it again.
Select at Ap rom that started with 2, uncheck auto restart, and press start.
WAIT until Odin say to Pass, don't remove at RESET.
If every thing goes right you installed MK7, and can continue the proccess.
Reboot and do the step again [Step USB Debuging].
[Preparation 2 - Intall custom recovery](Windows)
You have android installed at your gear, if you don't have the mk7 version, please download it at sammobile, use odin with checked restart and reset time, and hit start.
Now with MK7 version you will install a modification to when you use the [Go to recovery option], and now will have another feature this recovery.
At this new feature you can install a custom rom, and this case we will install null23(that is the lastest version, do not install null27)
To do so you will install a custom recovery TWRP, this will only affect the recovery option of your rom.
Open Odin, select the twrp.tar, and hit start.
Wait for PASS, and reboot and do the step again [Go to recovery option].
Check if touch is working, if this is not working, and you did a downgrade you need to do it again, i did this step at least 10 times, and the problem was I wasn't doing exatcly as I said.
If touch work you can go to the next step.
[Installing Null rom 23](Gear)
Now if your recovery changed you can go to your new customized recovery.
[Go to recovery option]
Click at wipe.
Wait, and back to menu.
Install, look for null_23.zip
Click at it.
Now you are installing the custom rom.
End
Hope I Helped.
filipemelo said:
[Installing Null rom 23](Gear)
Now if your recovery changed you can go to your new customized recovery.
[Go to recovery option]
Click at wipe.
Wait, and back to menu.
Install, look for null_23.zip
Click at it.
Now you are installing the custom rom.
End
Hope I Helped.
Click to expand...
Click to collapse
In what step did you actually install null_23 onto the gear??? In recovery I see twrp folder, but null 23 is not under it. I'm stuck at this point because I can't put null 23 in my sd card so I can install it.