yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] jukyO:
When I try to do it like this, it says "Done", but recovery is still AmonRa 2.0.1.

By "stock tool" I am referring to a stock "System Update" apk in MIUI Rom, with an option "Boot to recovery".

If I power on with power key and vol-, and set "Recovery", it goes into AmonRa 2.0.1 recovery.

Should I start unRevoked from Recovery Menu maybe or?
[Desire Android Development] Rastaman-FB:
thats fine, its not flashing it :/

if you did it the manual way i mentioned and it still shows amonRA then im certain youve done it the right way and this hasnt flashed. its a shame

the only way is s-off it seems unless the dev finds a way to get this working with unrevoked (it should bloody work)

unrevoked might not be compatible with custom roms tho
[Desire Android Development] jukyO:
So S-OFF then.....
[Desire Android Development] Rastaman-FB:
Just noticed you added a feature that is quite important especially for users with track ball problems

yes people you can now use the volume rocker and power as well as the trackball/trackpad to select menus
[Desire Android Development] rmg2:
Just curious about two things:

1. Can i restore my nandroid backups made with amonRA 2.0.0 if i use this recovery?

2. It is possible to directy root my device with Unrevoked method and with this recovery?
[Desire Android Development] nickk67:
Hi guys,

I am currently on amonra 2.0.1..I'm having issues with restoring my nandroid (I have 4 partitions data2ext running on miui rom). To my understanding, this is caused by amonra 2.0.1 which does not backup the 3rd and 4th partition.

So I would just like to ask if this recovery will solve my issue (by backing up the 3rd partition as well. 4th is just swap so it's not needed to be backed up, right?).

Please correct me if I am wrong. Thank you!
[Desire Android Development] Alex-V:
yes, this solves your problem :)

with kind regards..Alex
[Desire Android Development] Rastaman-FB:
1. yes you can

2. someone else tried this and while 3.21 said successful iit didnt flash the recovery. it could be that hes using a custom aosp rom rather than a 2.2 sense rom so you could try it.

other alternative is going s-off
[Desire Android Development] jukyO:
Reverted back to stock rooted ROM. S-OFFed my device and loaded this recovery with Fastboot Commander. Worked like a charm.

Flashed MIUI XJ ROM, all good, only at the end it says "unknown ROM". Rebooted, MIUI loads up fine!

Thanks all for your support!
[Desire Android Development] nickk67:
I tried installing this recovery v1.0.2 rc4 using a terminal app but it keeps saying flash_image not found.

I double checked and it is there.

I used the following commands:

su

flash_image recovery /sdcard/recovery.img

Anyone who can point out to me what had gone wrong?

edit: now trying rom manager by cwm as suggested by some sites

edit2: I followed amonra's steps to use rom manager..

via Rom Manager

Download "Rom Manager" from the Android market

Start "Rom Manager"

Select "Flash ClockworkMod Recovery" and wait for it to finish

Select "Flash Alternate Recovery" and wait for it to finish -> this will install the latest version of RA recovery.

But after flashing cwm recovery the alternate recovery option is still greyed out! Now I'm stuck with cwm! :(

Edit 3 : managed to flash it with android flasher 1.8. Although it says failed, when I boot into recovery RMD 1.0.2 came up! :)
[Desire Android Development] nickk67:
One problem, after doing a nandroid backup, it changed both my ext4 into ext2 resulting in all my apps missing..now I'm not sure about the integrity of said nandroid..im converting back to ext4 but not sure if its a good idea to use the nandroid I did..
[Desire Android Development] Rastaman-FB:
you cannot flash this using those methods and rom manager is a fake flash

android flasher works if you are S-OFF as it just automates a fastboot command
[Desire Android Development] m0narx:
nickk67

Strange, nandroid don't change filesystem, it only read or write files on current filesystem.... Can you post recovery log and i'll try to solve problem.

jukyO, can you post build.prop file from your ROM?
[Desire Android Development] nickk67:
Thanks for reply.

Ok will post log asap.
[Desire Android Development] Rastaman-FB:
i dont know, answer the ops question but also are you s-off? what are the steps you are doing to boot to recovery?
[Desire Android Development] nickk67:
Yea, s-off. Booted into recovery using power+vol down+back.

I'm testing out the backup again and see if it changes my ext4 to ext2 again.

To op, it is working fine now.

I have made the log but it was after I upgraded it to ext4 again, so I think I pretty much ruined it for you. I'm sorry I didn't know that I'm suppose to make the log before fixing the issue. Anyway I tested it and my ext didn't change to ext2 this time so all is working fine now.
[Desire Android Development] Rastaman-FB:
odd, ahh well its working now
[Desire Android Development] Schrumpel:
After installing Reflex 2.17 the recovery freezed.

The Image was installed but i have to pull out the battery to go on.

I tried it 3 times with RUU and Unrevoked 3.22 with RMD Recovery 1.0 and 1.02 but after installing the recovery freezes.

Edit: I tried AmonRa 2.01 and it works and doesn't freeze after flashing Reflex 2.17.
[Desire Android Development] m0narx:
Schrumpel

1. Can you check that device in avaliable in adb mode?

2. If it's avaliable can you copy file /tmp/recovery.log and post it

For examle you can do it with QtADB
[Desire Android Development] Rastaman-FB:
ive mentioned this 3 or 4 times and hoped the dev had seen it, unfortunately i fixed it so the log doesnt show it

to fix boot to fastboot

fastboot erase system

fastboot erase cache

fastboot reboot-bootloader

it will then boot to recovery and you can restore the backup you made in amonRA or a previous RMD version

i had this with cyanogen 7.0.3 light every time i flashed a new version of this rom

it seems it messes up on detecting the rom 1st time and then hangs
[Desire Android Development] fragargon:
hi rastaman,

this just happened to me.

i m preparing flashing another rom, this one used hboot oxygen (system90 mb)

i flashed cm7 hboot which has partition system of 145 mb and rmd recovery freeze.

I rebooted into bootloader erase system and cache and reboot bootloader and then recovery... it was fixed.

sorry could not extrac logcat since i didn't know issue.

thks i hit the button

edit: seems that happens if rom is unknow by rmd recovery whilst build.prop first line is:

ro.modversion=LeeDrOiD_V3.0.8.2
[Desire Android Development] Rastaman-FB:
indeed, the weird thing is the recovery only knows what the rom is after a flash or a restore.

if you flash a newer version of this recovery again, it will say "unknown" for the rom or hang and say "unknown". if it just says unknown without hanging then you can just restore the nand without doing fasboot erase commands

however its hung on me twice and both times i had no choice but to erase system and cache from fastboot.

it is stable and doesnt encounter any such issue once fixed but still its not a nice one, especially if you are coming from something like CWM where you dont have the liberties of restoring a backup after wiping system
[Desire Android Development] fragargon:
hi,

got a lil issue, should know that i m running hboot-cm7 (5 mb cache)

here is a pic
[Desire Android Development] nicklashidegard:
Seems like you're trying to install a rom with system bigger than your hboot. If its a data plus rom might be worth changing to the cm7r2 hboot.
[Desire Android Development] Rastaman-FB:
nail on head, this rom is not cm7 table compatible
[Desire Android Development] fragargon:
hi, indeed this is Hboot cm7r2,
[Desire Android Development] fragargon:
I m afraid you are wrong, this rom on data++ version is fully compatible

have not issue with the rom, only 5 mb cache and recovery trying write log on it each time it boots to recovery
[Desire Android Development] Rastaman-FB:
clear the cache?

i would have thought if you are using a data++ rom you should used the hboot its designed for.

i dont seem to have issues flashing any roms and im using a 3mb cache on custom mtd :/
[Desire Android Development] jukyO:
Hi m0narx,

attached in the post, sorry for late reply :(

Thanks for developing it!

Cheers,

jukyO
[Desire Android Development] fragargon:
hi, that's what i've done. did the trick.

i wouldn't say issue since recovery was working...

from fresh install, i didn't have had such message, so probably coz a flash hboot whitout wiping anything. I think it could be good advice wipe cache and system at least before flashing new hboot.

if new rom it flash dalvik and cache (updater script flash system)

anyway thanks for your support ;)
[Desire Android Development] m0narx:
New ver

Recovery updated to 1.0.3RC1

All info in the first post

Image in first post re uploaded
[Desire Android Development] fragargon:
hi,

for some weird reason, writing cache error comes up every 3 boot into recovery.

a wipe cache and fix for some boots.

a collected the recovery.log (see attachment)

however i already flash new RMD103rc1 so this could be of dated

edit: thanks so much mornax, like your work.

From my point of view, only RMD recovery trusted ;) (hit the button)
[Desire Android Development] jukyO:
Wow...usb brick fix from recovery....you rule mate!
[Desire Android Development] MatDrOiD:
Newest version of your recovery. Backup worked without any problem, and this very fast!! :) Nice work, dude.
[Desire Android Development] Meaple:
I must admit. This recovery is getting sicker and sicker. Awesome job man.
[Desire Android Development] Rastaman-FB:
Question for OP

flash img's: Can you clarify thats for s-off only? i know only people with s-off seem to be able to use this recovery but just incase can we get clarification

Rom version unknown: im not understanding this, are you saying youve fixed they recovery hang after flash? for me ive had to wipe system every time ive flashed it and each time it has said unknown

EDIT: flashed this version and didnt get the recovery hang

thanks
[Desire Android Development] aorifan:
1.03RC1 looks really cool mate! very useful, nice work:D
[Desire Android Development] scutworker:
Looks good.

Quick question: if I convert my ext2 partition to ext3, then to ext4, does it erase it, or will the data on the partition be preserved?

Cheers.
[Desire Android Development] LiooO:
Im using 1.03RC1 recovery and [ROM] LeeDrOiD HD V3.3.1-Port-R2 Data++.. Today i tried to do nandroid backup twice and i had to pull battery 2 times because backup was going for over an hour?! The dots was filling up all the time as the backup is working normally, but its taking too long (usually its over in couple of minutes..)?! Or i should wait even more than hour? Phone (ROM) is working just fine after reboot..

Any suggestions pls?
[Desire Android Development] AlxMAX:
Is there any chance to have the sources of this recovery?
[Desire Android Development] aorifan:
sounds like a usb brick,try usb brick fix
[Desire Android Development] MatDrOiD:
http://xdaforums.com/showthread.php?t=691639
[Desire Android Development] kl_arnet:
OK guys, I have used USB Brick Fix from this recovery and now can't get my phone back working.

Freezes on bootscreen.

Tried to reflash HBOOT, tried to flash different roms, nothing helps.

Fastboot and Recovery are accessible.

Any idea?

Regards
[Desire Android Development] LiooO:
USB brick? everything is working normal except i cant make nandroid backup?
[Desire Android Development] andreya108:
Just installed 1.03RC1.

For some reason it detects my DATA2SD ext4 partition as ext2.
[Desire Android Development] rmg2:
For me too, i just convert it to ext3 first and then to ext4 and now is just fine.
[Desire Android Development] kl_arnet:
It detects partitions format wrong. It was all the time ext4. It just shows ext2.

Can any one help me with my problem?

I run USB Brick Fix and now can't install any rom. Doesn't go through bootscreen.

I can access recovery, fastboot etc but rom itself isn't working.

Tried to wipe, reflash rom, flash other one etc.

Still nothing.
[Desire Android Development] m0narx:
Hi kl_arnet

1. For correct detection of ext4? convert it in ext4 in recovery.

2. Can you post recovery log, and logcat then the rom freezes on boot?

3. Can you run adb shell in recovery and post tresult of command:

cat /proc/cmdline

Also can you post recovery log?
[Desire Android Development] LiooO:
Also can you post recovery log?

Sorry.. Where is located recovery log?
[Desire Android Development] MatDrOiD:
In recovery is an option to move this log to sd card. Menu point "other". Now you can find this log on the root of your sd card, as far as I can remember.
[Desire Android Development] m0narx:
LiooO, you can find it in /tmp/recovery.log or type adb shell log2sd in console, and log will be on sd-card
[Desire Android Development] LiooO:
Thanks for info.. I deleted nandroid folder on SD Card and started full backup again 2-3 minutes ago.. i guess its stuck again?! How long to wait before i pull out battery?

If i pull off battery because its stuck at: "performing backup..." there will be recovery log at all?

Edit..

After 10 minutes i still see only "Performing backup. ", "Performing backup.. ", "Performing backup... "
[Desire Android Development] m0narx:
Just do that than backup is in progress with adb shell log2sd or with adb pull /tmp/recovery.log
[Desire Android Development] LiooO:
Attached recovery.log
[Desire Android Development] m0narx:
It's only startup log... no backup progress
[Desire Android Development] LiooO:
I tried again and got the same file?! I use command from other menu to move log to SD.. i don't know how to start shell..

I tried again with selected for backup boot, system, data and cache.. Finished backup successfully.. .android_secure and SD-ext was disabled!

Edit 1:

Now i will try only .android_secure..

Edit 2:

only .android secure backed up correctly! .. now i will try only sd-ext

Edit 3:

Now i'm confused!? sd-ext backup finished successfully in couple of minutes?!

I did selected 4 top options and backup was successful.. then only 5 option and again successful.. then only 6 option and success again? but if i select them all its going long.. maybe i just need to wait because i installed like 20 games and it takes longer? When i was doing selective backups none was lasting more than couple of minutes...
[Desire Android Development] LiooO:
bump!!!!!!!!!

Edit:

Now i selected all, and after few minutes backup done!?
[Desire Android Development] m0narx:
Fix boot

Please save dump to me

1. boot in recovery and run cmd

2. type adb shell

3. type dump_image misc /tmp/mtd_error.img

4. type exit

5. type adb pull /tmp/mtd_error.img

To fix

1. load phone in fastboot

2. Unzip image in attahment

3. Run fastboot flash misc mtd0.img

4. Boot rom

OR

1. Load in recovery

2. copy unzipped image on sdcard

3. type adb shell flash_image misc /tmp/mtd0.img

If with image 1 it fails try img2
[Desire Android Development] Rastaman-FB:
its not remotely showing characteristics of a usb brick!!!!!
[Desire Android Development] hawkeyexp:
Hi,

yesterday i tried out flashing slpash1 and it doesn't work. log says it can't find the splash1 partition :-(
[Desire Android Development] kl_arnet:
m0narx,

As I'm familiar with USB Brick, I've tried it before but it didn't work with my mtd0.img

Worked like a charm with your mtd0.img

спасибо!

P.S.

Do you still want logcat.txt and mtd_error.img?
[Desire Android Development] m0narx:
hawkeyexp - you are right will be fixed in rc2

kl_arnet - no, thanks, i found an error and makr it in first post(this bug is actual only for operator's phones)

new version will be done tomorrow
[Desire Android Development] Jagdish84:
Really love your recovery Mon, nice job indeed!!! Although the ext issue still puzzles me...

After flashing the 103 version recovery showed my ext as ext2 again, same as when I upgraded to 102, is it just me? Is it just a bug regarding the display of the current ext? Would sure appreciate an answer on this one as providing you with every bit of information you need.

Cheers.
[Desire Android Development] kl_arnet:
Just reformat your partition with RMD 1.0.3 and issue will be solved. My Ext partition is now shown as ext4 at it should be.
[Desire Android Development] Rastaman-FB:
indeed but shouldnt have too
[Desire Android Development] rmg2:
For THIS rom is not showing the name only: 2.36.405.8, maybe you can fix it.
[Desire Android Development] pecha2k:
Coolest recovery for our desire. Thx

Enviado desde mi HTC Desire usando Tapatalk
[Desire Android Development] kl_arnet:
He can't.

It's rom side issue.

If you look closely when you are flashing rom, rom's name is 2.36.405.8, not RCMix 2.

I'm also using this rom and spotted this. Wanted to blame recovery but when I flashed with Ra Desire was the same. Robocik screwed rom name. Period.
[Desire Android Development] shoey-n:
Occasionally you have to click the trackpad twice to select something

Also can you change the location of the theme because everytime I update a ROM or flash a new one, the theme gets deleted, perhaps putting it on /sdcard/
[Desire Android Development] Jagdish84:
Well, im flashing cyanogen nightlies every day(almost), i dont wanna have to upgrade it each n every day. needless to say its not a normal behaviour hence i reported it, as i said before im willing to assist in every way i possibly can...
[Desire Android Development] Rastaman-FB:
why would you have to do it everyday?

it is a bug that needs fixing but that error occurs when the recovery is flashed after the partitions are made. if you make the partitions using the latest recovery then they are read correctly and should continue to be read correctly

i could be wrong but thats how i see it
[Desire Android Development] Jagdish84:
Well, ya but that's what I want to avoid doing every time...

I think it's just a bug with the way the recovery displays the ext status...I tried using 4ext recovery and it shows my ext partition as ext4...
[Desire Android Development] Rastaman-FB:
i think its just how it reads it if the recovery hasnt created it itself. hopefully he fixes it but imo it should only happen again when you upgrade the recovery to another version
[Desire Android Development] fragargon:
hi,

I just come back from few days holydays, read thread.

I flashed RMD103rc2 and performed a backup. all went well (nice background)

Atm no more cache error writing in my case.

nice work and thanks to share it
[Desire Android Development] laowaizi:
really useful recovery

I used it to convert ext3 to ext4. All went well

thanks for sharing it
[Desire Android Development] MatDrOiD:
Flashed newest version, made backup, everything is working fine. :) Never had problems restoring backups, btw. ;)
[Desire Android Development] hawkeyexp:
tried 1.0.2 rc2 and seems to work well - also flash recovery from recovery works fine....
[Desire Android Development] m0narx:
Try to place image in folder that not contains spaces in path
[Desire Android Development] rmg2:
Got it. Done. Thanks!
[Desire Android Development] Meaple:
Using themes is a lot easier now due to it being on SD card.
[Desire Android Development] kodein:
m0narx can you change the add themes like in version 1.0.3 RC2? (with files.zip)

i can't build own theme.
[Desire Android Development] kakarot_22:
+1

the support of old and new scripts is very useful

i will give it a try but i think it is a very good recovery...

at the first start (or in the system info , u can maybe add the free space of the partitions in MB
[Desire Android Development] Rastaman-FB:
made a backup of my rom using rc1 then flashed to rc3

it said unknown rom so i restored backup and now it bootloops then autoboots to recovery :/

dont know whats happened but my rom is dead and forces a boot to recovery
[Desire Android Development] Rastaman-FB:
EDIT:

fixed, i forgot to patch the recovery with custom mtd patch

thanks
[Desire Android Development] Meaple:
Go look at the bottom of the first post.
[Desire Android Development] ghalalb:
Brilliant

cheers m0narx, this is a brilliant recovery
[Desire Android Development] kodein:
manual doesn't work or I did not understand

Edit: sorry, everythings all right, it was my fault...
[Desire Android Development] Bananebieger:
Just installed the recovery successfully. Doin my first nandroid Backup with this rom. I am missing the status what the recovery is backing up like CWM does it.

Now testing to fix apk uid mismatches, thats why I installed RMD.

Nice work though!
[Desire Android Development] ghalalb:
Backup

hhhmmm problem, attempted first backup, didn't work, just said Performing backup for 20 minutes?????
[Desire Android Development] kakarot_22:
Can i convert my ext3 fs to ext4 without data lose? I am scared ^^

I have the latest version with 1gb ext3 size rom is leedroid 2.5 a2sd

Btw. Best recovery anyway :-)
[Desire Android Development] kl_arnet:
You can't. Conversion means reformat.

Backup everything with titanium (I'm not sure with nandroid if it reverts also positions)

Convert and do the wipe.

Install rom and restore apps.

Swyped from Desire.
[Desire Android Development] Bananebieger:
Houston, I still have a problem :(

I flashed RMD Recovery to fix apk uid mismatches(what you can do with this recovery) but I am still getting the error "System UIDs inconsistent" when I boot my MIUI XJ xpart Desire...

That should be gone right now... my phone works fine and I am not experiencing any problems with apps/laggs/bugs or something...

So, why do I still get this warning?

I changed my recovery to fix this after all...
[Desire Android Development] Rastaman-FB:
you could have bigger problems?

personally ive never seen this issue in a rom but to make sure its not the recovery ignoring the mismatch request try flashing amonRA 2.0.1 and using that to fix the uid mismatches. if you still get the same error then i wouldnt imagine its repairable via recovery

have you tried wiping dalvic after using this tool?
[Desire Android Development] m0narx:
About UID Mismatches:

Did you use data2sd rom?

About convertings FS between fs:

If you do only converting(between any filesystems), you don't need backup, any convertions in dataloss less), but you must have free space on sdcard

About backup problem:

Can you post recovery log?

And about themes:

I upload two themes samles in first post.
[Desire Android Development] Bananebieger:
m0narx, I am using the x-part version of MIUI XJ Rom. 1.7.21

Rastaman-FB, whats the difference between this release and AmonRa 2.0.1? Both should be able to fix uid mismatches.

I'll try that this evening. I am at work right now.

Thanks folks.
[Desire Android Development] 123xdagsm:
Hi

I using in RMD Recovery 1.0.3Rc3.

It's wonderful .
[Desire Android Development] m0narx:
Hm... i used the original script for fix uid's mismathes... and it not support data2sd roms.

I modifyed it, and now it support any modifications of data partition)), will be released soon
[Desire Android Development] casacristo:
Awesome recovery, and I also installed it in order to fix the recent MIUI UIDs inconsistency and also it didn´t help (had to wipe data, restore apps and desktop layout and reconfigure the rest of the settings from scratch, argg)

I use MIUI 1.7.22 X-PART version
[Desire Android Development] m0narx:
New version uploaded, Please try it
[Desire Android Development] Rastaman-FB:
will try in the morning
[Desire Android Development] Marchief:
Updated to v1.0.34 from 1.02 via Andorid Flasher, all fine.

Will see if this fixes the issue with it locking up after flashing full rom zip in recovery completes.

Great work, keep it up.
[Desire Android Development] jukyO:
Zdravo,

latest version recognizes MIUI ROM, thats great.

Thanks Monarx!
[Desire Android Development] fragargon:
Hi, installed and testing... Seems working fine atm.

Thks

keep it up good work
[Desire Android Development] Bananebieger:
Is the fix apk uid mismatch Stuff useable with xpart roms like MIUI XJ ver 1.7.26?

Didn't fix my error message at booting.