yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] Menelkir:
You need to test some compatible script or application, AFAIK, s2e is the simpliest method using cm7, dont know if works with stock ones. To be honest, I dunno if the stock kernel comes with ext4 support, you'll need to test (try installing instersectraven kernel and s2e, if doesnt work, use Darktremor).

Btw, try open a thread in Q&A, since isn't related to this thread and there more people can help you with that. :)
[Nexus One Android Development] maglovato:
Cannot remove install-recovery.sh

Hi. I read a lot about how to solve it, and seems very simple.

The point is that I am doing this for the first time, so I still dont have root, this way, cannot mount /system and remove the .sh file.

What am I missing?

I am trying to install AmonRA to then patch the stockrom to get Root access with this: http://xdaforums.com/showthread.php?t=613812

Any idea?

Best

Marco
[Nexus One Android Development] efrant:
Looks like you are missing a lot. Is your bootloader locked or unlocked?

If it is unlocked, just boot into fastboot, and use fastboot to flash the recovery. Then, flash ChainsDD's superuser zip (it is in a thread in this forum, i.e., development), which will give you root. Then just delete the file.

If your bootloader is locked, then you need to be running (or flash) an older version of Android (i.e., pre-2.3.4) in order to root as 2.3.4 onwards are not rootable with a locked bootloader.

P.S. The file you are linking to is almost 2 years old. I would certainly not use that on a current Android build.
[Nexus One Android Development] maglovato:
Shame on me. I have CM running on a Magic and Brazilian SGS... (and already did it for a N1).

Well, my bootloader is unlocked as it should be. I flashed the recovery with "fastboot flash recovery recovery-RA-passion-v2.2.1-CM.img".

The point is that now I want to get into recovery, and Im only doing this thru "adb reboot recovery", i.e., I let android boot. At this time, before reaching recovery, install-recovery.sh runs.

As you said, "...lash the recovery. Then, flash ChainsDD's...". After the period, and before the "Then", I am missing something. I understand that I am supposed to install it from Recovery, not? Can I do this with "fastboot update" instead?

Best (and many thanks for your answer so far).

Marco
[Nexus One Android Development] efrant:
After you have flashed the superuser zip, you need to boot into the device normally, not in recovery (as your custom recovery will be deleted once you reboot and replaced with the stock recovery). Once you are booted normally, go in and delete the file, and then RE-FLASH your custom recovery.
[Nexus One Android Development] frozst:
Thank you very much for this recovery. The last CWM recovery corrupted my ext partition so I couldn't restore from that recovery:(. I tried to restore the ext partition manually and then data, cache, system, boot... with CWM but it didn't work.

Do you know how could I restore the backup made with CWMr 5.0.2.0 through this recovery?
[Nexus One Android Development] :
I am not sure you can

I did read a long time about moving the bu out of the CWM bu folder and into the Amon_Ra Nandroid folder on your sd card--not sure if it works

Make sure you have some kinda of bu, preferably on pc

It is a good idea to bu rom and sdcard on a regular basis to your pc

bu sdcard before you do this if haven't already
[Nexus One Android Development] frozst:
I tried but this is what LOG says. Maybe CWMr made a wrong backup and it's impossible to restore.

Restore path: /sdcard/nandroid/HT066P800269/BCDEARS-20111018-0100

Verifying backup images...
.....................................boot.img: OK
cache.yaffs2.img: OK
data.yaffs2.img: OK
recovery.img: OK
sd-ext.ext4.tar: OK
system.yaffs2.img: OK
.android_secure.vfat.tar: OK
Flashing boot...
mtd: MEMGETBADBLOCK returned 1 at 0x00000000 (errno=0)

Not flashing recovery image!

Erasing /data...
.Unpacking data image...
[B]open image file failed[/B]
Erasing /system...
....Unpacking system image...
[B]open image file failed[/B]
Restore done
[Nexus One Android Development] :
If that didn't work, I don't think you'll restore it

Just start over with Amon, sorry--:(
[Nexus One Android Development] frozst:
Thank you anyway :(. I have also tried copying the files manually to the partitions but (obviously) it didn't work.
[Nexus One Android Development] Naes10:
Just wanted to say thanks for the recovery. I was using CW recovery but then had to flash a radio and learned this could not be done on current versions of clockwork. Now I am happily running this recovery and new radio. Thanks!
[Nexus One Android Development] maglovato:
Perfectly understood. My unique question is how to flash superuser.

I found this: http://xdaforums.com/showthread.php?t=682828

It have versions for 1.5/1.6 and 2.1/2.2. I am running 2.3, since Google automatically updated mine weeks ago.

So, the missing link is how should I get root on this device. I was told to flash something thru Recovery to do so, but I cannot get to recovery since I cant remove that .sh because I cant go root.

Am I being too n00b on this? If so, sorry. SGS i9000B was a real pain, and I did it. I am somehow stuck on this tricky point.
[Nexus One Android Development] crachel:
can you flash the img files made with clockwork with fastboot?

fastboot flash userdata data.img

fastboot flash system system.img

etc...?
[Nexus One Android Development] frozst:
Hey! That's a good idea! Is that possible?
[Nexus One Android Development] crachel:
This CM wiki entry seems to indicate so

http://wiki.cyanogenmod.com/wiki/Fastboot
[Nexus One Android Development] frozst:
Thanks! I'll try and I'll post results.
[Nexus One Android Development] efrant:
How to flash a custom recovery and get root with an unlocked bootloader.

Ok, let me try and make this clear, as you are obviously not understanding something, depite all the information/guides available:

Step-by-step:

1) Download the Eclair/Froyo version of Superuser from here: http://xdaforums.com/showthread.php?t=682828 and place it on the root directory of your sdcard.

2) Ensure the Android SDK and USB drivers are properly installed on your computer.

3) Reboot your device into fastboot mode and plug into your computer.

4) Open a terminal window on your computer and navigate to the directory that has the fastboot executable.

5) Type fastboot devices. You should see your device. If not, redo step 2.

6) Place the custom recovery you want into the same directory as the fastboot executable.

7) Rename the recovery to recovery.img (to keep things simple).

8) Type fastboot flash recovery recovery.img

9) Reboot your device into recovery DIRECTLY. DO NOT reboot into the main ROM.

10) Reread step 9. Now you should be in Amon_RA's recovery.

11) Go to "flash zip from sdcard" or whatever the menu is called.

12) Turn OFF signature verification.

13) Find the Superuser zip file that you downloaded, and flash it.

14) Reboot. Now you have root.

15) Now, you can remove the install-recovery.sh either via your device or through ADB if you want. I will tell you how to do it via ADB.

16) Open a terminal window on your computer and navigate to the directory that has the adb executable.

17) Type adb devices. You should see your device. If not, redo step 2.

18) Type adb shell. You should now see the $ prompt.

19) Type su, and then look at your device: You should see the Superuser prompt. Give it permission.

20) Type mount -o remount,rw /dev/block/mtdblock3 /system to mount the /system partion as r/w.

21) Type rm /system/etc/install-recovery.sh to remove the file.

22) Type mount -o remount,ro /dev/block/mtdblock3 /system to mount the /system partion as ro.

23) Type exit.

24) Type exit again.

25) Type adb reboot-bootloader

26) Do step 4, 5, and 8 AGAIN.

27) Finished.
[Nexus One Android Development] maglovato:
efrant, thanks man. A lot. I know I was missing something stupid. Now I am at the Recovery. I tought that rebooting directly into Recovery will produce the same behavior, and of course I was completelly wrong. I admit that. Thank you for your time and attention.
[Nexus One Android Development] frozst:
Well, I tried to restore via fastboot but I got an error message saying the the size of file is too big. Apparently fastboot images are limited to 128MB.

Maybe I could try with a update.zip script...
[Nexus One Android Development] zc2:
efrant, thank you very much for the detailed guide, but could you please explain, what's the purpose of the step 26 ?
[Nexus One Android Development] efrant:
If you are using a stock ROM, there is a file (/system/etc/install-recovery.sh) included in the stock ROM that re-flashes the stock recovery on every boot.

So, if you flash a custom recovery, it will disappear the first time you boot into your stock ROM.

In order to have a custom recovery to stick on your device, you need to delete that script. However, if you booted into your ROM to delete that file, your custom recovery is gone, so you have to re-flash it. But now, since the file is gone, your custom recovery will still be there.
[Nexus One Android Development] zc2:
Thank you, that makes much sense
[Nexus One Android Development] yumcax:
Fastboot flash

I have used this recovery in the past by installing it through ROM Manager. Now that that seems to not be working, I decided to use the fastboot method. I got fastboot installed and working, fastboot devices finds the phone. But when I try to flash the recovery, I get this message:

So, it was recommended that I install from the SD card.

This does not work either. How can I correctly install? Where must the file be placed so that fastboot can access it and it works correctly?
[Nexus One Android Development] meric04:
It's fastboot

flash

recovery <filename>

[Edit: Nevermind - just re-read the post, you've presumably tried the correct syntax. Have you confirmed that the image file is correct - i.e. check the md5 signature?]
[Nexus One Android Development] efrant:
If your bootloader is locked, you cannot use fastboot commands. Either use the flash_image utility or install Blackrose. A quick search on both will show you how to proceed.
[Nexus One Android Development] gregferns:
Hi efrant,

My Bootloader is locked, but i flashed the Hboot with fastboot commands.

Also fastboot devices does show me my phone.

So i dont know if SOME fastboot commands work and some don't.

regards

greg
[Nexus One Android Development] efrant:
Let me rephrase my post: you cannot use "fastboot flash" to flash unsigned images (and this recovery is unsigned) if your bootloader is locked.
[Nexus One Android Development] gregferns:
Thanks man....
[Nexus One Android Development] Bi0haZarD:
Man, hit his THANKS button instead...
[Nexus One Android Development] Androidity3000:
Best recovery by far. Never any issues. Been using this version for months and months. Perfect with flashing, backing up, restoring, and partitioning.
[Nexus One Android Development] mikshepard:
Ditto!
[Nexus One Android Development] yumcax:
Thanks for the help- I had checked MD5 sums, they were correct. It turns out the problem was that I did not realize I needed an unlocked bootloader; I had used one-click root in the past.

fastboot oem unlock solved my problem.
[Nexus One Android Development] SiNJiN76:
Just wondering...has clockwork taken over the recovery on all phones now? Still use RA personally...and would love to continue on which ever phone I move on to.
[Nexus One Android Development] makelegs:
Team Win Recovery Project (TWRP) is pretty awesome and is available on multiple devices. I use it on crespo, but still use Ra on passion
[Nexus One Android Development] el_Salmon:
I have flashed this recovery from the Google Stock ROM (Android 2.3.4) and I haven't needed to make root. Just to unlock OEM bootloader, flash recovery and inmediately flash Cyanogenmod 7.
[Nexus One Android Development] yumcax:
You have to root if you don't want to unlock your bootloader.
[Nexus One Android Development] gcbxda:
secure

How secure is your phone after you install that?

i mean, with my stock one if i loose it, the lucky bastard that finds it can't access my data without a `oem unlock` which will wipe out the data.

is there a way to "lock"* it again after i did all the reimage i need to get cyanogen up?

* I read that `oem lock` will screw things up unless you have signed everything in your phone. So i'm thinking more about a amon_ra-backup feature instead of fastboot itself
[Nexus One Android Development] sert00:
any planning love for galaxy nexus users...?hope to use it one day on this phone..always loved amon_ra cwm..:victory:

sorry for necroing this 3ad..
[Nexus One Android Development] milli.kovach:
nice!
[Nexus One Android Development] loof13:
The site is down! Can someone upload the file again??
[Nexus One Android Development] crachel:
See attachment
[Nexus One Android Development] bankanidhi:
i tried to flash a ics rom, http://xdaforums.com/showthread.php?t=1995549 but it failed saying the rom is not sighned properly. Any help?

I do not know if it a problem with the ROM or the recovery. Thought since this recovery is really old, may be the problem is in the recovery. please help/
[MDA II, XDA II, 2060 ROM Development] saaqi:
HI M8S

I HAVE A PROBLEM WITH MY QTEK 2020 (XDA II) O2 FROM GERMONY.

IT HAS GERMAN LANGUAGE INSIDE AND I TRY TO MAKE IT ENGLISH AND GET ERROR AND NOW EVERYTIME WHEN I TRY TO UPGRADE IT GIVES ERROR 201.

NOT CONNECTING TO ACTIVE SYNC ..... BUT WHEN I CONNECT IT SHOWS ON THE SECREEN SERIAL TO USB .

IT IS WRITTEN ON IT (ACTUL STATUS OF THE PHONE IS ...)

SERIAL

V 1.01

ANY LUCK HOW TO FIX MY QTEK ?

I HAVE THESE FILES .....

1:- AL_DT_WWE_11100_112_10200_Ship.exe

2:- HIMA_DT_WWE_17500_103_11800_Ship.exe

PLZ CHECK MAY B MY FILES R NOT FOR THIS MODLE.....

WAITING FOR THE REPLY .

THANKS AND REGARDS

SAQIB.
[G1 Q&A, Help & Troubleshooting] adrake400:
Im getting a Nexus One and I need to know the most stable rom for my G1 because Im giving my G1 to my wife. Any suggestions?

Thanks!
[G1 Q&A, Help & Troubleshooting] JAguirre1231:
Do we have to Cyanogen
[G1 Q&A, Help & Troubleshooting] buggy1024:
Cyanogen has been pretty stable for me, using WG now through bcs. of speed.

I think you may consider unrooting it and flash the original T-Mobile/HTC firmware...?
[Windows Mobile Development and Hacking General] diomondus:
I couldn't find any answer to my problem so I'm starting a new thread.

When I travel outside the country my phone uses roaming networks. (Of course this is expected and normal.)

The problem is that the phone wakes up very often (every 5-10 minutes) trying to reconnect to the network or to search for a better signal.

The effect of this strange behavior is that my battery drains in less than 20 hours.

I mention that ActiveSync is closed and push internet is disabled.

How can I prevent this?

Thank you in advance!
[Windows Mobile Development and Hacking General] Bulldog:
FIRST: I think to open thread in this section for your inquire is not correct as here it is for development

however:

Roaming Network is big buck for the service provider. therefore many phone companies are interested to keep the roaming device on their network which makes the device keep changing the network and consumes high battery power .

1) check with your home service provider the partner companies in each country you are traveling or search in web the most cost effective comapany in that country. (different companies may charge different pricing for same country)

2) Ones you find out the suggested comapany set your device to manual networks sellection under SETTINGS---> PHONE--->NETWORK SETTINGS---> "network selection"..... and set manualy the name of the company that is right for you.
[Windows Mobile Development and Hacking General] diomondus:
Thank you for your answer.

I opened the thread here because this section is "Development and Hacking" and I was expecting to receive a solution related to tweaking registry.

I know the path for setting the network to manual but I don't want that.

When I travel abroad by car, I cross several countries and I don't have time to manually switch to another network.

All I wanted was to set the phone to keep the same network more than 5 minutes.

As I've already said before my phone tries to find the best network at every 5-10 minutes.

Or at least I would like to know how to set the phone to not turn on the display every time when it tries to find a network.

My wife has a Nokia phone (a cheap one) and doesn't face this kind of problems.
[HD2 Windows Mobile 6.5 ROM Development] jonboyuk:
Which is the best way to flash the Leo now?

Some chefs recommend flashing back to an original rom then to a custom.

Now we have a working HSPL, until now Bepe's custom RUU was used for flashing just the OS part (and this util is still part of the Rom's on here). Do we now no longer use this and use UDK's customRUU instead?

It just seems that when I flash one custom rom over another and one over that one etc etc, I always end up with strange rom results :-/
[HD2 Windows Mobile 6.5 ROM Development] crazyman1:
I would of thought that problems with ROMS are due more to them all being new and the chefs trying to iron out the bugs....I ended up going through most of the roms available on the site until I found one that worked for me.

The only time I install an official rom is if I have problems booting and am not able to get activesync working otherwise I just go straight over the top of whatever rom is on my device and then hard reset before booting up for the first time.
[HD2 Windows Mobile 6.5 ROM Development] jonboyuk:
Awesome! Good advice, thank you!
[HD2 Windows Mobile 6.5 ROM Development] chris_ah1:
Ok, just to piggyback on this. As a first time flasher (without the HD2 as yet), have i got this correct:

a) Install HSPL so I can install 1.48 or 1.61 onto my 1.43 device without goldcard by placing the HTC Rom on a FAT16 microsd card as leoimg.nbh? Then should i want to do that again I will have to re-install hspl?

b) For cooked roms, install HSPL, then use SSPL to install cooked rom. Should it all go wrong I can then put back my stock 1.61 ROM onto a sd card and voila back to work without goldcard?
[HD2 Windows Mobile 6.5 ROM Development] crazyman1:
I believe that the micro sd card should be formated FAT32. Just remember that when you flash an offical ROM, it will also remove the HSPL so you will need to reinstall it.

I only use SSPL, but I've got a Goldcard in case of problems.....just follow the guides and without the goldcard, it's a good idea to make sure that HSPL is installed so you've got a way to revert back if you have any problems. Hope that explains it a bit better
[HD2 Windows Mobile 6.5 ROM Development] chris_ah1:
Yep, that's precisely what I thought. thanks for confirming it.

I understand that some regulars are getting irritated by general newbie questions but sometimes it is good just to confirm and understanding of how it all works before hosing a device and then asking stupid qs on how to fix rather than posting how great a new ROM is :)

sadly I'm a bit too lazy to do the goldcard thing. But I might get one done for safety.
[HD2 Windows Mobile 6.5 ROM Development] frko:
You do not need any sspl to install a cooked rom when you've hspl'ed your leo.

You can revert back to the original spl by using the sd card method with a stock rom.
[HD2 Windows Mobile 6.5 ROM Development] Svenvdmeer:
too bad you got the wrong answer. there is no need for sspl or goldcard after you use HSPL. with that you can install official and custom roms. you don't have to install hspl again. just the once. UNLESS you install a official ROM with the SD card method. that will overwrite HSPL with the original (locked) SPL. you can flash a original ROM over usb. this will leave the hspl intact.
[HD2 Windows Mobile 6.5 ROM Development] crazyman1:
Am i bad, just trying to help. Still all they were after was some reassurence they wouldn't brick there device and what i said was at worst long winded.

Didn't see anyone else rushing to help.
[HD2 Windows Mobile 6.5 ROM Development] jonboyuk:
So are we supposed to use UDK's RUU utility to flash now?
[HD2 Windows Mobile 6.5 ROM Development] chris_ah1:
So no cooked ROM will over-write HSPL?

ah, good. I just saw some ROm page (i think Xannytech) which said use only SSPL.

I dunno - it's all a bit technical for a first timer. perhaps i should stick to official updates and CABs for now.
[HD2 Windows Mobile 6.5 ROM Development] HSKalay:
Hopefully someone can put down some clear methods/ways for the new people, as there seems to be a lot of conflicting ideas (or maybe i'm imagining it).

I just tried flashing stock 1.61 to my 1.48 Leo, (after installing HSPL, which seemed to install fine).

I done a bad flash though (for whatever reason) as the phone just went in to perpetual rebooting after the update utility completed. Just managed to get it started by reflashing 1.48 back on to it.
[HD2 Windows Mobile 6.5 ROM Development] chris_ah1:
Well here is the issue Hskalay:

You are meant to be able to uninstall HSPL...but some say that flashing a stock rom does not uninstall it.

Some say that cooked roms include SPL.nbh and that it will overwrite HSPL. In fact some rom cookers have said in their posts to only use SSPL and not sd flashing via leoimg.nbh and HSPL. However others say that cooked ROMS do not (and should not) overwrite the HSPL.

From what I have gathered without clear consensus is that as long as HSPL is on the device, ANY rom can be installed from the sd card - cooked or official. Without HSPL you NEEDED goldcard. With HSPL you can still use goldcard but it isnt essential, as long as HSPL works and boots.

From what I have read, it appears that HSPL is a bootloader like GRUB or windows boot loader or LILO. The difference from SSPL is that HSPL gets written to the boot sector, and SSPL is a temporary fix as if you installed GRUB/LILO to your linux system partition and had the stock bootloader in the boot sector point to it to boot.

Goldcard: you dont need a working bootloader (Bepe's HSPL or stock), you dont need a working ROM.

HSPL: you need a working bootloader (i.e HSPL of course), you dont need a working ROM.

SSPL: you need working rom, and working bootloader.

If you ever over-write your Bepe HSPL you will need to put it back on. hence it is not a once only deal. However, it appears as said that it is not over-written.
[HD2 Windows Mobile 6.5 ROM Development] HSKalay:
Thanks for your reply Chris.

With HSPL - Do the rom HAVE to be installed via the SD card? Or can they be launch and installed from the PC (via USB). ie install HSPL to the phone, and then running the standard update program for say, 1.48 to 1.61 (which needed goldcard previously if I am correct).
[HD2 Windows Mobile 6.5 ROM Development] crazyman1:
Right just tested everything out this morning. Installed HSPL.

Can run installs either using CustomRUU or SSPLRUU tools either leaving the phone in active sync or in the boot loader menu by holding down Vol Down key.

To install new Radio ROM just use CustomRUU as this won't wipe your device

and just install the radio. There is a tread with all the Radio only roms here http://xdaforums.com/showthread.php?t=611787

Also wiped HSPL by installing original O2 ROM and this did clear the HSPL. To install original ROM, just copy the nbh to the device, rename it to LEOIMG.nbh and then reboot into the Bootloader and it will then reinstall the rom. Just to let you know I got some wiered error when doing this and it restarted the update and then completed. Hope this helps

It's been said that at the moment you shouldn't install custom ROMs by copying the nbh files to your memory card.

Update:

To reinstall HSPL again after flashing original ROM, I had to remove my memory card or it would not work.