Related
Dear XDA-Helpers,
First of all I want to apologize. Because likely the most of you will think the answers on my question are already posted. But I've searched and searched and I don't have found the solution. (Yes I saw this thread too: http://forum.xda-developers.com/showthread.php?t=487187 It's the same question but that didn't help too.)
So this is what I did:
I wanted to test out the Eclair 2.0 Rom, so I flashed that over Cyanogen. Then I wanted back to 1.6, and used this method. ( http://www.gphone.org.hk/cgi-bin/ch/topic_show.cgi?id=60&bpg=1&age=0)
So I was on 1.5 and rooted with the one click method. Then I flashed the signed-dream_devphone_userdebug-ota-14721.zip ROM. When that was finished I reboot my G1, and then I wanted to flash Cyanogen, but when I went back to recovery mode, the orignal HTC recovery was back and I was unrooted, now I also cannot flash any DREAIMG.nbh because when I go in bootloader it says "not allowed".
I really don't know what to do now.
Some specs about my G1:
Android G1 with Donut 1.6
Kernel Version: 2.6.29-00479-g3c7df37 [email protected] #19
Build Number: dream_devphone-userdebug 1.6 DRC83 14721 test-keys
About the error of the bootloader:
0028002 not allowed
DREA110 PVT 32B
HBOOT-0.95.0000
CLPD-4
RADIO-2.22.19.261
Sep 2 2008
serial0v
Thanks!
You're not unrooted. You just didn't read the instructions carefully enough.
Use fastboot to flash a modified recovery (I prefer CM's).
Code:
start your phone in fastboot usb mode.
fastboot flash recovery recovery.img
fastboot reboot
Once that is done, go into the recovery and you can flash roms again.
This time FOLLOW the instructions...
After you've flashed the htc recovery image, do NOT restart the phone, simply flash cyanogens rom right after that, THEN reboot.
next time please post in the QnA section
you might also like to try RA-Dream-v1.5.2 - there are lots of extra options in there like partitioning your card for swap, apps2sd etc
garok89 said:
next time please post in the QnA section
you might also like to try RA-Dream-v1.5.2 - there are lots of extra options in there like partitioning your card for swap, apps2sd etc
Click to expand...
Click to collapse
Sorry for wrong section, I was used to use RA-Dream recovery, but since I don't have root anymore, I cannot flash a other recovery..
Bavilo said:
You're not unrooted. You just didn't read the instructions carefully enough.
Use fastboot to flash a modified recovery (I prefer CM's).
Code:
start your phone in fastboot usb mode.
fastboot flash recovery recovery.img
fastboot reboot
Once that is done, go into the recovery and you can flash roms again.
This time FOLLOW the instructions...
After you've flashed the htc recovery image, do NOT restart the phone, simply flash cyanogens rom right after that, THEN reboot.
Click to expand...
Click to collapse
Well, when I typ 'su'/'sudo' in Terminal Emulator, it says no permission or something, so I think I don't have root anymore.. will your method fix my Bootloader? I used to get a screen with some skateboard but now I get a screen with a few colours.. and then it says 'not allowed'
Well when you flash the htc recovery image and then reboot the phone it will flash the stock recovery. That's why you need to flash cyanogens rom right after it.
But I don't really see why you're at the stock bootloader again now.
So you're on 1.6 with the stock bootloader? And the bootloader won't flash the .NBH, Looks like you need a goldcard.
Thanks for your answer!
Bavilo said:
Well when you flash the htc recovery image and then reboot the phone it will flash the stock recovery. That's why you need to flash cyanogens rom right after it.
But I don't really see why you're at the stock bootloader again now.
So you're on 1.6 with the stock bootloader? And the bootloader won't flash the .NBH, Looks like you need a goldcard.
Click to expand...
Click to collapse
yes I'm on 1.6 with the coloured boot loader and I can't flash a .NBH file, it says not allowed. What is a goldcard? You mean this? http://revskills.de/pages/goldcard.html
It says I need to give them my SD Card Serial (CID), but I have no idea what it is and where I can find it..
Here now the problem is that you cannot flash anything from the bootloader coz its telling 'Not allowed' And not even flash through recovery coz its the non - Rooted Stock one...
So here you go may be this would help you to get out of this problem.
First try this...
1. Get Amon_RA Recovery image into any folder.
2. Then Start your Phone in Boot loader mode
3. Open Command Prompt on your PC (Windows > Run > Type 'cmd' > Enter)
4. Browse to the folder where the Recovery image is located using cd <folder>
5. Connect the Phone to the PC via USB
6. Type fastboot boot <recovery_img_name.img> in the cmd window.
The Phone may boot into the Rooted Recovery...
If Not Try this..
Remember when G1 was first rooted ?
We had to type telnetd and then it installed the telnet application...
Try it...
Put the downloaded recovery image into the sdcard means /sdcard/recovery.img
1) Go to the Terminal emulator & type "telnetd" and press enter.
2) Press Home
3) Goto the market and download "Telnet"
4) Open Telnet and connect to localhost : 23
5) Press enter and you should see a #
6) Now type the following and press enter at the end of each line
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery cm-recovery-1.4.img
cat /sdcard/recovery.img > /system/recovery.img
7) Now try going into Recovery mode hope this might work...
Then Post ur info here...
Thank you!
sangeet.003 said:
Here now the problem is that you cannot flash anything from the bootloader coz its telling 'Not allowed' And not even flash through recovery coz its the non - Rooted Stock one...
So here you go may be this would help you to get out of this problem.
First try this...
.....
If Not Try this..
...
Then Post ur info here...
Click to expand...
Click to collapse
Thank you for your answer!
The first method did not work because, when I go in Bootloader my PC don't detect that the G1 is connect, it just don't do anything.
The second method didn't work too, because when I typ in terminal 'telnetd' it says no permission...
He can't flash from the boot loader as he doesn't have the engineering boot loader installed.
The other option might work though. If not, a goldcard will be the only way out.
This process is a bit tricky though.
First of all you will need the cid of your sdcard, to get this, type the following command in the terminal emulator.
Code:
cat /sys/class/mmc_host/mmc1/mmc1:*/cid > /sdcard/serial.txt
The cid will be saved within the root directory of your sdcard.
Now comes the tricky part, you need to reverse the string byte-wise. Here is an example.
This is what your cid can look like.
Code:
03534453553038478021021a320087be
Now split it up in pairs.
Code:
03|53|44|53|55|30|38|47|80|21|02|1a|32|00|87|be
Next, reverse the string byte-wise.
Code:
be|87|00|32|1a|02|21|80|47|38|30|55|53|44|53|03
Your reversed cid will look like.
Code:
be8700321a0221804738305553445303|
Now, take that cid and plug it into the goldcard generator you posted earlier and enter your email.
https://ssl.webpack.de/revskills.de/pages/goldcard.html
You will be send an goldcard.img file.
This last part is important and requires knowledge with linux and the dd command
1. Format your sdcard with Fat32.
2. Open a shell and type dd if=location_of_goldcard/goldcard.img of=/dev/sdx(where x is the letter that stands for your sdcard)
3. When it gives you a prompt saying the write was successful, drag the .NBH to the root of the sdcard, plug it in your G1, and try again.
You are welcome to hit me up on MSN if you need further assistance.
thierrz said:
Thank you for your answer!
The first method did not work because, when I go in Bootloader my PC don't detect that the G1 is connect, it just don't do anything.
The second method didn't work too, because when I typ in terminal 'telnetd' it says no permission...
Click to expand...
Click to collapse
That's because you're on 1.6. I believe this only worked in 1.0 where the keyboard was attached to a root console, so anything you typed on the keyboard would go straight to the console with root permissions. This flaw has been fixed.
Bavilo said:
Code:
cat /sys/class/mmc_host/mmc1/mmc1:*/cid > /sdcard/serial.txt
Click to expand...
Click to collapse
And again, permission denied
Problem solved, a goldcard was needed.
This thread can be closed.
Solved!
okay, it's solved! Thanks to Bavilo for helping me out on msn
Thanks al others for helping!
I Have The G1 aka Dream, i wanted to upgrade my recovery mode I tried
- via terminal -> Requires root
Code:
Copy recovery-RA-sapphire-v1.5.2H.img to the root of your sdcard
start the terminal app
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-sapphire-v1.5.2H.img
- after i wrote the last part and pressed enter nothing happen - so after that i power off - tried going to recovery mode - NO RECOVERY MODE just T Mobile G1 LoGo - Now i Have NO RECOVERY IMAGE At all - What can i do?
DrLfresh81 said:
I Have The G1 aka Dream, i wanted to upgrade my recovery mode I tried
- via terminal -> Requires root
Code:
Copy recovery-RA-sapphire-v1.5.2H.img to the root of your sdcard
start the terminal app
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-sapphire-v1.5.2H.img
- after i wrote the last part and pressed enter nothing happen - so after that i power off - tried going to recovery mode - NO RECOVERY MODE just T Mobile G1 LoGo - Now i Have NO RECOVERY IMAGE At all - What can i do?
Click to expand...
Click to collapse
hmm, that recovery is for the sapphire/magic, not for the g1...if you can't get to anything other than g1 screen with home and power or camer and power, then you bricked your phone.
??
what can i do with cam/end button? i know thats the gree/red/blue but what can i do on that mode?
Put the RC29 file back on your SD (DREAIMG.nbh or however it is spelled) reflash it using that green/red/blue screen (also known as the rainbow screen). re-root and use the right recovery image this time
DrLfresh81 said:
what can i do with cam/end button? i know thats the gree/red/blue but what can i do on that mode?
Click to expand...
Click to collapse
yeah, that is fastboot mode and you can flash stuff from it, just put the recovery on the sd card with nothing else and turn it on into fastboot (camera and power)
so back when i had 1.5 on my hero i had no problem at all installing roms. so when i updated to 2.1 stock awhile back i tried to root it and install a rom on it with the command prompt and unevoked method. it got it rooted and when i got to the recovery menu i nanidroid backedup and wiped and installed it. it then got stuck on the htc boot screen so i tried different rom and still would hang on it. so i said screw it and stayed on stock. i then later used the unlock univeral to root it but i can not stand the stock rom it is so slow and lags so i tried the offiical htc update from .6 to .7 to see if it would be faster but once it downloaded and i pressed install it would yet again hang on the htc screen. i cant even make calls with out lagging. so i tried once more to install 2.2 on it with a recovery img. i download rom manger and put froyo on the sd card but it would yet again hang when i click install rom from sd card. what do i do?!!!!!
update: i tried doing it through the teminal but it say flash_recovery not found
so i tried to do it through rom manger and it did the back up and installed it through the recovery menu but once it was done and rebooted it yet again is stuck on the htc boot screen.
help please!
It might b the recovery ur using if your able to boot into any rom access terminal you can get it from the market try to flash a different recovery I recommend. Darchstar RA 1.6 once u download it place it on the root of ur SD card not in any folders / then open up terminal and type su once the # appears type flash_image recovery /sdcard/ recovery- name of recovery. img wen that's done type reboot recovery and you should boot into recovery then try and flash ur rom from there hope this helps good luck
Root-Hack-Mod-Always™
laie1472 said:
It might b the recovery ur using if your able to boot into any rom access terminal you can get it from the market try to flash a different recovery I recommend. Darchstar RA 1.6 once u download it place it on the root of ur SD card not in any folders / then open up terminal and type su once the # appears type flash_image recovery /sdcard/ recovery- name of recovery. img wen that's done type reboot recovery and you should boot into recovery then try and flash ur rom from there hope this helps good luck
Root-Hack-Mod-Always™
Click to expand...
Click to collapse
ill try this when i get home tonite. thanks!
i tried doing it through the teminal but it say flash_recovery not found
so i tried to do it through rom manger and it did the back up and installed it through the recovery menu but once it was done and rebooted it yet again is stuck on the htc boot screen.
I recommend you boot into recovery - wipe your system / cache / dalvik cache and then flash the 2.2 rom of your choice -
if you were just flashing rom after rom without flashing then that could be a lot of your troubles -
also - you mentioned that the recovery file was not found on your sdcard - did you remember to unzip it first before attempting to flash it through terminal emulator? because it wont work otherwise ...
if you have extracted it to the root of your sdcard you shouldnt have any trouble
type
su
flash_image recovery /sdcard/nameofyourrecovery.img
reboot recovery
and you should be good to go - let me know how you do and we'll see if we can't help you further if needed
good luck!
cbwhat said:
i tried doing it through the teminal but it say flash_recovery not found
Click to expand...
Click to collapse
did you type:
su
flash_image recovery /sdcard/yourrecovery.img
or su
flash_recovery like your post shows - because you dont want to do it like that - just checking -
Vandelay007 said:
did you type:
su
flash_image recovery /sdcard/yourrecovery.img
or su
flash_recovery like your post shows - because you dont want to do it like that - just checking -
Click to expand...
Click to collapse
no it i type in
su
flash_image recovery /sdcard/recovery7.img
flash_image not found
cbwhat said:
no it i type in
su
flash_image recovery /sdcard/recovery7.img
flash_image not found
Click to expand...
Click to collapse
you said that you are doing this in a terminal window? (i am assuming that is on the phone) is your phone connected via usb to your computer? is the sdcard mounted by the computer? if it is unplug the usb and try again. if the computer has mounted the sdcard you can't access it from the phone.
i dont have it plugged in when i use the terminal on the phone
cbwhat said:
i dont have it plugged in when i use the terminal on the phone
Click to expand...
Click to collapse
ok just checking.... that was the only thing that i could think of that would stop you from reading the sdcard.
It may sound silly, bt when I do it I always make sure I account for case sensitivity...
Like flash_image recovery /sdcard/RA-Darchstar.img
Have you tried that?
Sent from my HERO200 using XDA App
yep make sure everything that has a capitals in it i capitalized in the terminal
this may sound silly as well.. sometimes when i use adb to push i mistype the location for example: adb push myfile.ext /adcard
everything goes fine until i go to find the file....
don't know though.
i still can't figure out how to install a custom rom.
Try backing up you sd and reformatting it on ur pc then just place the recovery img on your sd and nothing else then try to flash it good luck feel free to pm me I know how u feel man so if I can help I will good luck
Root-Hack-Mod-Always™
Hello, as I said in the title, I have a problem with the recovery menu (Same with OR) - problem is I can boot in recovery (the screen with the triangle) but there can not go to the menu. I press Volume Up + camera and nothing happens. Remains the same screen with the triangle and phone.
Please give me a solution because my phone is moving very slowly with Android 2.2.x
Device - Motorola a853 Milestone
Bootloader - 90.78
Button on the camera work, as well as the volume.
What could be the problem?
Sorry for bad English ..
Come on guys, 26 views and no response to my question?
I searched all forums and tried all the solutions posted there, but none worked! But those were old solutions ...
No one knows who could be my problem?
Not sure what kind of problem you are facing. You can surely try this.
Looks like OR is not loading in ur case. You can download the latest OR, I'm using minimod OR, copy the update.zip file into the root of SD card, again reboot into recovery. If u find ur milestone stuck in triangle button try pressing volume up button. This time it should invoke the OR or it should ask u to update the zip file.
Still if it doesnt works i think u have to take advice from experts who can help u to use ADB comnands to troubleshoot further. Anyways best of luck.
Sent from my Milestone using xda app-developers app
like the last post, you should verify if you have OpenRecovery folder and update.zip file in your /sdcard.
You can try via adb or terminal emulation "reboot recovery"
I tried what you said nagabushan.c, but it does not work ... Always the same problem, no menu displays..
At least do u get exclamatory mark when u booted or milestone while pressing camera button ? Then give a sec gap and then press volume up button.
Any device both rooted or non rooted should display this.
Try ADB steps..
Let us know what u observe
Sent from my Milestone using xda app-developers app
nagabushan.c said:
At least do u get exclamatory mark when u booted or milestone while pressing camera button ? Then give a sec gap and then press volume up button.
Any device both rooted or non rooted should display this.
Try ADB steps..
Let us know what u observe
Sent from my Milestone using xda app-developers app
Click to expand...
Click to collapse
I see an exclamation mark only when you press power + x (bootloader 90.78).
I tried ADB steps..not working.
Have you verified OpenRecovery folder and its update.zip on sdcard? Try to re-download and unpack it fresh new.
What rom you said you currently have?
Have you installed vulnerable recovery?
Have you verified OpenRecovery folder and its update.zip on sdcard? Try to re-download and unpack it fresh new.
I tried, does not work ...
What rom you said you currently have?
Stock rom 2.2.x.
Have you installed vulnerable recovery?
Of course, just as there's no difference ... the menu does not show.
The menu should show. Any menu. Either from stock or OpenRecovery. I would try with a different sdcard because the older kernel (2.6.29) in recovery does not support some cards well. If the buttons are working and you have installed everything correctly then it should work. I'd try with different sdcard.
Alternatively, you can try to tell recovery to apply update.zip from sdcard automatically
Code:
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
but note that I am not sure if you need to be rooted for that. I assume not. You can either install Terminal emulator from PlayStore or enable usb debbuging in settings and try to connect through adb if you choose to try.
To see if adb detects your device
Code:
adb devices
if all is OK you should get some output (aphanumeric) and after that 16 characters, it should display in what mode is your device (device for a normally booted system, recovery for device in recovery...)
And then
Code:
adb shell
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
reboot
I'm no expert but it might be an unsupported sdcard...
mrvek said:
The menu should show. Any menu. Either from stock or OpenRecovery. I would try with a different sdcard because the older kernel (2.6.29) in recovery does not support some cards well. If the buttons are working and you have installed everything correctly then it should work. I'd try with different sdcard.
Alternatively, you can try to tell recovery to apply update.zip from sdcard automatically
Code:
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
but note that I am not sure if you need to be rooted for that. I assume not. You can either install Terminal emulator from PlayStore or enable usb debbuging in settings and try to connect through adb if you choose to try.
To see if adb detects your device
Code:
adb devices
if all is OK you should get some output (aphanumeric) and after that 16 characters, it should display in what mode is your device (device for a normally booted system, recovery for device in recovery...)
And then
Code:
adb shell
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
reboot
I'm no expert but it might be an unsupported sdcard...
Click to expand...
Click to collapse
Here's what I get from cmd:
C:\android-sdk\platform-tools>adb devices
List of devices attached
04037B7518003010 device
C:\android-sdk\platform-tools>adb shell
# echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
cannot create /cache/recovery/command: directory nonexistent
#
My device is rooted wth "superoneclick" method.
es7ar said:
cannot create /cache/recovery/command: directory nonexistent
Click to expand...
Click to collapse
Create it.
Code:
adb shell
mkdir -p /cache/recovery
mrvek said:
Create it.
Code:
adb shell
mkdir -p /cache/recovery
Click to expand...
Click to collapse
C:\android-sdk\platform-tools>adb shell
$ mkdir -p /cache/recovery
mkdir -p /cache/recovery
mkdir failed for -p, Read-only file system
$
Try without -p
Code:
mkdir /cache/recovery
mrvek said:
Try without -p
Code:
mkdir /cache/recovery
Click to expand...
Click to collapse
I created the folder "recovery" inside "cache" with root explorer.
Now cmd shows me: ( check attachments )
are you missing "echo"?
Code:
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
it simply writes what is in the first argument (in quotes) to file named "command" located in /cache/recovery
Edit: you can ommit adb devices. You just test the first time when you connect to be sure if adb detects your device. After that it should generally give "device not found" or something like that if connection to device is lost.
I do not understand ...
The command "echo" - update_package = sdcard: update.zip "> / cache / recovery / command" should create a file called "command" in the folder "recovery" from the "cache"?
If so, there is no file called "command"
Sorry, I'm newbie ... I do not want to stress you out.
Edit : Hmm ...
Instead of reboot, like you said, I typed "reboot recovery" then restated the phone ... and the loading bar appears. The phone has rebooted when it came to approx. 30% ..
es7ar said:
I do not understand ...
The command "echo" - update_package = sdcard: update.zip "> / cache / recovery / command" should create a file called "command" in the folder "recovery" from the "cache"?
If so, there is no file called "command"
Sorry, I'm newbie ... I do not want to stress you out.
Click to expand...
Click to collapse
Yes, it should create that file with that content, to instruct recovery to automatically apply update.zip.
You can try to create that file manually with the
Code:
--update_package=SDCARD:update.zip
content in it.
Could you post the content of
Code:
mount
executed in adb? i was sure you can write to cache, it should be mounted read-write.
---------- Post added at 03:32 PM ---------- Previous post was at 03:30 PM ----------
es7ar said:
Edit : Hmm ...
Instead of reboot, like you said, I typed "reboot recovery" then restated the phone ... and the loading bar appears. The phone has rebooted when it came to approx. 30% ..
Click to expand...
Click to collapse
hm...
could you please execute in adb:
Code:
ls -laR /sdcard/OpenRecovery /sdcard/*.zip
post output.
Okay, it looks like it was done!
You've explained it very well ... but I did not openrecovery and update.zip in sdcard.
I thank you so much for helping me! Thanks a lot!!
es7ar said:
but I did not openrecovery and update.zip in sdcard
Click to expand...
Click to collapse
That leads us back to the very begining of the process...
Hi,
I have a S5830 which was running CWM - not sure exactly what version but worked perfectly, and had CFW CyanogenMod (I think 7.2.0 if I remember correctly)
I did something stupid, I had a few bugs which were annoying me so thought I'd go back to OFW, I downloaded a couple from Tsar3000 which I tried flashing through Odin but It would just go for ages and not seem to progress. I can get in download mode but I dont know toe process to take to now get me back on official fw with original recovery. I have downloaded the stock recovery image zip file from this website but when ever I try and flash anything Odin just seems to not progress. I can no longer boot into recovery mode.
What shall I do from here please?
Thanks
Seems weird, are you sure you did flash it correctly?
How to flash with odin.
Flashing the newest firmware:
1) Turn off your phone
2) Remove your SIM Card and SD Card
3) Extract previously downloaded firmware
4) Open ODIN 4.38 on your PC
5) Select from extracted archive: OPS-OPS, Boot-APBOOT, Phone-MODEM, PDA-CODE, CSC-CSC (leave EFS and One Package empty)
6) Connect your phone via USB into PC
7) When the screen is turned on hold POWER+VOLUME DOWN+HOME and wait until the phone enters the Download Mode
8) If ODIN detected and recognised your phone should light up the first square to the left side
9) Press "Start" button and wait, the process should take ~5 minutes
10) If all goes well your phone should reboot automatically
11) Square should change the color to blue and display "PASS" it means that flashing process was successful and we have the newest firmware
12) Disconnect your phone
13) Turn off your phone
14) Insert your SIM Card and SD Card again
15) Turn on your phone
16) Now you have the newest firmware!
If you did try, pushing CWM with Odin.
Flash Custom Recovery:
1) Push recovery-clockwork-5.0.2.6-galaxyace.img to your device using Android Debugging Brige push recovery-clockwork-5.0.2.3-galaxyace.img /tmp/" command
2) Turn off your phone
3) Press POWER+HOME BUTTON
4) Login to your device over "adb shell"
5) Mount /system using "mount /dev/block/stl12 /system" command
6) Flash CWM recovery using "flash_image recoveryonly /tmp/recovery-clockwork-5.0.2.3-galaxyace.img" command
7) Umount /system using "umount /system" command
8) Reboot your device using "reboot recovery" command to test your new CWM recovery
9) Reboot your device[/QUOTE]
Then flash Stock Recovery, from CWM. - Download it Here. Use the version appropriate to your Android version.
reply
Hi,
Thanks for the reply. I tried everything you said except flashing the custom recovery with the method you said. The download link you provided for the recovery unfortunatly doesn't work So I downloaded from another link on the forum, but when I try and push the file ADB just doesnt find the device. Note: I can only get in download mode.
Do you know another way I can do this?
Thanks for your help
reply
Hi,
I tried what I did th efirst time, Odin + Ops + Custom Recovery - One package etc and its worked this time, only difference is did it on another PC, Still 7 x64. Dont kno whats different but phone now boots again so i can start from the beginning.
Thanks