[Q] Remove the write protection - Huawei Ideos X5 U8800

I want to write recovery, but it says remove the write protection, and erased, and the standard recovery. now is 2.2, 2.3.5 is safe to flash (512) via the menu? And how to remove this protection?

I really can't understand what ur trying to ask. Please be more detailed.

If you phone is rooted then try to follow below steps :
1) Install ES File Explorer or File Expert.
2) Install Remount.
3) Using Remount mount the .cust_backup folder as RW.
and now try to write your Recovery.img
http://forum.xda-developers.com/showthread.php?t=1377390

Related

[recovery hack] How to get back recovery 2e

Helo
I found a way to return to the recovery 2e
recovery 2e
Copying a file using the Root Explorer
# unzip and put archive contents in a folder called recovery2e on /sdcard/
# first mount -o remount,rw /system (important options in Root Explorer for do this)
# file recovery copy to /system/bin (and replace)
# xbi folder contents copy to /system/xbin/ (and replace)
Click to expand...
Click to collapse
Method by captive thanks buddy
# put archive contents in a folder called recovery2e on /sdcard/
# open a shell and get root (ADB or Terminal on Phone, type su and pres enter / accept )
# remount /system rw (busybox mount -o remount,rw /system)
# rename recovery in /system/bin to recovery3e (for backup purposes)
# copy "recovery" from /sdcard/recovery2e/ to /system/bin/ (cp /sdcard/recovery2e/recovery /system/bin/)
# copy the folder /sdcard/recovery2e/xbin/recovery to /system/xbin/ (cp -rr /sdcard/recovery2e/xbin/recovery /system/xbin/)
# enjoy!
Click to expand...
Click to collapse
Restart your phone
Isn't anyone going to comment on this?
Gurus: does it really work? That simple?
Thanks
Didn't work for me - used root explorer method. Now just hangs when I try to get recovery mode. Can get download mode ok still, and phone boots ok of course. Running JPM with root and voodoo5 3. Anything else to try?
Does not work on JPM....
it no works.
Phone: Doc's JP6 + voodoo pre3 + rooted
Method: Root explorer.
1, during copy the xbin folder to system, it shows "replace files" but after i check inside the system/xbin, the files are disappared??!! I did manually copy everything one after one from xbin to system/xbin, but i can't see where they are after copy.
2, anyway, i reboot the phone with 3b combo, the recovery mode still showing 3e.
so i say it no works. anyone tried the cable methed?
this thing work but it needs a little workaround as discussed by danzel. follow here: http://forum.xda-developers.com/showthread.php?t=774500&page=188
Could you please update the instruction for jp6 + voodoo pre4?
abd remount (don't know why) isn't working and /system is always ro so adb push and shell (adb shell works) cmd aren't working.
It is correct to remove su and busybox int the extracted folder since i have both already installed?
I was on JPM, followed the instructions.
Phone couldn't boot, lost ability to enter recovery. Luckily I could still enter Download mode, flashed to JPM, but being on voodoo kernel before that, didn't managed to disable lagfix before getting into this trouble - Couldn't revert back to RFS, and without ability to enter recovery to format.
Finally reverted back to Eclair firmware, could see my beloved recovery again. No way I'm going through the above again.
The above is just my own experience, for reference just in case someone is as unlucky as me.
This is the clear step on recovering the recovery2e
Recover recovery2 e
1. uncompress the downloaded file recovery 2e and copy the direcotry to sdcard and rename it to recovery2e
2. Using root explorer copy File recovery from recovery2e on sdcard to /system/bin
3. Using root explorer copy Folder recovery in xbin to /system/xbin
4. If did not work try copy xbin folder over /system/xbin folder
Ok, confirmed working for me on JPM+Voodoo.
I installed Rom Manager too, and CWM Recovery is fully working too!! TNX
xtrememorph said:
This is the clear step on recovering the recovery2e
Recover recovery2 e
1. uncompress the downloaded file recovery 2e and copy the direcotry to sdcard and rename it to recovery2e
2. Using root explorer copy File recovery from recovery2e on sdcard to /system/bin
3. Using root explorer Folder recovery in xbin to /system/xbin
Click to expand...
Click to collapse
Your method DO NOT work at all. I cannot enter recovery mode.
Fortunately download mode is still available.
JPM+Voodoo5 pre6
lagigia, what didn't work for you?
Here's what I did:
put archive contents in a folder called recovery2e on /sdcard/
open a shell and get root
remount /system rw (busybox mount -o remount,rw /system)
rename recovery in /system/bin to recovery3e (for backup purposes)
copy "recovery" from /sdcard/recovery2e/ to /system/bin/ (cp /sdcard/recovery2e/recovery /system/bin/)
copy the folder /sdcard/recovery2e/xbin/recovery to /system/xbin/ (cp -rr /sdcard/recovery2e/xbin/recovery /system/xbin/)
enjoy!
if using the root explorer method, copy xbin folder content, do not try to overwrite the entire dir on top.
mike.sw said:
if using the root explorer method, copy xbin folder content, do not try to overwrite the entire dir on top.
Click to expand...
Click to collapse
too late is there a way to solve it or get a step back?
thx!
i think u can just flash only the old kernel back and it will be fixed (only zimage).
captive said:
lagigia, what didn't work for you?
Here's what I did:
put archive contents in a folder called recovery2e on /sdcard/
open a shell and get root
remount /system rw (busybox mount -o remount,rw /system)
rename recovery in /system/bin to recovery3e (for backup purposes)
copy "recovery" from /sdcard/recovery2e/ to /system/bin/ (cp /sdcard/recovery2e/recovery /system/bin/)
copy the folder /sdcard/recovery2e/xbin/recovery to /system/xbin/ (cp -rr /sdcard/recovery2e/xbin/recovery /system/xbin/)
enjoy!
Click to expand...
Click to collapse
Thanks, works fine on JPM/JP6
Could we get a newbie friendly guide please. Get root. What does that mean and should i just type what you quoted. Thanks
Sent from my GT-I9000 using XDA App
Edited the first post and put the new, easy tutorial
Could i get some background on this, please?
Is it correct that:
1) recovery2e is the default samsung recovery?
2) new versions of recovery2e can't apply all the update.zip we were able to apply with the older versions? (unsigned, signed??)
3) This is why we need the old recovery2e to replace the new one?
4) Where did the issue started? Since Froyo releases?
5) Is this why we can't root Froyo FWs with an update.zip anymore like it was the case with Eclair?
I'm really sorry if this is kinda obvious but i never really saw any clear explanation about this. Hope someone could clear it up for me
1) Yes
2) Correct on recovery 2e you can't apply all the update.zip
4) Yes, New tutorial on fist post
4) The JPM ROM brings new recovery 3e
5) You can root phone by flash kernel with root by odni

Re-write damaged build.prop?

I've managed to make a typo somewhere when updating the build.prop and it hasn't written it, now my tab has a /System/build.prop.old file, but no /System/build.prop file. I've got a backup of the file, has anyone either got a valid UPDATE.ZIP file for a JK5 EU firmware version of the build.prop that I can write (will it work from the "external" SD card?) - or some other way of gaining root access via the recovery ADB shell so that i can rewrite this file, or am I going to need to reflash via Odin? I've tried creating my own update.zip file but it tells me that it can't find it, so I'm guessing it has to be on the internal SD card, which is not a lot of use as I can't mount it.
Not a big deal if I have to, I'd just rather know an alternative in case I stuff it up again
EDIT: Nevermind, I worked out how to gain root access whilst in recovery, pretty simple really - the same as the regular manual-root process but just using a different work folder. The /tmp folder is writeable in recovery mode so I just copied the rageagainstthecage binary into there via "adb push", set it to executable, ran it, killed the adb server and restarted it, reconnected and I had root access, moved the build.prop back and all is well again.
Based on this, it'd be a piece of cake to write an UPDATE.ZIP that did a full permanent shell-root and also installed busybox and superuser.apk. Any point or are people happy enough with the existing methods?

[Q] Busybox

Does anyone know where to get the busybox binary that will work on the nexus 10? Also, how do you manually copy it to the system folder? I'm rooted and on the stock ROM. File explorer used to have an option to remount a partition in read write mode but am not seeing this option now. Anyone know the syntax to remount the system partition with write? I have root and can get shell on the file system.
TIA
cowabunga said:
Does anyone know where to get the busybox binary that will work on the nexus 10? Also, how do you manually copy it to the system folder? I'm rooted and on the stock ROM. File explorer used to have an option to remount a partition in read write mode but am not seeing this option now. Anyone know the syntax to remount the system partition with write? I have root and can get shell on the file system.
TIA
Click to expand...
Click to collapse
You can grab busybox off the market, things like esFile explorer , root explorer, has options to remount RW , or you could just install a custom manta kernel ..

UNBRICK ASUS MemoPad 7 ME176C/CX

Enter recovery and sideload CN ROM
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-CN-3_2_23_182.zip
To return to WW rom its a litle complicated becouse when you try to sideloade ww version it gives error for not having inough space. So you need to give command to recovery to instal zip from location you want.
1. root with rootzenfone.apk
http://23pin.logdown.com/posts/230216-root-rootzenfone-14r
2. turn on usb debuging
3. download ww rom and rename it update.zip
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-WW-3_2_23_182.zip
4. download es or some other file menager that has root access.
5. go to / (root) and manualy copy update.zip to /data folder
6. Download https://drive.google.com/file/d/0B6...drivesdk&resourcekey=0-W0btfSuQS9kq5iNNsCuWgQ and copy command file to cache/recovery folder
6. open ADB and type line by line:
adb remount
adb shell
su
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/data/update.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
after this reboot to recovery and automaticly instal ww rom
This is fantastic, and smart move making a new thread...
Thanks,
sutekh137
And if you're not bricked, but can't update from the old software version. Copy and paste the commands in terminal emulator to force the update. Worked out great. Thanks for the tip.
slayeralive said:
Enter recovery and sideload CN ROM
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-CN-3_2_23_182.zip
To return to WW rom its a litle complicated becouse when you try to sideloade ww version it gives error for not having inough space. So you need to give command to recovery to instal zip from location you want.
1. root with rootzenfone.apk
http://23pin.logdown.com/posts/230216-root-rootzenfone-14r
2. turn on usb debuging
3. download ww rom and rename it update.zip
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-WW-3_2_23_182.zip
4. download es or some other file menager that has root access.
5. go to / (root) and manualy copy update.zip to /data folder
6. open ADB and type line by line:
adb remount
adb shell
su
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/data/update.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
after this your device will reboot to recovery and automaticly instal ww rom
Click to expand...
Click to collapse
I'm having a lil problem here. Could you elaborate a little more, like in /root. <-- What does this mean? Do i write root or am I to go to root of the tablet's memory? And should I use adb on my PC connecting by usb cable to the tablet? I'm having a little problem understanding some of the steps.
(Remember, it's my sex life that it's in danger here)!
bravesoul said:
I'm having a lil problem here. Could you elaborate a little more, like in /root. <-- What does this mean? Do i write root or am I to go to root of the tablet's memory? And should I use adb on my PC connecting by usb cable to the tablet? I'm having a little problem understanding some of the steps.
(Remember, it's my sex life that it's in danger here)!
Click to expand...
Click to collapse
I would assume root of the device itself as the next step is to put update.zip in /data
(Get me in on the fun. I helped. )
I tried terminal emulator to write adb remount, but just after I wrote it, it gives me an error.
I've put the the update.zip in data folder. but there's like two data folders in my tablet's memory root. Do I put it after mnt or before (I,m using root browser v2.3)? Like in the real root of everything? Another question. Must I use the zip inside another zip of the asus ww rom, or just the unzipped zip file. (LOL, confusing, i know).
(I dunno JerBear, they're very peculiar about what/who they blow)!!
bravesoul said:
I tried terminal emulator to write adb remount, but just after I wrote it, it gives me an error.
I've put the the update.zip in data folder. but there's like two data folders in my tab memory's root. Do I put it after mnt or before?
Click to expand...
Click to collapse
They should be symlinked to the same thing. Let me check...
Well. I only have the data folder that's in the root. Peculiar.
As for the zip file question, go for trial and error. Worst case scenario recovery rejects it.
(We'll work around it )
This is what I get in terminal emulator:
Me176c
bravesoul said:
This is what I get in terminal emulator:
Click to expand...
Click to collapse
You need that command only when you are using ADB over PC
Thanks, but I have other issues.
What zip file should I use? The original we download from ASUS or the zip file inside the original.
JerBear told me to try one or another, but he doesn't know I'm in a place where Internet speed is like 50 Kbps... Which means it takes about two hours to download the original file.
However,(and this will sound strange), if anyone can give me the original names of both the original .182 zip file and the one inside the original, I think I can use a previously (and renamed) downloaded .182 ROM.
Me176c
bravesoul said:
Thanks, but I have other issues.
What zip file should I use? The original we download from ASUS or the zip file inside the original.
JerBear told me to try one or another, but he doesn't know I'm in a place where Internet speed is like 50 Kbps... Which means it takes about two hours to download the original file.
However,(and this will sound strange), if anyone can give me the original names of both the original .182 zip file and the one inside the original, I think I can use a previously (and renamed) downloaded .182 ROM.
Click to expand...
Click to collapse
Use zip inside original.
slayeralive said:
Use zip inside original.
Click to expand...
Click to collapse
So to be clear. I'll use ES File Manager to rename the file (update.zip) and copyit into Root->Data->Turn off the tablet and on again->enter into recovery->in PC I'll use adb->type adb remount and other commands->The tablet will reboot and update into the WW.182 ROM.
Right?
Me176c
bravesoul said:
So to be clear. I'll use ES File Manager to rename the file (update.zip) and copyit into Root->Data->Turn off the tablet and on again->enter into recovery->in PC I'll use adb->type adb remount and other commands->The tablet will reboot and update into the WW.182 ROM.
Right?
Click to expand...
Click to collapse
No man can you read? Do not turn of. Connect to pc and use adb or use terminal. If you are using terminal skip adb commands and start at "su" command. After typing last command it will automaticly reboot to recovery and start instalation than just wait...
slayeralive said:
No man can you read? Do not turn of. Connect to pc and use adb or use terminal. If you are using terminal skip adb commands and start at "su" command. After typing last command it will automaticly reboot to recovery and start instalation than just wait...
Click to expand...
Click to collapse
Ok, ok. Don't get your intelligence in a twist.
Thanks for helping me with my absurd noobiness. :good:
bravesoul said:
Ok, ok. Don't get your intelligence in a twist.
Thanks for helping me with my absurd noobiness. :good:
Click to expand...
Click to collapse
Have fun with your "reward"
Not yet I'm afraid. I've tried via terminal emulator and indeed it goes to recovery, but afterwards, it just reboots into the CN version untouched.
(And JerBear, i'm kidding about the chicks...They aren't 3. It's only one).
Try again you did somethin wrong
Folow the steps download->extract->rename to update.zip->copy to /data folder->type in terminal
bravesoul said:
Not yet I'm afraid. I've tried via terminal emulator and indeed it goes to recovery, but afterwards, it just reboots into the CN version untouched.
(And JerBear, i'm kidding about the chicks...They aren't 3. It's only one).
Click to expand...
Click to collapse
If you missd or typed wrong one character in terminal it wont work. Try again.
bravesoul said:
Not yet I'm afraid. I've tried via terminal emulator and indeed it goes to recovery, but afterwards, it just reboots into the CN version untouched.
(And JerBear, i'm kidding about the chicks...They aren't 3. It's only one).
Click to expand...
Click to collapse
From the top, you must be rooted and you must know what that is.
I used the file from inside the download. I believe it has user in the name.
Rename this file to be update.zip.
Place update.zip into the data folder in the root directory, ie. root/data/update.zip.
Back out of that when it's finished and find the original post with the instructions, touch it and touch the message symbol like you are going to reply.
Copy all of the commands from after su, to the end.
Open terminal emulator, Type su and give root permission at the prompt, touch and paste, you should see what you copied, if you don't, do it again. If you do, touch enter and the process will begin.
Do not do anything until the device reboots COMPLETELY. It will go through several reboots, just wait.
Viola, you will be updated.

Unable to replace system files

I am trying to flash a touchwiz launcher and it succeeds in flashing in recovery but the files are not getting put into priv-app folder.
also, trying a copy paste using root explorer but it fails.
some files get copied but for some reason touchwiz launcher does not, any idea why?
Does Root Explorer have any option to remount /system with write permission? Nearly all File Managers with root access do it that way.
It looks like your /system is still mounted read-only. What exactly is being copied over?
Also, you can "adb shell" to the phone while on recovery, that way you have full access on the phone.

Resources