Database Info

Root official ics for desire s

has anyone already tried to root there official ics Rom that was released yesterday? And how?
Sent from my HTC Desire S using xda premium

Once you've installed the RUU, use ADB to push 4ext recovery, then reboot into recovery and flash the Supervisor 3.1.3 file - once you then reboot into the full system again you will have root access and can install the 4ext updater from the Play Store and update recovery to the latest version.

SimonTS said:
Once you've installed the RUU, use ADB to push 4ext recovery, then reboot into recovery and flash the Supervisor 3.1.3 file - once you then reboot into the full system again you will have root access and can install the 4ext updater from the Play Store and update recovery to the latest version.
Click to expand...
Click to collapse
anyone can confirm this is working?

mayurh said:
anyone can confirm this is working?
Click to expand...
Click to collapse
Yes. I can - that's why I posted the solution.
Or you can just use the search button. :banghead:

SimonTS said:
Once you've installed the RUU, use ADB to push 4ext recovery, then reboot into recovery and flash the Supervisor 3.1.3 file - once you then reboot into the full system again you will have root access and can install the 4ext updater from the Play Store and update recovery to the latest version.
Click to expand...
Click to collapse
Simon your DS was S-ON and you got it S-OFF with this procedure.
You pushed the 4ext recovery on a S-ON bootloader, right?
thank you

linqdesires said:
Simon your DS was S-ON and you got it S-OFF with this procedure.
You pushed the 4ext recovery on a S-ON bootloader, right?
thank you
Click to expand...
Click to collapse
No, my DS was S-Off - done with XTC-Clip 18 months ago.

Go to recovery mode;
choose .zip from sd card
Flash this
100%

potencia said:
Go to recovery mode;
choose .zip from sd card
Flash this
100%
Click to expand...
Click to collapse
give thanks is for free

For the people, like me, who have only done the HTCdev unlock ( S-ON ), it's quite easy to update the software/ROM using the RUU.
After downloading the RUU from here : http://forum.xda-developers.com/showthread.php?t=1857478 I just immediately ran it, but it failed with an error along the lines of : RUU, security fail! update fail!
So after a bit of googling around I figured that the RUU might simply not be happy with the phone being in an unlocked state, so after doing the following the RUU ran successfully :
1. Re-lock the bootloader with the "fasboot oem lock" command. The output after running the command shows the lock process was successful but moaned about something else failing, still not sure what that was. So after doing this my phone was kinda stuck in the bootloader, where it says ***relocked*** at the top and ***security warning!*** right underneath it. Everytime I reboot or powercycle it would just boot straight back into the bootloader with the warnings, which worried me a little bit.
2. In the bootloader I selected fastboot and connected the USB cable, and then I ran the RUU again. This time it completed successfully after some time. My HTC sync was installed but not running, so seems like that isn't even needed ?
And that's actually it. This process obviously puts the phone in a relocked state, and an overall factory configuration, it also restores the recovery ROM to the factory image or whatever.

No success
Hi,
I try to root my S-off /XTC Clip/ device, BUT:
1. 4ext pushed with adb - OK
2. I try to install recovery - 4ext wants busybux
3. I downloaded busybox - but it wants a rooted devices I got a message that "unrooted device" and busybox is closed
So I don't have recovery menu
What could be the solution ?

w_hy said:
Hi,
I try to root my S-off /XTC Clip/ device, BUT:
1. 4ext pushed with adb - OK
2. I try to install recovery - 4ext wants busybux
3. I downloaded busybox - but it wants a rooted devices I got a message that "unrooted device" and busybox is closed
So I don't have recovery menu
What could be the solution ?
Click to expand...
Click to collapse
Read the instructions correctly. Install RUU. Put phone into FastBoot mode. Use ADB to push recovery to phone. Reboot into recovery. Flash superuser from zip. Reboot phone properly. Install BusyBox from Play Store.

steps made by me
SimonTS said:
Read the instructions correctly. Install RUU. Put phone into FastBoot mode. Use ADB to push recovery to phone. Reboot into recovery. Flash superuser from zip. Reboot phone properly. Install BusyBox from Play Store.
Click to expand...
Click to collapse
1. Install RUU. -- OK
2. Put phone into FastBoot mode. -- OK
3. Use ADB to push recovery to phone. -- OK
4. Reboot into recovery. -- NOT OK -- there is no recovery menu just the red triangle.

w_hy said:
1. Install RUU. -- OK
2. Put phone into FastBoot mode. -- OK
3. Use ADB to push recovery to phone. -- OK
4. Reboot into recovery. -- NOT OK -- there is no recovery menu just the red triangle.
Click to expand...
Click to collapse
Post the exact steps and output of what you're doing. Recovery obviously isn't getting successfully installed. Which recovery are you using as well?

Isn't fastboot flash recovery recovery.img the command to flash a recovery?
Sent from my Desire S using xda app-developers app

c.m.b said:
Isn't fastboot flash recovery recovery.img the command to flash a recovery?
Click to expand...
Click to collapse
Yes

SimonTS said:
Post the exact steps and output of what you're doing. Recovery obviously isn't getting successfully installed. Which recovery are you using as well?
Click to expand...
Click to collapse
Steps made by me:
1. installed RUU -- OK
2. downloaded recovery.zip, extracted recovety.img (same directory as adb/fastboot)
3. restart phone to bootloader, fastboot usb mode
4. used "fastboot flash recovery recovery.img" command
5. got the next output:
G:\0\1>fastboot flash recovery recovery.img
sending 'recovery' (3768 KB)... OKAY [ 0.655s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.655s
In the recovery.zip file there is a version file:
ext.version=1005.3.0
ext.build=0
and recovery.md5:
3fd4750734837f6bce55b63def1e0a8b

w_hy said:
Steps made by me:
1. installed RUU -- OK
2. downloaded recovery.zip, extracted recovety.img (same directory as adb/fastboot)
3. restart phone to bootloader, fastboot usb mode
4. used "fastboot flash recovery recovery.img" command
5. got the next output:
G:\0\1>fastboot flash recovery recovery.img
sending 'recovery' (3768 KB)... OKAY [ 0.655s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.655s
In the recovery.zip file there is a version file:
ext.version=1005.3.0
ext.build=0
and recovery.md5:
3fd4750734837f6bce55b63def1e0a8b
Click to expand...
Click to collapse
What#s your current hBoot? And make sure you using the recovery files from 4EXT_Recovery_v2.2.7_RC5.zip

SimonTS said:
What#s your current hBoot? And make sure you using the recovery files from 4EXT_Recovery_v2.2.7_RC5.zip
Click to expand...
Click to collapse
hboot is 2.00...
Can you give me a link for EXT_Recovery_v2.2.7_RC5.zip, please?

w_hy said:
hboot is 2.00...
Can you give me a link for EXT_Recovery_v2.2.7_RC5.zip, please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=21895635&postcount=172

SimonTS said:
http://forum.xda-developers.com/showpost.php?p=21895635&postcount=172
Click to expand...
Click to collapse
So:
hboot: 2.02.0002
s-off /xtc clip/
recovery.img: what you said /puted in new directory togeather with adb.exe and fastboot.exe/
command: as before
result: the same:
G:\0\4>fastboot flash recovery recovery.img
sending 'recovery' (5624 KB)... OKAY [ 0.987s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.988s

Cant install new recovery

Hi, ive been trying to S-off and root my HTC sensation using this guide
http://forum.xda-developers.com/showthread.php?t=1870233
ive managed to get up to step 2, but unable to flash a new recovery using instructions in this guide and also whilst trying kgs utility…. Im pulling my hair out tbh been at it for hours…
so basically, I unlocked my phone, then have got s-off..but now cant get new recovery to get rooting.
when I use the utility in theafore mentioned guide. It either cant find device or just hangs. When I use the kgs utility, it looks promising until I get the message the system cannot find the bacth label specified - dl_4ext_found
any ideas?

try this
boot your device into bootloader
connect your device into pc via usb(it should say fastboot usb)
now in your pc place the recovery.img in the folder where you have adb and fastboot files
open a command window in that folder and do this command
fastboot flash recovery recovery.img

hi rzr86, thanks for the help. tried what you said, but it tells me remote not allowed. any ideas?
c:\android>fastboot flash recovery recovery.img
sending 'recovery' (6348 KB)...
OKAY [ 1.619s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.936s
c:\android>

gdallas said:
hi rzr86, thanks for the help. tried what you said, but it tells me remote not allowed. any ideas?
c:\android>fastboot flash recovery recovery.img
sending 'recovery' (6348 KB)...
OKAY [ 1.619s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.936s
c:\android>
Click to expand...
Click to collapse
hmm ok,
do you have htc drivers installed?
also check if you are using 2.0 usb ports
enable also usb debugging mode
edit:i just inform you also that the recovery can be renamed as recovery.img
i mean when you perform the command do it like this
fastboot flash recovery <the name of recovery>

rzr86 said:
hmm ok,
do you have htc drivers installed?
also check if you are using 2.0 usb ports
enable also usb debugging mode
edit:i just inform you also that the recovery can be renamed as recovery.img
i mean when you perform the command do it like this
fastboot flash recovery <the name of recovery>
Click to expand...
Click to collapse
hi, i noticed that even though I now have S-off, my phone went back to "locked" status. So i tried uinllocking it again, and currently it is now. I flashed the recoevry again as per your instruiction, and seems to have worked!! but not really sure, how would i tell? is there a simmilar way to root it too as when i use the kgs utitly is now goes into a boot loop when i attempt to root.
thanks

gdallas said:
hi, i noticed that even though I now have S-off, my phone went back to "locked" status. So i tried uinllocking it again, and currently it is now. I flashed the recoevry again as per your instruiction, and seems to have worked!! but not really sure, how would i tell? is there a simmilar way to root it too as when i use the kgs utitly is now goes into a boot loop when i attempt to root.
thanks
Click to expand...
Click to collapse
that's why you couldn't perform the command
if i remember well after S-OFF an unlocked bootloader goes again locked
but there was no need to unlock it again
you could use an eng hboot(juopunutbear) which is unlocked
nevermind
flash this zip from recovery now
http://download.chainfire.eu/310/SuperSU/UPDATE-SuperSU-v1.04.zip
it will give you root

hi and thanks..
So i should capy this to my SD card, then what? sorry for the noob questions.

gdallas said:
hi and thanks..
So i should capy this to my SD card, then what? sorry for the noob questions.
Click to expand...
Click to collapse
Hi,
Yes.
Copy to the root of your sd card.
Flash like a ROM.

malybru said:
Hi,
Yes.
Copy to the root of your sd card.
Flash like a ROM.
Click to expand...
Click to collapse
thanks gents

hmm, i think i must be doing this wrong guys. it thought I flashed the recoevery ok, but then when i hit powerdown on the recovery option, it goes to an HTC logo for a while, then i see my vodafone logo etc and then have a clean install of the orginal rom i guess.
Where am i going wrong?
Many thanks

hey man u just saved my life lol
rzr86 said:
try this
boot your device into bootloader
connect your device into pc via usb(it should say fastboot usb)
now in your pc place the recovery.img in the folder where you have adb and fastboot files
open a command window in that folder and do this command
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
My htc sensation was just rebooting couldnt get into recovery, i had clockwordmod recovery, i thought i lost my phone, i searched on xda and saw ur post, and i fixed my phone thnx to you,
So just wanted to say thank you very much.

[Q] AT&T HTC One X Bricked and need advice

Hi,
I have an AT&T HTC One X with no OS. I wiped it when I was trying to flash a custom ROM.
I only have access to bootloader and TWRP. Fastboot is working fine but TWRP is not. It does
mount properly, and adb sideload fails as well. I am using a Windows 7 PC and used a USB 2.0 port.
I installed some HTC Drivers from here:
http://forum.xda-developers.com/showthread.php?t=2217396
but it still says "device drivers failed to install" when I boot into recovery.
When I try to mount, it does not let me mount the sdcard. I see an E: drive on my
PC but it is inaccessible.
I have S-On, my bootloader is unlocked, and I have hboot version 2.14 if that info helps.
Does anybody have any suggestions as to what I can try next?

First thing you need to do is clear your post up a bit. You said you have access to TWRP but it isn't working, can you elaborate on that please?
You also said that it does mount, but then you said later it doesn't mount, which is it?
Have you performed a factory reset from the bootloader at any point?
Exactly which ROM(s) did you try to install? I need the exact filename(s) please.
Did you remember to flash the boot.img with fastboot after flashing the ROM?
Do you have a TWRP backup on your phone?
Please answer all questions with as much relevant detail as possible, that'll aid me to help you properly.
Sent from my Evita

I helped him over teamviewer so I can clarify the situation. He can't mount in TWRP, it must of been a typo. It seems he cleared everything when he was trying to wipe to flash a rom. I believe it was ViperXL. He has no backup and sideload does not work as well. Hopefully that will clear things up a little bit more. I installed some newer HTC Drivers since the ones he had were old. The only thing that works seems to be fastboot at this point.
Sent from my HTC One X using Tapatalk

timmaaa said:
First thing you need to do is clear your post up a bit. You said you have access to TWRP but it isn't working, can you elaborate on that please?
You also said that it does mount, but then you said later it doesn't mount, which is it?
Have you performed a factory reset from the bootloader at any point?
Exactly which ROM(s) did you try to install? I need the exact filename(s) please.
Did you remember to flash the boot.img with fastboot after flashing the ROM?
Do you have a TWRP backup on your phone?
Please answer all questions with as much relevant detail as possible, that'll aid me to help you properly.
Sent from my Evita
Click to expand...
Click to collapse
Sorry it was a Typo, I was not able to mount at all. The error said "unable to mount /sdcard"
Yes I have tried performing a factory reset from bootloader but the phone restarts and comes back to TWRP and then same thing.
I tried installing the ViperXL ROM but was not successful.
I was not able to flash the ROM and I tried to fix that but meanwhile looks like I wiped all what I had on my Phone, so no but I did try to flash a new boot.img after and it didnt work.
I dont think I have any TWRP backup on my phone, even though I tried flashing new TWRP but all failed.

Ok first thing, don't ever perform a factory reset from the bootloader because it corrupts your sd card. That's why you're experiencing problems now. You need to wipe the sd card/internal storage using TWRP 2.6 to make it usable again. If you don't currently have TWRP 2.6 installed you'll need to do that. Download it 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 should be able to mount your sd card using TWRP and copy a ROM across to flash.
Sent from my Evita

timmaaa said:
Ok first thing, don't ever perform a factory reset from the bootloader because it corrupts your sd card. That's why you're experiencing problems now. You need to wipe the sd card/internal storage using TWRP 2.6 to make it usable again. If you don't currently have TWRP 2.6 installed you'll need to do that. Download it from . 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 should be able to mount your sd card using TWRP and copy a ROM across to flash.
Sent from my Evita
Click to expand...
Click to collapse
So I followed all the above steps as noted; I had TWRP 2.6.3.0 earlier, I flashed the new TWRP 2.6.0.0 from the link you provided.All
successfully done.
-------------------------------------------------------------------------------------------------------
C:\Fastboot>fastboot devices
HT29WW300913 fastboot
C:\Fastboot>fastboot flash recovery "openrecovery-twrp-2.6
.0.0-evita.img"
sending 'recovery' (8000 KB)... OKAY [ 1.530s]
writing 'recovery'... OKAY [ 1.900s]
finished. total time: 3.430s
C:\Fastboot>fastboot erase cache
erasing 'cache'... OKAY [ 0.120s]
finished. total time: 0.120s
C:\Fastboot>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.070s]
finished. total time: 0.070s
---------------------------------------------------------------------------------------------------------
I rebooted into recovery, still came up as TWRP 2.6.3.0, then I went to TWRP reboot and chose Recovery, phone rebooted into TWRP 2.6.0.0
Tried mounting (could not select /sd card and /cache(expected as we erased it)) and ADB sideload, got the same errors as before. Unable to mount /sdcard.
Rebooted again and it displayed TWRP 2.6.3.0

Did you wipe the sd card/internal storage like I said before trying to mount it?
Sent from my Evita

timmaaa said:
Did you wipe the sd card/internal storage like I said before trying to mount it?
Sent from my Evita
Click to expand...
Click to collapse
Yes I did

And which recovery is currently installed?
Sent from my Evita

timmaaa said:
And which recovery is currently installed?
Sent from my Evita
Click to expand...
Click to collapse
Its 2.6.3.0, but in recovery when I go into option TWRP reboot and chose Recovery button, phone reboots into TWRP 2.6.0.0 and when I reboot it again, its 2.6.3.0

That's really screwy. I think you should try installing recovery again. What happens when you boot the phone normally?
Sent from my Evita

timmaaa said:
That's really screwy. I think you should try installing recovery again. What happens when you boot the phone normally?
Sent from my Evita
Click to expand...
Click to collapse
Ok good news, something happened, I tried all the steps again carefully and now I see TWRP 2.6.0.0 on boot and I am able to mount the sdcard and my computer now recognises the phone and I can manually copy files on to it.
Now in order to not mess it up anymore, should I just copy ViperXL ROM or should I use ADB sideload?

tapukakababa said:
Ok good news, something happened, I tried all the steps again carefully and now I see TWRP 2.6.0.0 on boot and I am able to mount the sdcard and my computer now recognises the phone and I can manually copy files on to it.
Now in order to not mess it up anymore, should I just copy ViperXL ROM or should I use ADB sideload?
Click to expand...
Click to collapse
Either one should be fine. If you have S-ON and the phone gets stuck on the HTC screen, you have to flash the boot.img. here's how to do it.
1. On your PC in the ViperXL.zip, take out the boot.img and put it in the directory where you have the adb and fastboot files.
2. Boot into fastboot.
3.Open cmd. Change the directory to the folder where you have those files.
4.type "fastboot flash boot boot.img"
5. Reboot the phone.
The phone should boot.
Sent from my One Xl using Tapatalk

Definitely install through TWRP. You shouldn't need to flash a boot.img because Viper uses an aroma installer which does that for you. But, if for some reason it doesn't work just flash the boot.img via fastboot.
Sent from my Evita

timmaaa said:
Definitely install through TWRP. You shouldn't need to flash a boot.img because Viper uses an aroma installer which does that for you. But, if for some reason it doesn't work just flash the boot.img via fastboot.
Sent from my Evita
Click to expand...
Click to collapse
So I flashed the boot image, then copied ViperXL and installed it through TWRP, it failed.

Exactly which error is it giving you? Did you check the md5 of the downloaded file? Are you still on TWRP 2.6?
Sent from my Evita

timmaaa said:
Exactly which error is it giving you? Did you check the md5 of the downloaded file? Are you still on TWRP 2.6?
Sent from my Evita
Click to expand...
Click to collapse
No I did not check the MD5, yes I'm on TWRP 2.6.0.0 and the errors it gives are as follows:
unable to mount '/cache'
unable to open zip
Error flashing zip

Always check the md5. It's possibly corrupt.
Sent from my Evita

timmaaa said:
Always check the md5. It's possibly corrupt.
Sent from my Evita
Click to expand...
Click to collapse
Yup redownloaded the file, checked/compared MD5, copied it back to the phone, removed the previous bad copy, flashed ROM successfully..., as per the message but system reboots to recovery.. is that expected?
And I still see both the TWRP's 2.6.3.0 and 2.6.0.0 the phone needs couple reboots in order to get to TWRP 2.6.0.0 but automatic reboot is in TWRP 2.6.3.0 whats the deal here?

I have no idea why your recovery is acting like that. Hopefully someone else can chime in on that.
Sent from my Evita

Recover a 4.4.4 downgrade brick! (Temporal solution)

So, i have noted a increased number of threads about people who have soft-bricked their phones downgrading from 4.4.4 GPE after recieving the OTA, since it includes a new partition table and there's no firmware image yet.
Worry not, i have found a solution for your problem. This method only let's you use custom ROMs (sadly), but it's meant to be a temporal solution while we wait for a 4.4.4 GPE image anyways.
So, without further ado, here's my fix:
You will need:
-The good ol' Android SDK
http://developer.android.com/sdk/index.html#download
-Motorola drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
-A custom recovery. I recommend TWRP, since is the only one i have tested.
Official TWRP Images for Moto G: http://techerrata.com/file/twrp2/xt1032/openrecovery-twrp-2.7.1.1-xt1032.img
-The gpt.bin from 4.4.4 (this is the partition table)
I extracted it from the OTA file and uploaded to my Dropbox: https://dl.dropboxusercontent.com/u/82658555/gpt.bin
-A custom ROM of your choice (obligatory) + GApps (optional)
What to do:
Once you have the Android SDK, decompress the folder sdk/platform-tools in a place of your choice.
Inside this folder, put gpt.bin, the custom recovery image and the ROM and GApps zip's.
Start your phone on fastboot. Connect it.
Inside your decompressed platform-tools folder, hold shift and right click inside the folder. Select "Open command window here".
Make sure your phone is properly connected by typing "fastboot devices" (without the quotation marks). The command prompt should show your phone serial number.
Now we start the real deal. Fist of all, flash gpt.bin using this command:
fastboot flash partition gpt.bin
Make sure it ends on "OKAY"
Now, flash the recovery
fastboot flash recovery nameoftherecoveryfile.img
Once this is done, enter recovery using the fastboot menu on your phone (use Vol- to highlight "Recovery", and then press Vol+)
Now your phone should boot on recovery mode. If you recieve an error like "Can't mount /system/", don't worry, this is normal (there's no system partiton yet, after all). Now you can use ADB command with your PC. Once again, to be sure everything is connected properly,tyipe on the console:
adb devices
Once that is done, it's time to give your phone the custom ROM, so you can flash it. Type (or copy/paste)
adb push NameoftheROMfile.zip /sdcard/ NameoftheROMfile.zip
If you have GApps, do the same for those
adb push GApps.zip /sdcard/ GApps.zip
Now you can finally disconnect your phone from the PC! You are almost done, select "Install" in your recovery, and flash your ROM zip, then the GApps if you have them.
Once it's done, you can reboot to system.
And you will have a working Moto G again!!
Enjoy it, and don't brick it again

the guide isw missing some info (like enter flash sideload on recovery)
and that weird command push does not work, i have to use other command
i managed to install another rom after being bricked but still that rom won´t start, i have to try another
still thanks a lot
i did not download android sdk, i have my folder with adb files
also when i am in recovery, i type fastboot devices and nothing happens, but still the recovery could receive the file

maurocds said:
the guide isw missing some info (like enter flash sideload on recovery)
and that weird command push does not work, i have to use other command
i managed to install another rom after being bricked but still that rom won´t start, i have to try another
still thanks a lot
i did not download android sdk, i have my folder with adb files
also when i am in recovery, i type fastboot devices and nothing happens, but still the recovery could receive the file
Click to expand...
Click to collapse
From my experience, you don't have to enter sideload mode in recovery to push a file, sideload mode is for pushing OTAs. And remember, the ADB push command requires you to put the exact name of the file to transfer twice, that could have failed for you.
You can't use fastboot devices on recovery because you can only use ADB commands in recovery, you were supposed to use "adb devices".

Or you can restore 4.4.2 nandroid backup using recovery if you made one. But after that you need to flash correct baseband.

masa86 said:
Or you can restore 4.4.2 nandroid backup using recovery if you made one. But after that you need to flash correct baseband.
Click to expand...
Click to collapse
Not many people do NAND backups these days.
Sad, because they're really useful, and there wouldn't be as many "HALP BRICKED PHONE" threads.

It Doesn't work only say failed xD

Fresroqir said:
It Doesn't work only say failed xD
Click to expand...
Click to collapse
Care to explain what failed?

tatazeuz said:
Care to explain what failed?
Click to expand...
Click to collapse
The install for the custom rom and gapps

Fresroqir said:
The install for the custom rom and gapps
Click to expand...
Click to collapse
What error did you receive? Did you flashed gpt.bin correctly?

tatazeuz said:
What error did you receive? Did you flashed gpt.bin correctly?
Click to expand...
Click to collapse
i just received failed at twrp recovery and how do i flashed gpt.bin right because it say okay.
And what does gpt.bin actually? (i am a noob)

Fresroqir said:
i just received failed at twrp recovery and how do i flashed gpt.bin right because it say okay.
And what does gpt.bin actually? (i am a noob)
Click to expand...
Click to collapse
got.bin is the partition table of the Moto G. Its the file that indicates to the phone the size, name and number of partitions it should have.
So, I know TWRP said in red letters Failed, but I'm interested what is the specific error, what did it said on the command prompt of TWRP.

Error flashing zip sdcard pa falconzip
and then there comes this updating partitution details and do i need to put the rom twice in the cmd?

and do i need a cutom rom with 4.4.4????????

yes, exactly what rom did you use to recover??????????
paranoid did not work, installed fine but stuck at logo loading

Fresroqir said:
and do i need a cutom rom with 4.4.4????????
Click to expand...
Click to collapse
maurocds said:
yes, exactly what rom did you use to recover??????????
paranoid did not work, installed fine but stuck at logo loading
Click to expand...
Click to collapse
I used the latest version of PA + Stock GApps

Thanks!
Edit: Nope... Still same problem. Looks like the gpt file flashed but everything else is the same.

It still doesn't work for me i got th whole time failed and i don't know what i need to do ;(
It says: Z:\New folder\Android>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.025s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.372s]
finished. total time: 0.399s
is that good?
EDIT:it looks that sideload works and not that push command
EDIT: nvm i am stuck at bootanimation
EDIT: this wont work it says failed all the time at twrp

I'm kind of confused. Why couldn't people downgrade and go back to stock by reflashing all of the files from an older stock image, including the motoboot and gpt? I would think this would work...although with people saying that they are unable to downgrade I'm not willing to try upgrading to 4.4.4 myself.
What errors are people seeing if they try to flash gpt and motoboot from, say, 4.4.2 stock or 4.4.2 GPE?
-- Nathan

not work for me..
every recovery stay on black screen and return vibration on touch screen
:/
help > http://forum.xda-developers.com/moto-g/help/help-downgrading-cm4-4-4-to-stock4-4-3-t2804228

i think this fix doesn't work because i can only sideload my roms and gapps xD

[UNOFFICIAL] [RECOVERY] [OnePlus 7 Pro] OrangeFox Recovery Project [R10.1]

[Deleted]

The flashing instruction makes no sense to me

Spookybear said:
INSTALLATION:
0. Backup your ROM, your data, your internal storage, and your settings/apps, to an external device
1. Reboot to your custom TWRP-based Recovery
2. The device will automatically reboot into OrangeFox recovery after installation (allow this to happen)
3. Enjoy!
(Note: There is no zip file because this recovery is too big to fit in the ramdisk.
Click to expand...
Click to collapse
Can you please clarify this?
I assume install .IMG to Ramdisk? It will likely come up, so just want to cover all bases.

gorilla p said:
Can you please clarify this?
I assume install .IMG to Ramdisk? It will likely come up, so just want to cover all bases.
Click to expand...
Click to collapse
I tried that...no dice...
Flash to both _a and _b using trwp but recovery does not boot... so back to trwp til some future info...

I flashed via TWRP, via flash .img to ramdisk, rebooted to recovery and nothing.
Stuck at "Bootloader unlocked" screen

Tried to boot via fastboot and it failed.

Was this recovery tested on the OP7 Pro? If so, what ROM was being used and what was the flashing process?

Gungrave223 said:
The flashing instruction makes no sense to me
Click to expand...
Click to collapse
Sorry, fixed the instructions.

avid_droid said:
Yeah directions are honestly the worst I've seen on XDA yet.
Click to expand...
Click to collapse
Sorry, fixed the instructions.

I have a feeling these new instructions aren't going to work either, considering we don't have a recovery partition.

Spookybear said:
Sorry, fixed the instructions.
Click to expand...
Click to collapse
still no dice
HTML:
Writing 'recovery'
FAILED (remote: '(recovery_a)
No such partition'

I guess the command should be
fastboot boot /path to recovery
But again this wont flash recovery permanently AFAIK, everytime we need to boot into recovery we have to flash it via fastboot

insaneparnoid said:
I guess the command should be
fastboot boot /path to recovery
But again this wont flash recovery permanently AFAIK, everytime we need to boot into recovery we have to flash it via fastboot
Click to expand...
Click to collapse
He updated it with fastboot flash, indicating that this is to be installed, however it doesn't appear to work at all at this point.

For me is working , latest OOS beta. Just had to disable vbmeta in order to boot.

we need a flashble zip for this.

is OTG working with OrangeFox ?

otakutw said:
we need a flashble zip for this.
Click to expand...
Click to collapse
Not exactly, try - fastboot flash recovery *drag the image into the cmd then press enter*

Can this recovery be decreased in size so that it can be flashed to the ramdisk?
EDIT: It seems twrp is even bigger than this. Twrp img is 30.7mb while this is 29.4mb. Twrp does flash to the ramdisk. If this could be permanently flashed, it would be perfect. If the size needs to be decreased, certain graphics could be moved to the internal storage to save space on the ramdisk.

Hahaha wow what are you doing here it's like you didn't even test this at all. I'm tried to flash the installer in twrp and it tells me that this recovery is only for guacamole not OnePlus 7 pro. So it does not support custom roms clearly cause I'm on bliss

shadowikr said:
Not exactly, try - fastboot flash recovery *drag the image into the cmd then press enter*
Click to expand...
Click to collapse
There is no recovery partition on modern Android devices. The boot.img ramdisk contains the recovery