Hello,
been a while since Iv'e been here.
I flashed the latest full RUU - Sprint_HTC_One_M9_3.41.651.21_RUU, lost root and TWRP recovery. I can get into bootloader, download and stock recovery.
Tried latest twrp image rename 0pjaimg.zip on SD from download (22RU_HEADER_ERROR, FAIL22 RU_HEADER_ERROR) and recovery modes (E:footer is wrong, E:signature verification failed) - no work. Tried within ADB, no work. tried sideload su. APK, no work.
Am I missing something? I must be, any help appreciated.
http://forum.xda-developers.com/showpost.php?p=61777179&postcount=562
this worked for me. it took a few tries on windows with different RUU's. it finally worked when i used my linux machine to compress. placed on sd, renamed 0pjaimg, kick into download mode, flash prompt, up volume>>i now have custom TWRP. everything else was downhill from there!!
Related
Really didn't want to make a new thread about this but honestly people just jumped to conclusions without being helpful in my previous thread.
Long story short I'm trying to manually get 4.4.2: http://forum.xda-developers.com/showthread.php?t=2664561
I saw that I needed to get s-off, which requires root. Bootloader was already unlocked and so did everything here: http://forum.xda-developers.com/showthread.php?t=2273376
I installed CWM. It said to install a superuser tool so I installed SuperSU.
"You're not out of the woods yet! The stock kernel is system write protected, so you still can't modify it (changes won't "stick"). You'll have to flash a custom rom or a kernel if you want stock instead." was the next line. <-- I saw that message. Installed a kernel that he recommended: http://forum.xda-developers.com/showthread.php?t=2255900
After reboot I get SuperSU error: There is no SU binary installed and SuperSU cannot install it. If you just upgraded to Android 4.3, you need to manually re-root- consult the relevant forums for your device etc.
Can anyone help me get the proper SU Binary installed? Not a beginner to rooting as I've had had several previous phones before. Never encountered something as annoying as this.
On 4.3, 3.17.502.3.
I had the same issue when I installed 4.4.2 on my international One.
What I done to root was;
- downloaded SuperSU v1.80 zip from here.
- download SuperSu from the Play Store
- in SuperSU, select the option to install binaries via TWRP/CWM. (If it doesn't reboot to recovery, manually enter recovery)
- flash the supersu v1.80 zip and reboot
- open SuperSu and install the binaries using the normal option.
That then enabled my root. I'd tried quite a few different variations and this was the only method that worked for me.
Sent from my HTC One or Note 3 via XDA Premium 4
Thank you! Although I just managed to installed a custom ROM and managed to get root.
I followed this thread: http://forum.xda-developers.com/showthread.php?t=2664561
I flashed the Recovery_Cingular_US in fastboot. Unfortunately I'm unable to boot into stock recovery. I've been told right after you enter recovery from bootloader you press all three buttons simultaneously?
Is there a way to get into stock recovery from fastboot? Or better yet install the ROM from fastboot?
mch277 said:
Thank you! Although I just managed to installed a custom ROM and managed to get root.
I followed this thread: http://forum.xda-developers.com/showthread.php?t=2664561
I flashed the Recovery_Cingular_US in fastboot. Unfortunately I'm unable to boot into stock recovery. I've been told right after you enter recovery from bootloader you press all three buttons simultaneously?
Is there a way to get into stock recovery from fastboot? Or better yet install the ROM from fastboot?
Click to expand...
Click to collapse
You seem very confused about the whole rooting process ... what was the point in flashing the stock recovery ? Are you trying to install the OTAPkg.zip ?
what Rom are you wanting to install and whats flashing stock recovery have to do with it ?
Well, if you looked at the thread I linked, you'll see that it says to flash a stock recovery file in order to install the OTAPkg.zip
mch277 said:
Well, if you looked at the thread I linked, you'll see that it says to flash a stock recovery file in order to install the OTAPkg.zip
Click to expand...
Click to collapse
I wrote the thread you linked too
http://forum.xda-developers.com/showthread.php?t=2659374
and yes it is necessary to have stock recovery to take an OTA, but your post didn't mention taking OTA it said you had no SU installed.
to get into stock recovery
boot to bootloader
choose recovery
wait for black screen, hold vol up and then power
you will see something about sdcard fail .. ignore it till the menu comes up
then choose to flash OTAPkg.zip from sdcard
Hi,
I have a UK Nabi2 which I used Nabilab2 to install TWRP+root+google apps a while back. I needed to do the new two part OTA update, for warranty reasons, so went to install my original backup, but could not find it. I used Nabilab2full and did the stock install, which removed root and returned the device back to stock. (This also changed my nabi to a US version with no serial, FW 2.1.29. which I later found out). & at that point I still had TWRP.
I did the first two of three OTA updates (which worked), the third update crashed during install. I retried the OTA twice more but each time it crashed. The device lost TWRP after this.
Upon entering recovery with ON/Vol+ I now get <3e> recovery. Running the root.zip file from sd card fails (I assume as I am not in the correct mode or have a bad file?). The OTA updates I grabbed from the nabi wiki page (and the thread, see below) also fail.
My device does not show in fastboot. Adb sees it but when using the command, C:\adb reboot recovery, the Nabi reboots and goes to the dead android (pushing -/+ to get into) <3e> recovery, and adb at that point no longer sees the device. The nabi also disconnects once adb shell is executed. I can intsall .apk files via adb command but I still need root access to run TWRP backup manager. I can run the root.zip file via an apk installer, but when running SU it gives a message 'There is no superuser binary installed, and superSU cannot install it. This is a problem!' ...Is there another way can I install root and/or the recovery.img to the Nabi2?
(I have been following the thread here, http://forum.xda-developers.com/showthread.php?t=2041224&page=10, as well as several hours worth of reading various adb, <3e> recovery, lost root etc q&a's in other places but cannot find an answer, or it's assumed that the adb reboot recovery command is working, which mine appears not to be).
Any help or pointers in the right direction would be very appreciated.
Regards,
Smirnofred
Hi,
I have quite a similar issue with this. I flashed custom recovery and forced gapps, but now cannot flash original recovery to perform OTA update. Cannot boot into custom recovery at all.
Done a system restore so now i have lost the gapps that were pushed and cant get into recovery to flash them again :crying:
Thank you for the reply mate, sorry to hear you are in the same situation more or less.
Further reading over at Stack overflow help forums seems to lead me to believe the tablet is bricked. Loss of su/root privileges means no r/w access via adb to put the required files where they need to be, or install or TRWP.
I'm not giving up on this... well not yet. I have a ton of other work related things going on right now that I need to clear down so I can look into this a bit more seriously. I'm away till the 17th April but will check in here when I can. And, if I find a solution I will post it here.
smirnofred ;0)
smirnofred said:
Hi,
I have a UK Nabi2 which I used Nabilab2 to install TWRP+root+google apps a while back. I needed to do the new two part OTA update, for warranty reasons, so went to install my original backup, but could not find it. I used Nabilab2full and did the stock install, which removed root and returned the device back to stock. (This also changed my nabi to a US version with no serial, FW 2.1.29. which I later found out). & at that point I still had TWRP.
I did the first two of three OTA updates (which worked), the third update crashed during install. I retried the OTA twice more but each time it crashed. The device lost TWRP after this.
Upon entering recovery with ON/Vol+ I now get <3e> recovery. Running the root.zip file from sd card fails (I assume as I am not in the correct mode or have a bad file?). The OTA updates I grabbed from the nabi wiki page (and the thread, see below) also fail.
My device does not show in fastboot. Adb sees it but when using the command, C:\adb reboot recovery, the Nabi reboots and goes to the dead android (pushing -/+ to get into) <3e> recovery, and adb at that point no longer sees the device. The nabi also disconnects once adb shell is executed. I can intsall .apk files via adb command but I still need root access to run TWRP backup manager. I can run the root.zip file via an apk installer, but when running SU it gives a message 'There is no superuser binary installed, and superSU cannot install it. This is a problem!' ...Is there another way can I install root and/or the recovery.img to the Nabi2?
(I have been following the thread here, http://forum.xda-developers.com/showthread.php?t=2041224&page=10, as well as several hours worth of reading various adb, <3e> recovery, lost root etc q&a's in other places but cannot find an answer, or it's assumed that the adb reboot recovery command is working, which mine appears not to be).
Any help or pointers in the right direction would be very appreciated.
Regards,
Smirnofred
Click to expand...
Click to collapse
You need to select fastboot protocol in the menu after booting with pwr/vol buttons. Then install fastboot driver, then install TWRP. From that point the thread you linked will work.
scotia_rfc said:
Hi,
I have quite a similar issue with this. I flashed custom recovery and forced gapps, but now cannot flash original recovery to perform OTA update. Cannot boot into custom recovery at all.
Done a system restore so now i have lost the gapps that were pushed and cant get into recovery to flash them again :crying:
Click to expand...
Click to collapse
Doesn't matter if you flash the original recovery, you need to flash the original system. TWRP can do the OTA but it will fail because there are a couple of system files that were changed that fail SHA-1 checks. Don't know what version you are on or if it's a UK or US or Disney/Nick version.
aicjofs,
Thanks for the pointers! ...its most appreciated.
After checking, I do see the nabi in device manager when its in fastboot mode, but its not installed properly (it says 'Android device' but has a 'fastboot' icon with an exclamation mark under it) which would be the root of my issue I would have thought. I was certain the fastboot drivers were installed too, obviously I was wrong.
*EDIT*
Success!
I had java disabled. I also had issues with device manager switching from 'Android device' to 'Unknown device' intermittently.
I started fresh by uninstalling everything nabi/sdk/adb related. Re-installed java, sdk and adb drivers, in that order, which resulted in no conflicts or driver issues! Then when I put the nabi into 'fastboot protocol' the second menu then appeared (which it was not doing previously). I flashed the 2.3.3.0 TWRP recovery image.
Now I have some more reading to do about what image I need to put back onto the nabi.
Thank you.
*EDIT*
Thanks again.
Smirnofed.
smirnofred said:
aicjofs,
Thanks for the pointers! ...its most appreciated.
After checking, I do see the nabi in device manager when its in fastboot mode, but its not installed properly (it says 'Android device' but has a 'fastboot' icon with an exclamation mark under it) which would be the root of my issue I would have thought. I was certain the fastboot drivers were installed too, obviously I was wrong.
*EDIT*
Success!
I had java disabled. I also had issues with device manager switching from 'Android device' to 'Unknown device' intermittently.
I started fresh by uninstalling everything nabi/sdk/adb related. Re-installed java, sdk and adb drivers, in that order, which resulted in no conflicts or driver issues! Then when I put the nabi into 'fastboot protocol' the second menu then appeared (which it was not doing previously). I flashed the 2.3.3.0 TWRP recovery image.
Now I have some more reading to do about what image I need to put back onto the nabi.
Thank you.
*EDIT*
Thanks again.
Smirnofed.
Click to expand...
Click to collapse
Somewhere in that post you linked I put a pretty good procedure for getting a UK Nabi to the latest OS, hopefully you will be up and running in no time.
I'm there, finally. Using the link to the three part install you posted. http://forum.xda-developers.com/showthread.php?t=2041224&page=10 post #98
I'm now @ 2.2.2 (I think), 4.1jb, with 2.6.3.0 twrp recovery. First thing I did was make a full backup (once it was all working 100%).
I had a minor issue with SU trying to install repeatedly once I put the 2.2+ stock image (+modded ota), which sent the nabi back to <3e> recovery. But I just flashed it back to 2.6.3.0 with fastboot.
Many thanks ;0)
smirnofred said:
I'm there, finally. Using the link to the three part install you posted. http://forum.xda-developers.com/showthread.php?t=2041224&page=10 post #98
I'm now @ 2.2.2 (I think), 4.1jb, with 2.6.3.0 twrp recovery. First thing I did was make a full backup (once it was all working 100%).
I had a minor issue with SU trying to install repeatedly once I put the 2.2+ stock image (+modded ota), which sent the nabi back to <3e> recovery. But I just flashed it back to 2.6.3.0 with fastboot.
Many thanks ;0)
Click to expand...
Click to collapse
Hi Smirnofred, I have similiar issues to you, and i'm wondering of you can help. The 2.2 file from dropbox is no longer available, have you still got it? and would you kindly upload it somewhere for me if you have time. It would be much appreciated. :good:
James
Has anyone got any pointers on how to get out of recovery on the oneplus x. The phone 'was' rooted, but I unrooted to allow the update. However it failed and now just boots inot recovery.
I have wiped data and cache, formatted device, but no luck in getting the phone to boot. It hasn't had a custom rom or recovery.
How do I go about flashing the latest update manually?
I'm able to get into fastboot mode, should I update the recovery to stock? This seems a little weird as I haven't replaced the stock rom, but I was wondering if this might help.
veearrsix said:
I'm able to get into fastboot mode, should I update the recovery to stock? This seems a little weird as I haven't replaced the stock rom, but I was wondering if this might help.
Click to expand...
Click to collapse
If you have stock recovery, just download the full OS and install it. However, you will need to have a computer and a way to save the ROM onto the micro SD card.
Full ROM 2.1.3
http://forum.xda-developers.com/showthread.php?t=3244996
If you can't do that and you have an unlock bootloader. You can flash twrp, then adb sideload the ROM onto the phone. Then re-flash stock recovery again and install the ROM.
You can flash OTA from twrp, follow this thread.
http://forum.xda-developers.com/showthread.php?t=3245185
Sent from my ONE E1005 using Tapatalk
So,
I have added OnePlusOxygen_14_OTA_004_all_201511031712.zip to an sd card. Booted into recovery with the sd card installed, select 'Install from local' and nothing happens.
Am I missing something?
Also, I am unable to unlock the bootloader as the enable oem unlock wasn't set and I'm now unable to boot into the system to set it.
Also, Im pretty sure usb debugging wasn't enabled either.
Did you manage to fix your phone? I had a similar issue, what I did was;
Load the full ROM into the root of my internal storage (not SD card)
Boot into stock recovery
Install from local - this should list the ROM
Select the ROM and follow the instructions.
How do you load the ROM onto the internal storage? I am not able to adb push in sideload mode and adb sideload doesn't work.
So I've tried to follow both of the methods listed here, but I've had no luck.
Trying the sd card route I am not offered the option to install from sd card, I only get 'Install from local' and 'Install from USB'.
When I try to 'Install from USB' I receive the error:
error: protocol fault (no status)
And the message on the phone says installation failed.
Do I have any other options?
I have the same problem
veearrsix said:
Has anyone got any pointers on how to get out of recovery on the oneplus x. The phone 'was' rooted, but I unrooted to allow the update. However it failed and now just boots inot recovery.
I have wiped data and cache, formatted device, but no luck in getting the phone to boot. It hasn't had a custom rom or recovery.
How do I go about flashing the latest update manually?
Click to expand...
Click to collapse
i have got the same problem. Did you solved it ?
No,
I ended up returning the phone to oneplus. They sorted it (or gave me another one).
veearrsix said:
So I've tried to follow both of the methods listed here, but I've had no luck.
Trying the sd card route I am not offered the option to install from sd card, I only get 'Install from local' and 'Install from USB'.
When I try to 'Install from USB' I receive the error:
error: protocol fault (no status)
And the message on the phone says installation failed.
Do I have any other options?
Click to expand...
Click to collapse
Did you fix your phone yet
veearrsix said:
Has anyone got any pointers on how to get out of recovery on the oneplus x. The phone 'was' rooted, but I unrooted to allow the update. However it failed and now just boots inot recovery.
I have wiped data and cache, formatted device, but no luck in getting the phone to boot. It hasn't had a custom rom or recovery.
How do I go about flashing the latest update manually?
Click to expand...
Click to collapse
i had a similar issue. i installed twrp and backed up my rom. restored rom to get ota but it failed everytime i tried. tried to flash stock recovery but locked the bootloader before flashing stock recovery using fastboot oem lock command and the stock recovery installation failed everytime as the bootloader was locked. tried fastboot oem unlock with status success but while checking always show me bootloader lock status true. The bootloader won't unlock unless you have a stock recovery. installed cm13 using twrp, copied stock recovery and oxygen os zip 2.2.0 downloaded from oneplus website to internal memory, flashed stock recovery using twrp and flashed stock rom using stock recovery.
completed 2.2.1 ota and it worked.
How to flash stock recovery using twrp recovery... Please send me link
Thanks in advance
veearrsix said:
Has anyone got any pointers on how to get out of recovery on the oneplus x. The phone 'was' rooted, but I unrooted to allow the update. However it failed and now just boots inot recovery.
I have wiped data and cache, formatted device, but no luck in getting the phone to boot. It hasn't had a custom rom or recovery.
How do I go about flashing the latest update manually?
Click to expand...
Click to collapse
Just download this file http://downloads.oneplus.net/oneplus-x/oneplus_x_oxygenos_2.2.3/ and paste it into the sd card as it is dont extract and do not paste that file into any folders. Select install from local then select sd card, you will see this file first on the list select it after getting success just reboot it!
Done Enjoy!
no solutions yet? i have the same problem as well.
debbensakye said:
no solutions yet? i have the same problem as well.
Click to expand...
Click to collapse
Of course there are solutions, but explain where you are exactly.
Or you can use the Mega Unbrick Guide
My Padfone S screen is broken, fully black and out of function. I can't follow the some of the root guide to install TWRP and load the SuperSU zip to it because the screen is broken. I can just use my Padfone with the padfone station, so is there any way to root it? Thanks.
I did my Padfone X about an hour ago! I realize its not the same, but I'll give you a run-down of what I did and maybe it will help!
So I rooted it the dirty way first with KingoRoot, because I just really wanted to debloat. Downloaded the app, nothing complicated about it, I just don't like it and personally I don't trust this root provider for a daily driver. Prefer SuperUser or SuperSU.
Next, I spent a long while poring over threads full of dead links trying to find a CWM or TWRP recovery, and finally stumbled across one, which also contained the flashable bootloader unlocker. So I put the phone in fastboot mode (power the phone off, hold power + vol up) and ran "fastboot boot recovery.img", which is what I renamed the TWRP recovery file to. To my surprise, it booted and mounted the internal storage! So I copied the bootloader unlocker zip, flashed it, rebooted. Entered fastboot again, "fastboot flash recovery recovery.img" and boom! TWRP installed and working.
My next step will be to replace KingoRoot with SuperSU. I tried it via the normal flashable zip, but it failed somehow. The flash completed but when I rebooted, the SU binaries were missing or something. I lost root access. Good thing that the backup and restore works in TWRP
I'll post a full "how I did it" guide when I'm done. Until then, hopefully something I learned will help you!
yes, it can be root
Hi, I use TWRP 3.0.0 from quarkx
http://quarx2k.ru/asus_padfone_s/
and install magisk
https://forum.xda-developers.com/app...mless-t3473445
it's really work for MM rom
Hello everyone,
so I have been playing around with my HTC U11. I unlocked the bootloader and installed the newst TWRP version. Then I flashed it to Lineage 16. However I could not install the HTC Edge Sense App and since I couldnt find any answers to that problem decided to flash back to stock rom and then update to Android 9.0 and get my Edge Sense back.
So I checked for my device CID which is HTC_034 and downloaded myself the stock rom from the getdroidtips stock firmware collection (cant post link because I am new)
I did the MD5 Checksum and everything was fine. However when I try to sideload it via adb i get a zip file corrupt error and TWRP stops it. Then I tried pushing it and installing it through the install function of TWRP. I can push it onto the device but when I want to install it I get the same error again. Things I tried so far:
1. used an older version of TWRP
2. all the 4 stockroms available for the HTC_034 on said link
3. load the .zip onto an sd card, enter it and tell TWRP to install from there - didnt work either.
4. rename the .zip to package.zip (read it somewhere)
Everytime I get the Error that the .zip is corrupt. Checksums of all the files are ok...
Has anyone an idea what else I can do? I would actually be fine with lineage 16 if I could just get my HTC Edge Sense back (
Thanks in advance for your help
Headcannon: what if the problem ia for some reason the twrp? Could i somehow flash the stock rom without going through the TWRP?
I am not talking about removing it. I am talking about somehow flashing without using it. Maybe via adb or odin?
Then the stockrom should be able to install. If something goes wrong I can still boot into recovery and use TWRP to get LOS16 back.
Ok so since I read somewhere that on the pixels root access was necessary to get HTC Edge Sense running I installed Lineage 16, added GAPPS and then used Magisk to get root access.
I still can't install HTC Edge Sense. I even downloaded the apk and pushed it onto the phone but the install always stops and tells me it can't finish
So for now I can neither have stock rom nor Edge Sense - any suggestions because I am slowly running out of ideas