ok so i still cant get the payload to push i have tried every method. I have no problem getting adb into recovery that is easy but when i go to push the payload update i get signature verification failed, installation aborted and i have done the 1.bat command and still nothing here are my steps.
1.After i get the error message no such directory i stop the loop command, then i hit the apply sd card update and it fails of course then i enter in these commands.
adb push busybox /sdcard/busybox
adb push ota.zip /sdcard/update.zip
adb push su /sdcard/su
adb push Superuser.apk /sdcard/Superuser.apk
Then i volume down to the apply sd card update.zip hit power and then about a half second later i enter in this command.
\/
adb push payload-update.zip /sdcard/update.zip
and then i get this
--install from sdcard--
finding update package
opening update pacakge
verifying update package
E:signature verifacation failed
installation aborted
If anyone could give me some advice i would greatly appreciate it.
Are you sure you copied the correct files (ie. busybox,su, superuser,update) to sdk/tools/ ? And assuming you did, you really do not have to wait and count to press enter after pressing "apply update" on the phone. Just press enter on that command right when you see the green status bar on the phone.
Good luck!
Thank you i stopped trying to time the command and the hitting power worked first time getting ready to flash a rom now.
My original problem is that I ran the OTA upgrade of Froyo like an idiot the day I bought my Desire here in India. Now, I am trying to downgrade the HBOOT so that I can root my device.
Now the issue is that I am not able to follow the procedure to downgrade the HBOOT as I am unable to push the flash_image and the mtd0.img into the data folder as I get an error "remount failed: Operation not permitted" when I try to remount.
I have tried to access shell and do a 'su' which again comes up with the 'access denied' message.
Can anyone help me get rid of the access issue so that I can downgrade the HBOOT and root my device?
I permrooted pre-OTA, and received the OTA shortly after rebooting, which broke my permroot. I wiped, downgraded, installed OTA and tried permrooting again but now when I type su, term returns 'su: unknown user root' rage works to drop me in a root term, but following the process does not succeed in giving me permroot.
When trying to find any more information about the error I've been getting, I've tried 'whoami' and 'passwd' and they both return 'uknown uid 0'
Any thoughts?
Sent from my T-Mobile G2 using XDA App
the initial root was done with visionary, but i have tried rage in addition.
bump..any ideas?
do i need to play with any permissions when i get temproot via rage??
bump......
bump msglength
jakobdroid said:
When trying to find any more information about the error I've been getting, I've tried 'whoami' and 'passwd' and they both return 'uknown uid 0'
Click to expand...
Click to collapse
whoami and passwd are failing because there is no passwd file. But it's saying you are uid 0, so you are the root user.
What happens when you try the rage method, do you get error messages ? Which bit isn't working exactly ?
If you got temp root then try the gfree method for perm root.
Sent from my HTC Vision using XDA App
following the steps everything goes well until
# /data/local/tmp/root
i get:
mkdir failed for /system/xbin, File exists
cp: can't stat '/system/bin/su/su' : Not a Directory
jakobdroid said:
following the steps everything goes well until
# /data/local/tmp/root
i get:
mkdir failed for /system/xbin, File exists
cp: can't stat '/system/bin/su/su' : Not a Directory
Click to expand...
Click to collapse
The "mkdir failed" message is normal, just ignore that.
But the "cp" message indicats a problem. Check the files on your sd card, have you already got a folder called "su" on it before you started this procedure ? Because that will make things go wrong, there needs to be a *file* su on your SD card, after you have copied it across from your PC using "adb push". If you already have an "su" directory, rename it as something else, then start again with the procedure.
Hi guys,
here's the thing.
I'm rooted with stock rom and want to have lollipop by OTA.
steps I've been doing until now:
1. full unroot thru supersu setting
2. flash stock recovery, extracted from OTA
3. Got error /system/bin/debuggerd unexpected blabla.. (status 7)
4. Tried to relock the bootloader
5. same error as point no 3
I think it's because link2sd messing my debuggerd file.
any advise?
where can I find original debuggerd and debuggerd.bin file?
really need those files
edit: try to replace debuggerd with debuggerd.bin, but adb shell give me error "read only"
edit 2: managed to replace debuggerd with /system/bin/debuggerd.bin with adb shell
but when every time it boots, file "link2sd" debuggerd always come back
Guess this is link2sd issue
I have the Xiaomi Mi A2 Lite 1.4.3 drivers installed and keep getting the error when I try to ADB Sideload "adb sideload connection failed: no devices/emulators found" error
Phone Statistics
- Rooted with Magisk
- Boot Loader Unlocked
im trying to install TWRP following this guide the "the custom droid" install-twrp-recovery-root-xiaomi-mi-a2-a2-lite
and I can load the TWRP img via "fastboot boot" command but once I do the ADB Sideload I get the above error ive never had this issue before years ago with Samsung phones but with the Xiaomi im at a loss
is there a way to flash the kernal with TWRP while in the ROM
Did you enable ADB sideload from "Advanced" tab in TWRP?
yes I clicked advanced then adb sideload and it does its thing but when i do the command on pc in cmd prompt adb sideload xxx.zip i get the error as stated above