Develop Bugs

Frustrated!

Alright I have a problem. I bought a used G2 which had already been rooted. I installed CM7 on it and it worked fine except for wi-fi (little did I know the awful path this was about to send me down). I thought this might be because I was using Recovery 2.5, so I switched to recovery 3.0 and flashed CM7 again, same problem. I found out you have to reboot the phone after your first boot to get wifi working a lot of time so that was my fault, I should have researched that more thoroughly from the beginning and I would have avoided this whole ordeal. Anyway after this I wanted to downgrade to Recovery 2.5 again because there are a lot of zips that can't be installed through recovery with 3.0. So I tried to do that and couldn't, I looked around and found that was probably because I didn't have eng s-off which I didn't, I had s-off but not engineering.
So I tried getting that working, this took forever because I couldn't figure out if I was supposed to use the OTA or preOTA.ko file. I discovered my phone was post OTA so I tried using that file and didn't receive the correct error message (Function not implemented), but instead some other error. After researching this and trying to find out why that could be or what exactly the OTA part of it does without a definitive answer I decided to go ahead and run the terminal command for eng s-off anyway feeling relatively safe. This succeeded and I was happy that I'd finally figured everything out! Wrong. I had eng s-off. Also I was able to downgrade the recovery again through terminal, however after doing this and trying to boot into recovery it would just stay at the white HTC symbol. Fine, maybe I can't downgrade to 2.5 after installing CM7. So I upgraded Recovery back to 3.0 and used it to install CM6.1.
After doing this I went into ROM manager and dropped myself back down to recovery 2.5.1.3. Now whenever I try to reboot into recovery I immediately get taken to fastboot. I've tried searching for any others having problems like this without success and I'm extremely frustrated. I tried using different versions of recovery 2.0, I tried updating to recovery 3.0 all without any success, still just boots into fastboot if I try to get into recovery. Please tell me someone knows what my issue could be and how I can fix it, meanwhile I'll continue trying to work it out and let you know if I do. Thankyou.
EDIT: It appears for whatever reason rom manager may actually not be flashing a recovery, if someone could post the 2.5.1.3 recovery.img that would be wonderful

I dont know if you have Andriod SDK set up and if you know how to use Fastboot, but since you have an ENG. Hboot you can use fastboot to flash a new recovery image onto your phone, you can download the CWM Recovery 3.0.0.5 .Img from HERE. Place the new recovery image into the same folder your Fastboot.exe file is and run this command:
Code:
fastboot flash recovery <name of recovery.img>
There is also a way to flash a new recovery using flash_image method from you phone, so you can download a new recovery from the link above and use this method to flash it.
2.5.1.3 recovery is obsolete, the new 3.0.0.5 recovery supports all roms 2.2. and 2.3.

joemm said:
I dont know if you have Andriod SDK set up and if you know how to use Fastboot, but since you have an ENG. Hboot you can use fastboot to flash a new recovery image onto your phone, you can download the CWM Recovery 3.0.0.5 .Img from HERE. Place the new recovery image into the same folder your Fastboot.exe file is and run this command:
Code:
fastboot flash recovery <name of recovery.img>
There is also a way to flash a new recovery using flash_image method from you phone, so you can download a new recovery from the link above and use this method to flash it.
2.5.1.3 recovery is obsolete, the new 3.0.0.5 recovery supports all roms 2.2. and 2.3.
Click to expand...
Click to collapse
Thanks, yes I know how to use fastboot, and I did install the 3.0.0.5 recovery earlier, the problem with recovery 3 is that a lot of older zips don't support it and I'd really like that functionality. Any idea on where I might be able to find the older recovery? Thanks in advance

I have a copy of the 2.5.1.3 recovery, I put it in my dropbox for you:
http://dl.dropbox.com/u/17831112/recovery.img
Heres a MD5 checksum for it:
0C9C47FC09460DB17EC4BDA5F4F97A12

Update for anyone else frustrated by this, I found a tool that will attempt to update your zip to the new edify format. I've tried it on a couple zips so far and it worked both times, they just added support for the G2. Here's the link
http://forum.xda-developers.com/showthread.php?t=903598

Can't Boot Into Recovery Only Fastboot

So I recently updated my op3 to 3.5.2 Community Build of oxygen OS. It was working well with a few changes from the official builds but a little time passed and the 3.5.3 Community Build was released. Of course I wanted to update so I downloaded it and tried to update but when it booted into the recovery it froze on the logo. So I downloaded the update on the computer and flashed twrp to the recovery and booted into the recovery and it froze again. Currently i have no Recovery and no access to adb.
*When trying to flash a recovery it says it was done successfully but freezes when trying to boot into it.
Normal OS booting is unaffected.
When executing the command "fastboot boot recovery.img", to boot into the recovery without flashing it i get "(remote dtb not found)"
When trying to manually update the OS through "fastboot zip Update.zip", I get "(remote: data too large)".
I also tried to do "fastboot erase recovery" before issuing the flash command.
*In trying to fix this i flashed the boot image of 3.5.3 onto the boot partition but nothing happened and now the phone reads as 3.5.3 on 3.5.2 firmware :crying:
I tried to use SkipSoft ToolKit,custom and official twrp, and recoveries such as CWM.
This would probably be better placed into the, ONEPLUS 3 ROMS, KERNELS, RECOVERIES, & OTHER DEVELOPMENT, section but I can not post there yet. If anyone can help me or find a mod that knows about this problem it would be much appreciated.

Found a Solution
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56

Unable to Root AT ALL

So I wanted to install a CM ver on my mother's Redmi 1s and first thing I have to do is root the device right?
<image>
I have tried downloading several SuperSU.zip from multiple sources, including here at xda forums and the miui forums, to no avail.
Every single attempt has been a failure using the Stock Recovery that comes with the phone.
Fine then, I'll just use a custom recovery. I then connected the phone to my laptop via USB and used the sdk I downloaded.
After typing this line >>adb reboot bootloader, the phone booted into a screen with the fastboot bunny, all normal yes?
Then I typed >>fastboot oem unlock, but the image below doesn't show up on the phone
<image>
Instead, the command prompt just shows a few lines of the process completing
<image>
I continued to enter>>fastboot flash recovery customrecovery.img into cmd with the custom recovery image IN the platform-tools folder in sdk. Cmd again shows a few lines saying that the process completed.
<image>
However the phone still stays on the screen with the fastboot bunny, even after rebooting and then entering recovery mode, it is still the stock one. I have searched everywhere on how to root this phone but they just showed to install the SuperSU.zip using the stock recovery or the sdk method. If anyone could just help me solve this issue that would be great. If you need more information that I can provide regarding the issue feel free to ask. Thanks in advance !
P.s. Due to xda preventing me from posting outside links since I have not met the threshold, anyone who needs the pictures can message me privately.
Edit: Ah yes, I should also mention that I have tried using the stock Updater app to install the SuperSU.zip as well but that doesn't work. Also, I have tried using King Root and Kingo Root as the easy way, same thing.

Find the TWRP image for our device. I don't prefer the fastboot method; flashing TWRP and then the SuperSU zip is a whole lot more convenient as you don't need a computer.

NightRaven49 said:
Find the TWRP image for our device. I don't prefer the fastboot method; flashing TWRP and then the SuperSU zip is a whole lot more convenient as you don't need a computer.
Click to expand...
Click to collapse
But doesn't flashing TWRP without PC (with an app) requires the phone to be rooted to begin with? Or is there any workaround method?

Then use Philz recovery. There's a sticky in the general section that provides a link to such a guide using Philz. After rooting you can flash TWRP.

NightRaven49 said:
Then use Philz recovery. There's a sticky in the general section that provides a link to such a guide using Philz. After rooting you can flash TWRP.
Click to expand...
Click to collapse
Nope, still doesn't work. Tried using the stock recovery to install update.zip and also flashing the .img via sdk, both doesn't work. I'm again out of options.

before do this backup your device
you can install custom recovery with official fastboot rom.
download any official fastboot rom for your device (stable or beta does not matter)
download twrp .img file for your device
rename your recovery image file to "recovery.img"
extract the fastboot rom
go to "images" folder in extracted fastboot rom
overwrite recovery.img file with your downloaded file
flash the fastboot rom with mi flash.
wait for the installation to complete
setup your device
turn off your device and go to custom twrp recovery.
after that you can install supersu or any custom rom via twrp.

I hope you have checked this post
http://en.miui.com/thread-104048-1-1.html

For me..I started with a zip file containing the custom recovery (TWRP) it was named as Update.zip I got it from a tutorial I googled (noob, I know)...and I flashed it using stock recovery (Redmi 1s don't have locked bootloaders, I guess) and then I had Custom recovery installed..I made a backup of MIUI (it was unrooted, stock) and then flashed the CM 12.1( it was the latest then). Then there was no looking back.

Problems returning to Stock

Hey Guys,
Hope that someone can help me or point me in the right direction.
Currently I am running RR-0S and have TWRP 3.1.0.0 installed.
I am trying to go back to stock but have having problems, If I try to flash Oxygen through TWRP I get an error 7 code.
If I change TWRP version to flash I end up with a black screen when booting recovery.
When I try stock recovery and ABD sideload, I cannot sideload as there seems to be an issue with Minimal adb and Fastboot and it keeps giving me error messages.
I don't know where I'm going wrong

sudd1976 said:
Hey Guys,
Hope that someone can help me or point me in the right direction.
Currently I am running RR-0S and have TWRP 3.1.0.0 installed.
I am trying to go back to stock but have having problems, If I try to flash Oxygen through TWRP I get an error 7 code.
If I change TWRP version to flash I end up with a black screen when booting recovery.
When I try stock recovery and ABD sideload, I cannot sideload as there seems to be an issue with Minimal adb and Fastboot and it keeps giving me error messages.
I don't know where I'm going wrong
Click to expand...
Click to collapse
You have a PC close? Wipe all partitions then adb sideload it. If you have issues with sideloading you can use adb push and then manually flash the rom.

https://forums.oneplus.net/threads/...-3-3t-and-go-back-completely-to-stock.456232/
Voila

Thanks for the suggestions guys, managed to get it all back to stock.
Was flashing a different bootloader and modem, compared to the Rom that I was trying to install.
Realised my mistake after 2 days of trying...doh !!

Error Can't load TWRP.IMG

First of all i am sorry to post the same question when it is already in the forum, i did alot of digging and i couldn't find answer in thread. So here is what happened
i am using Ubuntu
i have ADB and Fastboot installed, i have been using them for long time now without any problem, i decided to update my OP3, And OP3T 2 days back. it wasn't working at first but i finally managed to install update, now i am stuck with this error " Can't load twrp.img" i am trying to flash twrp on both devices but i am getting same error

Bootloader unlocked or not?
Check it.
Fastboot command
fastboot OEM device-info
If unlocked, twrp.img should be in fastboot folder.

What recovery ?
Must be the latest!
I recomand blu spark twrp v.8.54 by eng stk. Flash with ADB in Bootloader/Fastboot mode.

Yup bootloader unlocked, i have been using magisk on previous version which was 4.5.1
but after update to 5.0 nothing seems to work, i managed to flash 5.0
when i install twrp it works fine but after first boot it reverts back to stock recovery.

Thanks for your comment, i tried blu spark too but it did not work either.

There's a modified twrp for stock oreo. Blu spark's recovery won't work.(didn't work for me personally)
I tried recovery from this thread and it worked like charm.

Btw It is Solved now. Thanks for your time and Info.

What did you do?