Database Info

[Q] installing 4ext touch recovery without root

My question is simple: how can I flash 4ext recovery touch before I have root?
I have s-off but still on the stock ROM. I know I can just follow the s-off guide and in step 2 install CWM recovery, but I need 4ext touch instead.
How can I do this?
Thanks

Yes is should be fine!

GhostXSeries said:
Yes is should be fine!
Click to expand...
Click to collapse
Sorry.. not sure u answered my question there? lol

anyone who can help?

fredcorp6 said:
My question is simple: how can I flash 4ext recovery touch before I have root?
I have s-off but still on the stock ROM. I know I can just follow the s-off guide and in step 2 install CWM recovery, but I need 4ext touch instead.
How can I do this?
Thanks
Click to expand...
Click to collapse
Just interested why do you "need" 4EXT ?
Anyway, as you're still on the stock ROM and I assume the Stock HBOOT, you have two options:
i) Use Fastboot flash to flash the recovery img to the phone. You'll need to install adb etc. onto your PC/Linux system.
ii) Load the appropriate PG58IMG.zip file onto the root of your SD-card, complete power off (pull battery) reboot (Power & Vol -)
As I don't use 4EXT I'm not certain what downloads exist for it.
The bottom line is that it's the same process for either CWM or 4EXT.

gol_n_dal said:
Just interested why do you "need" 4EXT ?
Anyway, as you're still on the stock ROM and I assume the Stock HBOOT, you have two options:
i) Use Fastboot flash to flash the recovery img to the phone. You'll need to install adb etc. onto your PC/Linux system.
ii) Load the appropriate PG58IMG.zip file onto the root of your SD-card, complete power off (pull battery) reboot (Power & Vol -)
As I don't use 4EXT I'm not certain what downloads exist for it.
The bottom line is that it's the same process for either CWM or 4EXT.
Click to expand...
Click to collapse
The reason I need it is because I want to install ARHD, and with 4EXT you are able to pick what kernel, addons etc you install with the ROM. As far as I know CWM does not let you do this?
I think option 1 is my best bet... do you mind giving me a few more details on how to do this?
I have adb set up and I am capable of using it. I also have the 4ext recovery zip file - it contains an image file called "recovery" and a text document containing an md5 sum.
Thanks a lot for your help so far

fredcorp6 said:
The reason I need it is because I want to install ARHD, and with 4EXT you are able to pick what kernel, addons etc you install with the ROM. As far as I know CWM does not let you do this?
I think option 1 is my best bet... do you mind giving me a few more details on how to do this?
I have adb set up and I am capable of using it. I also have the 4ext recovery zip file - it contains an image file called "recovery" and a text document containing an md5 sum.
Thanks a lot for your help so far
Click to expand...
Click to collapse
CHECK AND RECHECK the MD5 for the IMG file..
The ADB and FASTBOOT commands might or might not be in the same folder, depends where you got it and what version.
Connect the phone via USB and debugging enabled.
i) make sure "adb devices" can see your phone.
ii) Get the phone into Fastboot (usual Bootloader then Fastboot, it should say "Fastboot USB")
iii) fastboot flash recovery "recovery.img"
where "recovery.img" is the name of the 4EXT.img file
iv) fastboot reboot-bootloader
v) Go into Recovery and osh bosh done.

fredcorp6 said:
The reason I need it is because I want to install ARHD, and with 4EXT you are able to pick what kernel, addons etc you install with the ROM. As far as I know CWM does not let you do this?
I think option 1 is my best bet... do you mind giving me a few more details on how to do this?
I have adb set up and I am capable of using it. I also have the 4ext recovery zip file - it contains an image file called "recovery" and a text document containing an md5 sum.
Thanks a lot for your help so far
Click to expand...
Click to collapse
It is very much possible to install 4ext recovery without root. But your phone must be S-OFF. To install 4ext touch do the following.
1. Download an appropriate PG58IMG.zip file from this thread. By the word appropriate I mean that the PG58IMG.zip is having your CID and MID. Hope you know your CID and MID. The PG58IMG.zip can be of any version. I would suggest V1.17 as it has less files.
2. Download latest 4EXT recovery touch from the development forum. It will be in img format. Rename it to "recovery.img"
3. Open the PG58IMG.zip by winrar on your pc.
4. Delete all the files except the android-info.txt.
5. Add "recovery.img" into the PG58IMG.zip .
6. Now your PG58IMG.zip contains only two files i.e "recovery.img" and "android-info.txt"
5. Save the PG58IMG.zip.
6. Copy the PG58IMG.zip on the root of your sdcard.
7. Boot your phone into bootloader.
8.Your phone will prompt for update.
9. Say "yes" by pressing volume up key.
10. Once it is finish your phone will reboot and you will have 4ext touch recovery on your phone.

musarraf172 said:
It is very much possible to install 4ext recovery without root. But your phone must be S-OFF. To install 4ext touch do the following.
1. Download an appropriate PG58IMG.zip file from this thread. By the word appropriate I mean that the PG58IMG.zip is having your CID and MID. Hope you know your CID and MID. The PG58IMG.zip can be of any version. I would suggest V1.17 as it has less files.
2. Download latest 4EXT recovery touch from the development forum. It will be in img format. Rename it to "recovery.img"
3. Open the PG58IMG.zip by winrar on your pc.
4. Delete all the files except the android-info.txt.
5. Add "recovery.img" into the PG58IMG.zip .
6. Now your PG58IMG.zip contains only two files i.e "recovery.img" and "android-info.txt"
5. Save the PG58IMG.zip.
6. Copy the PG58IMG.zip on the root of your sdcard.
7. Boot your phone into bootloader.
8.Your phone will prompt for update.
9. Say "yes" by pressing volume up key.
10. One it is finish your phone will reboot and you will have 4ext touch recovery on your phone.
Click to expand...
Click to collapse
Sounds like the option 2 gon a dal was talking about...
Thanks a lot guys
BTW... I already have the PC58IMG file from downloading CWM - could I just paste the recovery.img into this file? Deleting the CWM one first ofcourse

fredcorp6 said:
Sounds like the option 2 gon a dal was talking about...
Thanks a lot guys
BTW... I already have the PC58IMG file from downloading CWM - could I just paste the recovery.img into this file? Deleting the CWM one first ofcourse
Click to expand...
Click to collapse
Sure, as I said either way works. If you have the IMG and are happy using commands at a prompt, the fastboot is probably faster. If you don't have the ready made PG58IMG.zip file the instructions above also work.
Either way, check and recheck the MD5.................
EDIT: If you flash via the PG58IMG.zip method, pop the SD-card after it's finished for a clean boot. Then remove/rename the PG58IMG.zip file on the card, or remove/rename via a PC before the boot.

gol_n_dal said:
Sure, as I said either way works. If you have the IMG and are happy using commands at a prompt, the fastboot is probably faster. If you don't have the ready made PG58IMG.zip file the instructions above also work.
Either way, check and recheck the MD5.................
EDIT: If you flash via the PG58IMG.zip method, pop the SD-card after it's finished for a clean boot. Then remove/rename the PG58IMG.zip file on the card, or remove/rename via a PC before the boot.
Click to expand...
Click to collapse
Thanks for poiting out. I forgot to mention these.

Can you give me a link to 4ext?
thx

bibihtc said:
Can you give me a link to 4ext?
thx
Click to expand...
Click to collapse
Look herehttp://forum.xda-developers.com/showthread.php?p=20015407
Sent from my HTC Sensation 4G using Tapatalk 2

Clean Cricket Htc One SV Nandroid (2.04.1050.3)

idk if anyone would want this but here is a clean jellybean nandroid backup of a cricket wireless Htc One SV with newest update already applied. http://www.filefactory.com/file/5u395y1qavzr/Clean_JB_Crkt_2.04.1050.3.rar

Ok, i've downloaded this backup and made a zip file for flashing in recovery from it.
Credits:
- ironhide602 for the backup
- dsixda for his kitchen
Download:
JB_Crkt 2.04.1050.3_stock_odexed.zip
Notice:
As i don't have a cricket phone i could not test but one tester reported it's working.
Anyway, flash this on your own risk. Don't do this, if you are not experienced enough!
This files are for flashing in recovery.
I will not work on bugs, if you find some (as i could not test myself)!
Kernel source code can be found at htcdev.com.
How to install:
First of all: make a nand backup in recovery, so you can easily go back if you don't like it!!!
Download the zip file that match to your device and copy to sd card.
Wipe/format data/system/cache/dalvik cache, factory reset.
Flash the zip through recovery.
Htcdev.com unlocked users who are not S-Off have to extract boot.img from the zip file and flash it afterwards over fastboot with the command:
Code:
fastboot flash boot boot.img
Then reboot.
- There is no superuser/su inside, if you wanna root, flash superuser from here.

old.splatterhand said:
Ok, i've downloaded this backup and made a zip file for flashing in recovery from it.
Credits:
- ironhide602 for the backup
- dsixda for his kitchen
Download:
JB_Crkt 2.04.1050.3_stock_odexed.zip
Notice:
As i don't have a cricket phone i could not test but one tester reported it's working.
Anyway, flash this on your own risk. Don't do this, if you are not experienced enough!
This files are for flashing in recovery.
I will not work on bugs, if you find some (as i could not test myself)!
Kernel source code can be found at htcdev.com.
How to install:
First of all: make a nand backup in recovery, so you can easily go back if you don't like it!!!
Download the zip file that match to your device and copy to sd card.
Wipe/format data/system/cache/dalvik cache, factory reset.
Flash the zip through recovery.
Htcdev.com unlocked users who are not S-Off have to extract boot.img from the zip file and flash it afterwards over fastboot with the command:
Code:
fastboot flash boot boot.img
Then reboot.
- There is no superuser/su inside, if you wanna root, flash superuser from here.
Click to expand...
Click to collapse
Hellow , Please can u Upload this file in other server ill try multiple times
& stuck in the final byte .
Regards

I have no fast internet and i'm trying since days to upload a big file, so not before the other one is finished.

old.splatterhand said:
I have no fast internet and i'm trying since days to upload a big file, so not before the other one is finished.
Click to expand...
Click to collapse
sorry sorry ... not server ,,its my own pc,, ill try in other & everythin ok
thanks
Regards

I Need a root package

hey guys... all the root packages I have seen so far have a survey to download ... I cant do surveys because .. well its a long story .
in a short version .. I am looking for a direct root package download without being troubled in doing a survey .
I would be grateful if some one can help me out

Please don't duplicate posts, it's against the rules. I was already helping you in the other thread you posted in but I'll continue here. The root package you were looking at is most likely not compatible with your current firmware version. What are your bootloader details? I need to see the first five lines.
Sent from my Evita

timmaaa said:
Please don't duplicate posts, it's against the rules. I was already helping you in the other thread you posted in but I'll continue here. The root package you were looking at is most likely not compatible with your current firmware version. What are your bootloader details? I need to see the first five lines.
Sent from my Evita
Click to expand...
Click to collapse
*** UNLOCKED ***
evita pvt ship s off RL
CID-HTC__622
hboot-2.15.0000
radio-1.30a.32.45.18
opendsp-v33.1.0.45.1128

What's your ultimate goal? Do you want to root your current stock ROM or install a custom ROM? Either way you need to install TWRP recovery first. I'm assuming you already have adb/fastboot installed on your PC.
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you have TWRP recovery on your phone.
If you want to root your current stock ROM you can just flash SuperSU through the install menu in TWRP recovery. You'll find a download link here:
http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
If you want to install a custom ROM, just find one you like, download it, read the install instructions on the ROM thread, perform a full wipe (cache/dalvik cache/factory reset/system) through the wipe menu in TWRP, then install the ROM through the install menu in TWRP.
Before doing either of these options you should make a backup of your current setup in the backup menu in TWRP. Select system, data, and boot, then swipe to backup.
Sent from my Evita

timmaaa said:
What's your ultimate goal? Do you want to root your current stock ROM or install a custom ROM? Either way you need to install TWRP recovery first. I'm assuming you already have adb/fastboot installed on your PC.
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you have TWRP recovery on your phone.
If you want to root your current stock ROM you can just flash SuperSU through the install menu in TWRP recovery. You'll find a download link here:
http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
If you want to install a custom ROM, just find one you like, download it, read the install instructions on the ROM thread, perform a full wipe (cache/dalvik cache/factory reset/system) through the wipe menu in TWRP, then install the ROM through the install menu in TWRP.
Before doing either of these options you should make a backup of your current setup in the backup menu in TWRP. Select system, data, and boot, then swipe to backup.
Sent from my Evita
Click to expand...
Click to collapse
tried to flash recovery ...
"error : cannot load "recovery file name" (openrecovery-twrp-2.6.0.0-evita)
though it is in the same folder of android where I put fastboot and all that stuff..

The command should be:
Code:
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
Sent from my Evita

timmaaa said:
The command should be:
Code:
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
Sent from my Evita
Click to expand...
Click to collapse
oh I forgot the img thing haha
thanks a lot
though now I wanna flash the venom rom (sense 5 , 4.2) and step 3 says : "Confirm the MD5 on the download page matches the MD5 of the file on your phone (ES File Explorer will show the MD5 of the file)" what does that mean ?

If you're downloading the file directly to your phone, use an app called AFV (Android File Verifier) to check the md5. After you've downloaded the ROM just copy the md5 listed on the download site, open AFV, paste the md5 into the box, click the select file button, navigate to the file then long press it and select calculate md5, hopefully it'll say success. If it says anything other than success the download is corrupt.
Sent from my Evita

timmaaa said:
If you're downloading the file directly to your phone, use an app called AFV (Android File Verifier) to check the md5. After you've downloaded the ROM just copy the md5 listed on the download site, open AFV, paste the md5 into the box, click the select file button, navigate to the file then long press it and select calculate md5, hopefully it'll say success. If it says anything other than success the download is corrupt.
Sent from my Evita
Click to expand...
Click to collapse
oh ok thanks alot you are smart you know ?? extremely helpful and nice to have you around the thread

madshark2009 said:
oh ok thanks alot you are smart you know ?? extremely helpful and nice to have you around the thread
Click to expand...
Click to collapse
Thanks, I've just been doing this for a while. Give yourself some time and try to keep up with things and you'll gain a whole lot of knowledge too.
Sent from my Evita

[Q] Painted myself into a corner...

I made a mistake by trying to get through the rooting/rom-ing process in a hurry. The result is that i'm stuck on cm boot logo.
1. I installed cwm 5.5.0.4 custom recovery through this guide.
2. Made a nandroid and copied it to pc, sd card, external sd card.
3. Flashed cm-10.1-noname>gapps>tablet ui>wipe cache>wipe dalvik>reboot. (source, version:cm-10.1-20130827-UNOFFICIAL-tf101.zip )
4. Stuck on boot screen.
I'm guessing I should have used twrp rather than cwm.
The trouble is that cwm 5.5.0.4 seemingly doesnt have external sd card support, and having tried to flash cm, it means that the stock nandroid i made probably got moved elsewhere as no backups are found when i try to recover.
Is there a way out of this mess?

Ah, you are not totally painted into a corner. Just climb up the wall and across the ceiling!
There are 2 ways out: ADB or APX.
To use ADB, whilst booted to CWM, connect your USB cord to your computer. Update using the Naked Drivers 0.72 for the unknown device, or ADB device. It will probably show an MTP device as well, leave that alone.
Once you think you have the driver working, you will need ADB. I have a copy of the files in my dropbox so you don't need the whole android SDK.
https://dl.dropboxusercontent.com/u/34321735/adb.zip
Unzip them to the c:\adb folder.
Command prompt and run the following:
Code:
c:
cd c:\adb
adb devices
You should see a device followed by RECOVERY.
Once this is working, find the file you want to move to the tablet to flash (I would recommend TWRP 2.6.3.9 unless you plan on flashing Android Revolution HD) and move this file to c:\adb. I will call it flash.zip for the purposes of this.
Next, go back to your command prompt and type the following:
Code:
adb push flash.zip /sdcard/
Once this is completed you should see the flash.zip on the tablet in CWM so you can install it.
If you do install TWRP, be sure to do a NORMAL reboot (even if it is to a bootlooped OS) so the installation completes. Once you get to the ROM boot screen (pas the Eee Pad logo screens) you can boot back to recovery.
Method 2 - APX
I have a guide for using APX and EasyFlasher here: http://www.transformerforums.com/fo...nt/31927-frederucos-guide-root-rom-tf101.html
You can either use one of my repacked versions (linked in that thread) to install TWRP (has not been updated for the latest TWRP yet, but it is only a few versions old). If you want the latest, put it on a microSD and flash it after updating to the Easyflasher version.
Or you can download the stock ROM from the Asus Support site, place the .zip file as is in the asusupdate folder within EasyFlasher folder structure and then click the unbrick option.

Thank you Sir for the lightning quick response
Will try the apx method first and will let you know how it goes.
Just a quick question though if i may:
cwm is just a personal preference for me so is there an updated cwm easyflasher and will it do the cm 10.1 install better than 5.5.0.4?
(the last time i was adventurous with a recovery, philz raped my cat and shaved my mom. i know it was just a senseless crime! something about having to manually backup /preload/ or end up with broken nandroid)

jbonetwo said:
Thank you Sir for the lightning quick response
Will try the apx method first and will let you know how it goes.
Just a quick question though if i may:
cwm is just a personal preference for me so is there an updated cwm easyflasher and will it do the cm 10.1 install better than 5.5.0.4?
(the last time i was adventurous with a recovery, philz raped my cat and shaved my mom. i know it was just a senseless crime! something about having to manually backup /preload/ or end up with broken nandroid)
Click to expand...
Click to collapse
If you are going to venture into the JellyBean 4.2/4.3 ROMs, I would HIGHLY recommend using TWRP. It is by far superior to CWM, and no one is supporting CWM for the TF101 as far as I know. 4.2 introduced a new file structure for multi-users and updates do not flash properly if using an older recovery. You end up with your /sdcard/ folder in the /sdcard/0/ (and an additional 0 for each new ROM update flashed).
TWRP is far more intuitive IMO (all wipes are in one simple menu), and @sidneyk has added (in addition to internal and microSD support) dock USB and SD card support. TWRP has a terminal emulator and lots of other nice features over CWM.

Well thats got me puzzled.
Installed TWRP 2.6.3.0 using APX.method
Reflashed cm-10.1-20130721-UNOFFICIAL-tf101.zip >
gapps_4.2.2_CM10.1_TF101_20130324_stock_camera >
cm-10.1-20130721-UNOFFICIAL-tf101-tabletUIpatch >
wipe cache/dalvik >
reboot
And I'm still stuck on cm loading screen. Unless it takes more than 10 minutes for first boot I'm stumped...
P.S. Any way of reusing the CWM made stock nandroid with TWRP?
P.P.S. You're right TWRP is MUCH better. Gonna convert all of my devices for sure.

solved!
flashed cm then rebooted - worked!
flashed cm and gapps then rebooted - still works!
flashed cm>gapps>tablet ui - still working!
all with wiped cache/dalvik
apparently it doesnt like all of them being flashed at the same time for first installs :S

[p500][CWM Advanced Edition] PhilZ Touch

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
To take a screen shot, just long press outside a menu (2 sec and slightly change pressure after the delay)
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
LG Optimus One P500 (p500)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/p500
Click to expand...
Click to collapse
XDA:DevDB Information
[p500][CWM Advanced Edition] PhilZ Touch, a Tool/Utility for the LG Optimus One P500
Contributors
Phil3759
Version Information
Status: Testing
Created 2014-04-21
Last Updated 2014-04-21

Cool.
Upon which CWM version is this based? Note fundamental differences between newer 6.0.* after June 16 -- can flash new Kitkat ROMs and older 5.* which flash older ROMs.
Because of space limitations -- whole business must fit < 5 meg, functionality such as partitioning SDcard was removed from the 6.0.* versions.
What do we have in this version?

Plz update the post with all the features of this recovery... How can we test, if we don't know what to expect???

ujilraj said:
Plz update the post with all the features of this recovery... How can we test, if we don't know what to expect???
Click to expand...
Click to collapse
If you can't read OP and follow links, just do not test
I am fine with this

Unable to flash!
Can't flash the image file by "CWM 6.0.4.6. 16 Jan" recovery by Mukulsoni.Status 7.Please suggest what wrong i did?
1) After d'loading the .image file, i rename it to "recovery" as it in the zipped folder of Mukulsoni recovery.
2) Then i open the zip of Mukulsoni recovery and drag Phil's image file to replace it.
3) Close the zip, put it in the sd card and flash.
4) Status 7 happened.
What should i do? Please help! :crying:

I suggest that the first link needs to highlighted... My mistake, but honestly i didn't notice a link below the title...

sumansur2008 said:
Can't flash the image file by "CWM 6.0.4.6. 16 Jan" recovery by Mukulsoni.Status 7.Please suggest what wrong i did?
1) After d'loading the .image file, i rename it to "recovery" as it in the zipped folder of Mukulsoni recovery.
2) Then i open the zip of Mukulsoni recovery and drag Phil's image file to replace it.
3) Close the zip, put it in the sd card and flash.
4) Status 7 happened.
What should i do? Please help! :crying:
Click to expand...
Click to collapse
This is NOT a flashable zip file!
1. Download, adb push a 6.0.4.6 image file to sdcard (just in case).
2. adb push the PhilZ file to sdcard.
3. In terminal emulator or adb shell (must be rooted):
4. flash_image recovery path-to-file
If it fits and all goes well, you got it.
In case of error, do same for the 6.0.4.6 image and be back in business.

Dovidhalevi said:
This is NOT a flashable zip file!
1. Download, adb push a 6.0.4.6 image file to sdcard (just in case).
2. adb push the PhilZ file to sdcard.
3. In terminal emulator or adb shell (must be rooted):
4. flash_image recovery path-to-file
If it fits and all goes well, you got it.
In case of error, do same for the 6.0.4.6 image and be back in business.
Click to expand...
Click to collapse
I wouldn't suggest anyone do that, I tried to it and almost bricked my phone (long story). I did it before you mentioned this, so it's not your fault. Apparently there isn't enough space in recovery to flash this. I think our recovery has 5mb and this recovery is almost 6mb. I may be wrong with this, but that was the error that showed up when I tried to flash it with flash_image.
It would be safer to suggest to download the recovery, rename it to recovery.img and place it on the root of another recovery zip, overwriting the old recovery, and then trying to flash it. That way, if something happens you will get an error instead of flashing it wrong. But as I said earlier, even if you try you will most likely get a Status 7 error.

indigobv said:
I wouldn't suggest anyone do that, I tried to it and almost bricked my phone (long story). I did it before you mentioned this, so it's not your fault. Apparently there isn't enough space in recovery to flash this. I think our recovery has 5mb and this recovery is almost 6mb. I may be wrong with this, but that was the error that showed up when I tried to flash it with flash_image
Click to expand...
Click to collapse
This should be the error. Then flash_image the 6.0.4.6 which fits. Do it immediately or else .... I believe I had that happen once. I posted about that 5meg limit above. Did not try this because of the limit.
It would be safer to suggest to download the recovery, rename it to recovery.img and place it on the root of another recovery zip, overwriting the old recovery, and then trying to flash it. That way, if something happens you will get an error instead of flashing it wrong. But as I said earlier, even if you try you will most likely get a Status 7 error.
Click to expand...
Click to collapse
Maybe the op should post a proper flashable zip instead. Problem is that status 7 itself might mean a brick.

Dovidhalevi said:
Problem is that status 7 itself might mean a brick.
Click to expand...
Click to collapse
Thanks for the heads up, I actually didn't try booting in recovery after the status 7 error. Now I can confirm that it tries to flash it even if it shows the error and then forces the phone to go in fastboot mode until the problem is solved.

I built using official p500 armv6 repo
They should fix the device recovery size in that case!!

Hi
Recovery Tools will work on LG p500?
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
I See LG optimus me
Because I Want To Flash The Recovery Without Taking Risk

eran32 said:
Hi
Recovery Tools will work on LG p500?
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
I See LG optimus me
Because I Want To Flash The Recovery Without Taking Risk
Click to expand...
Click to collapse
I believe this is simple a nice GUI for flash_image. Aint no such thing as no risk so beware.
The method I suggested should be safe if one flash_image's a valid recovery immediately after any error (but I make no guarantee!).
I advise against flashing this recovery version at this point because it is clearly too big for our device. We can get along just fine without a touch interface if need be. Never had one.
Changing board partition sizes is not a readily done simple matter by any means.