Related
i have a problem, for some reason i cant go to recovery mode. i have JFv 1.42_RC33... what can i do
What exactly do you mean by that? Have you tried booting into recovery straight from the terminal?
Iceucold said:
Have you tried booting into recovery straight from the terminal?
Click to expand...
Click to collapse
That made even less sense.
forgive me if im mistaken, but doesnt it have something to do with the bootloader as well?
kydcleric said:
forgive me if im mistaken, but doesnt it have something to do with the bootloader as well?
Click to expand...
Click to collapse
i dont know im new to this stuff but what happens is that the g1 boot screen pops up when i press home+power then it just restarts and shows the g1 boot screen again then it goes to the normal home screen
Iceucold said:
What exactly do you mean by that? Have you tried booting into recovery straight from the terminal?
Click to expand...
Click to collapse
i dont know what u mean
Sorry about that. I was referring to going into the terminal emulator and typing in the command:
Code:
# reboot recovery
Iceucold said:
Sorry about that. I was referring to going into the terminal emulator and typing in the command:
Code:
# reboot recovery
Click to expand...
Click to collapse
nothing happens i put that in there and it just shows a money sign under it.. and when i just put reboot it says
reboot: operation not permitted
You are holding down home first right? I.e. press home and hold it down and then press power(I continue to hold home down all the way up until I see recovery mode starting)
Can you check if the recovery image (/system/recovery.img) is intact?
if you're using the haykuro builds, it is known that reboot won't work from terminal emulator. but you should be able to reboot recovery through adb shell.
I remember I read somewhere that certain bootloaders have a different key sequence for recovery mode, but i've never seem any of them.
ooooo crap i just checked it and there is no recovery.img in there ok what do i do??
someone plz help me out
probably best to dl the one from the Rooting Hacking & Flashing... post. They have a link to the file there. Just dl it and, as su, copy it to the folder they say.
what post???
Cosine said:
what post???
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=442480
yea but thats only to get to root and i already did that... and i just tried it and it dosent work
Cosine said:
yea but thats only to get to root and i already did that... and i just tried it and it dosent work
Click to expand...
Click to collapse
The suggestion was to try restoring the recovery image as outlined in that thread: (though you shouldn't need to do the "telnetd" part)
Instructions:
1. Download recovery.img and copy it to your SD card (see the previous instructions on how to copy from your computer to your Phone's SD card).
2. Download the Hard SPL and copy the zip file to the SD card.
3. All files must be on the root of your SD card.
4. Restart your phone. Wait for your phone to start up fully and show the home screen.
5. After your phone starts up, hit the enter key twice, type "telnetd" and press enter. (Yes, it will start up a contact search, don't worry. Just type it.)
6. Download an Android "Telnet" application from the Market and connect to localhost.
7. If you connect successfully, you will have a root prompt "#".
8. Type the following into Telnet (these commands will give you root access easier in the future):
* mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
* cd sdcard
* flash_image recovery recovery.img
* cat recovery.img > /system/recovery.img
Now you have root!
Click to expand...
Click to collapse
so should i just try
8. Type the following into Telnet (these commands will give you root access easier in the future):
* mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
* cd sdcard
* flash_image recovery recovery.img
* cat recovery.img > /system/recovery.img
in the terminal emulator
I know you had to push a reboot file to get it working on some Hero ROMs. What about the EVO version?
The Hero way works.
FIRST, install Quickboot from the market. Run it and enable it in the superuser permissions screen.
Download the reboot.txt file I attached and rename it to "reboot" (take off the ".txt"). Move it to where ever your "android-sdk-windows/tools" folder is.
Connect your phone to your computer (make sure it is "charge only") and boot into recovery...
Code:
adb shell
reboot recovery
Start your "Windows-recovery.bat" (if using windows) and let it do it's thing in the CMD prompt. Keep that prompt open.
In a CMD prompt OTHER THAN the one opened by recovery.bat type...
Code:
adb shell
mount /dev/block/mtdblock4 /system
exit
This will keep your system mounted but get you out of shell. Now type...
Code:
adb push reboot /system/bin
adb shell
cd /system/bin/
chmod 755 reboot
reboot
Once you're back up, run Quickboot and choose either reboot or recovery (both will now work). It takes about 5 seconds to start rebooting but it does work.
What does this do? does it make recovery stick?
watzone69 said:
The Hero way works.
Download the reboot.txt file I attached and rename it to "reboot".
Once you're in recovery...
Code:
adb push reboot /system/bin
adb shell
cd /system/bin/
chmod 755 reboot
reboot
EDIT: It takes about 5 seconds to start rebooting but it does work.
Click to expand...
Click to collapse
Woo! Thanks!
Edit: Didn't seem to work for me. Damn.
joeavery2 said:
What does this do? does it make recovery stick?
Click to expand...
Click to collapse
No, this just lets you use the QuickBoot app from the Market to reboot your phone.
TheBiles said:
Didn't seem to work for me. Damn.
Click to expand...
Click to collapse
Code:
adb shell
cd /system/bin/
ls
See if the reboot file actually got pushed to the directory. If so, try this:
Code:
chmod 755 /system/bin/reboot
The only other thing I can think of is that I installed Quickboot BEFORE doing all of this. Did you get the SU permission screen when you tried to run it?
Any luck??
Did I mention that the Quickboot "recovery" button works also? Much easier than opening a shell and typing it in.
Of course you still have to run the recovery.bat to get the custom recovery but at least it's one less step.
Still no dice. I also already had QuickBoot installed and granted it root permission prior to pushing the reboot file.
any update to this?
thanks
joey3002 said:
any update to this?
thanks
Click to expand...
Click to collapse
It doesn't work for you?
I updated my earlier post to give more instructions for getting into recovery and pushing the "reboot" file. I hope it helps!
I have a ROM ready to go that changes a couple icons and quickboot works with no probelm. Wifi tether is the only thing I don't have working. I can post it if you would like. I also removed sprint apps and some widgets
I made an update zip that got Quickboot working for me. This is using watzone69's reboot file.
Run from Toast's recovery. http://forum.xda-developers.com/showthread.php?t=690762
watzone69 said:
It doesn't work for you?
Click to expand...
Click to collapse
yes i got it working last night by reading this thread from top to bottom.. then repeated.. thanks
Do it at your risk!
Hi,everybody.
I had successfully ported CWM recovery&Bootmenu 2ndinit for spice,which allows us to use custom rom.
Now,you have two ways to use CWM recovery.One is entering CWM recovery through bootmenu,the another way is entering CWM recovery through stock recovery(Fake flash update zip).
Method 1:Through bootmenu
First of all,you need to root your spice.And then install bootmenu.
Download the bootmenu.tar file(attached).And push it into /sdcard/
Turn on usb debugging on your phone. And use the following commands in adb:
Code:
C:/> adb shell
$ su
# mount -o remount,rw /dev/block/mtdblock1 /system
# mkdir /system/bootmenu
# cd /system/bootmenu
# busybox tar -xf /sdcard/bootmenu.tar
# rm /system/bin/charge_only_mode
# busybox ln -s /system/bootmenu/binary/bootmenu /system/bin/charge_only_mode
# sync
# mount -o remount,ro /dev/block/mtdblock1 /system
# exit
The bootmenu will be installed.
Restart your device once.
Using Boot Menu:
Turn your phone off.
Press the Power Button.
After 1-10 seconds, the red led on your phone will light up for just 3 seconds (Still while the Motorola logo is being displayed).
Exactly when the led lights up, press the volume down button.
You will see the BootMenu, use the Volume Button to navigate up and down, and the power button to select an item.
Then you can select enter CWM recovery.(Someone say CWM's backup&restore cannot work,you can use method 2 for it)
Method 2:Through stock recovery(Fake flash zip)
I found that we can use CWM recovery with stock recovery leak(Fake flash update zip,like OpenRecovery),but this leak is only existed in SESGC_U3_10.10.0_RT firmware.
I have dumped this recovery(Attached file:recovery.img).And flash it by fastboot.It works well with SESLA_U3_01.72.0 firmware.
And then to flash a fake update.zip(Attached file:update.zip) from the root of your sdcard,you will enter CWM recovery!
By the way,if you want to port CM7 for spice,you need to use 2ndinit for your froyo/gingerbread,because it has locked bootloader.
I have compiled CM7 for it,and it can boot up but stuck in white screen after CM bootanimation.If you want to continue my work,you can checkout my github.
Thanks to:
CyanogenMod
koush
...
sorry for my poor English.
With the first method i can't make a nandroid backup, i'll try it with the second!
Nand backup question
GentryLamp said:
Do it at your risk!
Hi,everybody.
I had successfully ported CWM recovery&Bootmenu 2ndinit for spice,which allows us to use custom rom.
Now,you have two ways to use CWM recovery.One is entering CWM recovery through bootmenu,the another way is entering CWM recovery through stock recovery(Fake flash update zip).
Method 1:Through bootmenu
First of all,you need to root your spice.And then install bootmenu.
Download the bootmenu.tar file(attached).And push it into /sdcard/
Turn on usb debugging on your phone. And use the following commands in adb:
Code:
C:/> adb shell
$ su
# mount -o remount,rw /dev/block/mtdblock1 /system
# mkdir /system/bootmenu
# cd /system/bootmenu
# busybox tar -xf /sdcard/bootmenu.tar
# rm /system/bin/charge_only_mode
# busybox ln -s /system/bootmenu/binary/bootmenu /system/bin/charge_only_mode
# sync
# mount -o remount,ro /dev/block/mtdblock1 /system
# exit
The bootmenu will be installed.
Restart your device once.
Using Boot Menu:
Turn your phone off.
Press the Power Button.
After 1-10 seconds, the red led on your phone will light up for just 3 seconds (Still while the Motorola logo is being displayed).
Exactly when the led lights up, press the volume down button.
You will see the BootMenu, use the Volume Button to navigate up and down, and the power button to select an item.
Then you can select enter CWM recovery.(Someone say CWM's backup&restore cannot work,you can use method 2 for it)
Method 2:Through stock recovery(Fake flash zip)
I found that we can use CWM recovery with stock recovery leak(Fake flash update zip,like OpenRecovery),but this leak is only existed in SESGC_U3_10.10.0_RT firmware.
I have dumped this recovery(Attached file:recovery.img).And flash it by fastboot.It works well with SESLA_U3_01.72.0 firmware.
And then to flash a fake update.zip(Attached file:update.zip) from the root of your sdcard,you will enter CWM recovery!
By the way,if you want to port CM7 for spice,you need to use 2ndinit for your froyo/gingerbread,because it has locked bootloader.
I have compiled CM7 for it,and it can boot up but stuck in white screen after CM bootanimation.If you want to continue my work,you can checkout my github(["github . com/gentrylamp").
Thanks to:
CyanogenMod
koush
...
sorry for my poor English.
Click to expand...
Click to collapse
Hello!
Mr GentryLamp, congratulations done, I do not see many people who understand Android programming interested in XT300, you're the man!
I performed all the procedures above, installed bootmenu (but renamed the "charge_only_mode" as "charge_only_mode.bin" the backup purposes), I installed the old recovery with flash_image (command "flash_image recovery path_of_recovery _.img") and put the update.zip on the root of SD.
I can not perform with nand backup recovery from bootmenu (advance notice, and obviously non-functional), and the second way does not work (the leakage update.zip).
When trying to nand backup the nand, the device is the screen backuping ("SD memory free... Backup system...") For about an hour, and then the screen goes white, and end.
You know how I could accomplish this nand backup? You got on your device? Do you know any script that I can use for it?
If you need more information, or something that I test on my device, I place myself at your disposal.
Sorry my english too, Google Translate help much Brazilians.
Hug.
Regisboliver said:
Hello!
Mr GentryLamp, congratulations done, I do not see many people who understand Android programming interested in XT300, you're the man!
I performed all the procedures above, installed bootmenu (but renamed the "charge_only_mode" as "charge_only_mode.bin" the backup purposes), I installed the old recovery with flash_image (command "flash_image recovery path_of_recovery _.img") and put the update.zip on the root of SD.
I can not perform with nand backup recovery from bootmenu (advance notice, and obviously non-functional), and the second way does not work (the leakage update.zip).
When trying to nand backup the nand, the device is the screen backuping ("SD memory free... Backup system...") For about an hour, and then the screen goes white, and end.
You know how I could accomplish this nand backup? You got on your device? Do you know any script that I can use for it?
If you need more information, or something that I test on my device, I place myself at your disposal.
Sorry my english too, Google Translate help much Brazilians.
Hug.
Click to expand...
Click to collapse
I haven't confirmed whether NAND backup will work in bootmenu,but it works well in fake update.zip way.
If your firmware version is SESLA_U3_01.72.0,you need to boot the phone into fastboot mode(bule screen,pressing Vol-up&Vol-down while the phone boots up),and using fastboot to flash recovery.img.
BTW:Some firmware(such as SESGC_U3_10.10.0_RT) do not allow fastboot.You can see some warnings in fastboot bule screen.
More questions...sorry
GentryLamp said:
I haven't confirmed whether NAND backup will work in bootmenu,but it works well in fake update.zip way.
If your firmware version is SESLA_U3_01.72.0,you need to boot the phone into fastboot mode(bule screen,pressing Vol-up&Vol-down while the phone boots up),and using fastboot to flash recovery.img.
BTW:Some firmware(such as SESGC_U3_10.10.0_RT) do not allow fastboot.You can see some warnings in fastboot bule screen.
Click to expand...
Click to collapse
Thanks for reply man o/
My firmware is SESLA_U3_01.72.0, nand backup really not work on first method, and in the second method, also not .
I followed a guide like this: [ht tp:// forum . xda-developers . com/showthread.php?t=918275]. I believe the command is flash_image the same effectiveness as the fastboot, because I could run the CWM_recovery from the update.zip (you said that this gap is only SESGC_U3_10.10.0_RT recovery firmware, and I do not use - no clue of what it is, just know mine, and Chinese MONSTER).
But I saw now that you've lost your XT300 and therefore believe that there is no possibility to test or you do something for it. But anyway, I am grateful and even my disposal device testing, if desired.
Taking advantage ... would be able to put an 'if' that is, the low volume was not pressed, he continued with the 'charge_only_mode', so that the battery could be charged with the device off? I would also like to know if you know if it is possible to make a nand backup from a script, with the connected device, and if you have some kind of script ...
Excuse me for asking so many questions to you is that I know someone who knows and is as interested as you.
Thank you!
Hug.
i had the same problem with NAND backup using method 2
Regisboliver said:
the low volume was not pressed, he continued with the 'charge_only_mode', so that the battery could be charged with the device off?.
Click to expand...
Click to collapse
The phone will not enter charge only mode when you install bootmenu.
In method 2,NAND Backup&Restore works well when I use spice,I'm sorry that it doesn't work with some phone.
GentryLamp said:
The phone will not enter charge only mode when you install bootmenu.
In method 2,NAND Backup&Restore works well when I use spice,I'm sorry that it doesn't work with some phone.
Click to expand...
Click to collapse
I understand that only with bootmenu the device not charge without boot but, my question was would like to know if one can apply this procedure to boot: power button pressed > magenta led light and Motorola logo > {(before bootanimation and bootinstructions) volume down button pressed while red led light? "yes? -> bootmenu" | "no? -> execute the real charge_only_mode binary", execute charge_only_mode.bkp for example, in my case, since renamed the original charge_only_mode for subsequent restoration of boot } > boot. Understand my question? :s
But if there is, I made two scripts, one for installation and uninstallation of another bootmenu (if someone wants I can post), but if you do not give to run the above algorithm, I use the update.zip CWM_recovery the same, so I can recharge my device is switched off, while I find I try to do a custom for 2ndinit.
Mr GentryLamp, you said above, in the opening thread, it has ported a CM7 for XT300 and it crashed after the Motorola logo. I some time ago, I replaced the file libGLES_android.so (in the folder / system / lib / egl), trying to enable the GPU, I fear there is not even in the chipset of XT300 and while on the Motorola logo, the screen was white, blinking. You keep intact the lib folder? Forgive me if I did wrong or very noob question, because I have no expertise in ROM switches, ports, CM, etc...
Regarding the nand backup, searched about it here, to see if I can find at least one script for it, because then I can become more peaceful to test changes more dangerous, not bothering with RDS, SBF ...
Thanks again bro!
Is there a way to port to other Motorola devices? I have a DROID x that I need to try this on because it is stuck in safe mode. How did you port this to flash in stock recovery?
Sent from my DROID4 using Tapatalk 2
Great job, but I think this work is not useful because we don't have a custom Rom for this phone and the stock Rom sucks, I have this xt300 from my carrier iusacell Mexico, and is so slow and to f**king buggy, if is thera a chance to have a good froyo or gingerbread stable Rom will be perfect this phone have some potential but is too capable by the Motorola software
I hope we can some time get a good Rom for this great and cheap phone
hi...i'm searching on how to fix booting problem on my note 2 clone??? i think i have brick my phone when i trying to chnage font using font installer....now it stuck on android logo...does anyone know how to fix the problem??? thanks in advance
Anyone??
Sent from my R800i using Tapatalk 2
Bump!!! Help plss...
Sent from my R800i using Tapatalk 2
spec
spec
Why did you post 4 times?
sent from my minecraft world
CasTTeLLo said:
hi...i'm searching on how to fix booting problem on my note 2 clone??? i think i have brick my phone when i trying to chnage font using font installer....now it stuck on android logo...does anyone know how to fix the problem??? thanks in advance
Click to expand...
Click to collapse
turn off your phone, press volume up +home key + Power on. you are on 3e screen. then "wipe data / factory reset" then reboot.
*Note: that this will format your phone to factory default. and delete all your data.
still not working
ronnylaborada said:
turn off your phone, press volume up +home key + Power on. you are on 3e screen. then "wipe data / factory reset" then reboot.
*Note: that this will format your phone to factory default. and delete all your data.
Click to expand...
Click to collapse
i try to enter recovery sytem but still no luck....still stuck @ android logo after reboot...
note2 clone
CasTTeLLo said:
i try to enter recovery sytem but still no luck....still stuck @ android logo after reboot...[/QUOTE
u have test to volume up hole+back button hole+power button hole...
Click to expand...
Click to collapse
I have same problem with my friends note 2 clone.. Can't fix yet... Bookmarking this page...
same problem
i have also the same problem, please help me if you get rid of it
CasTTeLLo said:
hi...i'm searching on how to fix booting problem on my note 2 clone??? i think i have brick my phone when i trying to chnage font using font installer....now it stuck on android logo...does anyone know how to fix the problem??? thanks in advance
Click to expand...
Click to collapse
try this service code :-
*#*#10086#*#*
if its ok let me know.
regards
If you have busybox installed on your android and adb shell on your pc try this script
Code:
echo " "
echo "Waiting for device..."
adb wait-for-device
echo " "
adb -d shell su -c "mount -o rw,remount /system"
adb -d shell su -c "ls /system/fonts"
adb -d shell su -c "mv /system/fonts/FONT_NAME.EXTENSION /system/fonts/NEW_FONT_NAME.EXTENSION"
The ls command lists the names of the fonts in /system/fonts directory and now try renaming them one by one using the script. You must replace "FONT_NAME.EXTENSION" with the one find after ls command. If after renaming the first file doesn't work run the script again with the following font name and so on.
Take out the battery and put it in and quickly hold the buttons that put you into stock recovery
Sent from my SGH-T959V using xda app-developers app
I'm trying to reboot from terminal emulator. What I type is:
Code:
su
reboot
or
Code:
su
reboot -p
but it always returns
Code:
Not permited
.
Note that I get the same "Not permited" both with gaining and not gaining su access before executing the reboot command.
This is a known problem (see here for example) but I haven't been able to find a solution.
Of course, root is working fine on my rom so that's not the problem.
Anyone using reboot from terminal emulator?
Thanks
nor-ric said:
I'm trying to reboot from terminal emulator. What I type is:
Code:
su
reboot
or
Code:
su
reboot -p
but it always returns
Code:
Not permited
.
Note that I get the same "Not permited" both with gaining and not gaining su access before executing the reboot command.
This is a known problem (see here for example) but I haven't been able to find a solution.
Of course, root is working fine on my rom so that's not the problem.
Anyone using reboot from terminal emulator?
Thanks
Click to expand...
Click to collapse
Entering commands
Code:
su
reboot
reboot the phone for me. I'm on latest Carbon rom.
You could try
Code:
su
shutdown -r now
but that will probably have the same result...
Is there a specific reason you want to be able to reboot from terminal? If you are looking for quicker access to recovery or bootloader and are using an AOSP rom you could enable the advanced reboot menu in developer options to get those options from the power menu. Hope this helps.
zaak00 said:
You could try
Code:
su
shutdown -r now
but that will probably have the same result...
Click to expand...
Click to collapse
It instantly reboots, without the proper shutdown routine.
UnspecialEffects said:
Is there a specific reason you want to be able to reboot from terminal? If you are looking for quicker access to recovery or bootloader and are using an AOSP rom you could enable the advanced reboot menu in developer options to get those options from the power menu. Hope this helps.
Click to expand...
Click to collapse
I'm on stock rom and I suspect that's the source of the problem: infact in the thread I linked above the user is on a stock HTC One.
I'd like to do it from terminal so that I can create a reboot event on Tasker/Llama.