Database Users

Going back to Sense from [RUU] Google Edition Conversion.Graffixync UPDATE 12th May

EDIT - UPDATED INSTRUCTIONS 12th May 2014
Due to the partition sizes being different in the GPE RUU it is not simply a case of flashing a sense rom in recovery. You will experience problems if you do this. This might involve getting the storage encrption message, bootloops, freezing etc etc.
This thread is specifically for users who have problems getting back to sense. Solution is below. If you have alternative solutions that have worked without issues please post.
I have tried to make them as simple as possible. This guide assumes you are S-Off otherwise how did you get here. (
This does not apply if you have installed a GPE ROM. You can flash as normal through recovery. (using instructions of new rom)
Thanks to @exad for his continuing support/assistance throughout the thread, as well as @graffixnyc for the GPE RUU and both he and @navalynt for finding the initial fixes.
It will be much easier if you have your new Rom on your external sdcard prior to starting this. It will also stop a number of problems if you have SuperCID (11111111) If you don't know how to - FASTBOOT Commands
1. Enter the command "fastboot oem readcid". Make and KEEP a note of your original CID.
2. Enter the command "fastboot oem writecid 11111111"
3. Enter the command "fastboot read cid" [it should confirm your CID is 11111111]
4. Press the volume down button twice on your phone and navigate to reboot bootloader, then hit power button to reboot the bootloader.
5. Bootloader will also say "CID-11111111" now to confirm (Thanks to @xl VipeR lx ) Also to @umjammerlammy for the GENTLE reminders to include this
Make sure the firmware file and twrp recovery are in your Android directory on your PC - Mine is
C:\Users\Grentuu\AppData\Local\Android\android-sdk\platform-tools\
During this process you may find that when you reboot the phone starts to boot into android. Mine did but simply had the GPE animated logo but never entered GPE. All you do is press Vol up and power for about 10 seconds to reset. As soon as it resets press vol down and power to get back to bootloader.
Flash 1.54.401.5 firmware from Here
Fastboot Method
Boot device into FASTBOOT mode either by adb reboot bootloader or Vol down & Power (device should show FASTBOOT USB)
Make sure the firmware file to be flashed is in your android folder
Open a command prompt from the folder where fastboot resides. (Hold shift key/right click in the dir to get menu - left click on Open Command Prompt here.)
Run the following commands:
fastboot oem rebootRUU (this will reboot the device into RUU mode in preparation for zip flashing)
fastboot flash zip 1.54.401.5-W_Splash.zip (the name of the zip should EXACTLY match the name of the file you're flashing)
It will fail the first time. Run the same command AGAIN until you see it has flashed successfully.
I repeat - Run the same command TWICE until you see it has flashed successfully.
Once complete, type fastboot reboot-bootloader The hyphen is required.
Some users have stated this firmware (1.54.401.5) did not work for them as they weren't GSM and reboots just threw them back to recovery. If this happens try a stock (your original e.g. T-mobile) firmware then follow the rest of the process.
Boot into stock recovery
Factory reset
Reboot into bootloader
Flash TWRP - command = fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img (The must match exactly the name of the recovery you are flashing and remember the recovery file must be in your android folder)
Boot into TWRP
Go into Wipe menu
do a full factory reset wipe
Reboot back into recovery
Install rom
Profit
These have worked for me everytime (Change count =19)

Thanks for this. I'm about to give it a shot now.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
---------- Post added at 05:08 PM ---------- Previous post was at 04:40 PM ----------
For some reason the firmware wont flash in twrp. Should I sideload the firmware?
Sent from my GT-P5210 using XDA Premium 4 mobile app

To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip
Fastboot reboot-bootloader

exad said:
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firnwarefilename.zip
Then again
Fastboot flash zip firnwarefilename.zip
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Thanks. Understood, I was just reviewing my steps for the conversion. I really just want to try out that new Sense rom and then I'll probably revert back. BRB...I'll let you know how it goes.

Bear in mind you must have S-off to flash a firmware that way.

exad said:
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Those are the instructions in post 1 the original thread.
The issue is with people wanting to go back to sense

This thread is about returning to sense. Flashing a firmware is always the same. It's the firmware itself that's different...

Here is where I am at..
I converted to GP easily and it worked well.. I wanted to convert back so I installed twrp first, then through twrp installed the 1.54.401.5 firmware.
Installing that firmware removed twrp and the rom. So I am without an OS at all, and have stock recovery.
Is there anyway I can flash a custom recovery or a rom via the stock firmware/recovery?
My computer will not recognize adb devices. But it used to obviously.
I have an SD card.
Any help and I will be sooo grateful. (maybe even donate)
Thanks!

You can't flash a firmware through recovery... You can flash a stock recovery after the steps listed above if you like. See the stock backup thread.
You can flash any recovery through fastboot... Adb only works with the rom booted or with custom recovery booted.

Thanks will try it out.

exad said:
You can't flash a firmware through recovery... You can flash a stock recovery after the steps listed above if you like. See the stock backup thread.
You can flash any recovery through fastboot... Adb only works with the rom booted or with custom recovery booted.
Click to expand...
Click to collapse
So what do I do in this situation with no rom installed only 1.54 firmware and stock recovery.

Flash twrp

exad said:
Flash twrp
Click to expand...
Click to collapse
I have no rom installed, so it wont show in adb devices.

PunchLick said:
I have no rom installed, so it wont show in adb devices.
Click to expand...
Click to collapse
You flash recovery via fastboot, no need for a rom.
Just make sure you have the proper fastboot drivers from htc.

Dmaxon said:
You flash recovery via fastboot, no need for a rom.
Just make sure you have the proper fastboot drivers from htc.
Click to expand...
Click to collapse
ADB devices shows no devices. If i had custom recovery this would be so much easier, but im using 1.54.401.5 firmware with stock recovery and no ROM.
Just dont know what to do to get a working device again. All i can do is boot into stock recovery, hboot and fastboot.. but computer shows no device.

PunchLick said:
ADB devices shows no devices. If i had custom recovery this would be so much easier, but im using 1.54.401.5 firmware with stock recovery and no ROM.
Just dont know what to do to get a working device again. All i can do is boot into stock recovery, hboot and fastboot.. but computer shows no device.
Click to expand...
Click to collapse
I would recommend the All-In-One Toolkit. This will allow you to fastboot the recovery, even though the pc doesn't recognize it. This has worked for me in the past.
Meanwhile, I get the following error message when attempting to flash the 1.54...
Any suggestions guys???
Problem solved. I had not supercid. After I did that, I was able to successfully flash 1.54...

Why post steps if your not willing to help?
The steps in the OP can still cause issues for some people.
Sent from my HTC One_M8 using Tapatalk

Ideas4ya said:
I would recommend the All-In-One Toolkit. This will allow you to fastboot the recovery, even though the pc doesn't recognize it. This has worked for me in the past.
Meanwhile, I get the following error message when attempting to flash the 1.54...
Any suggestions guys???
Problem solved. I had not supercid. After I did that, I was able to successfully flash 1.54...
Click to expand...
Click to collapse
Can you elaborate a little on which options etc, because that sounds fantastic and would help me so much!

PunchLick said:
Can you elaborate a little on which options etc, because that sounds fantastic and would help me so much!
Click to expand...
Click to collapse
When you open the all in one...the 3rd option on the top right is what you need. Follow the step, even if fastboot says device is not connected, this will still send the recovery to your device as long as you're in the bootloader.

I will never understand why people play with there phones and have no understanding of adb and fastboot commands with the bootloader. if people would learn that first there wouldn't be so many threads when they get stuck. tool kits are bad it makes people lazy. but I appreciate the devs who make them

Help: Brick oneplus2 that is not recognised by my pc

I cleared the internal storage of my oneplus 2 by mistake and it became brick. I can acceas to the fastboot and twrp. But my pc is not recognising it when i tried adb sideload and fastboot. Pc has winfows 10. I have heard some settings we should do there. So pleasw someone help. How to unbrick it easily. I am a noob here so.. Pls

alwinv001 said:
I cleared the internal storage of my oneplus 2 by mistake and it became brick. I can acceas to the fastboot and twrp. But my pc is not recognising it when i tried adb sideload and fastboot. Pc has winfows 10. I have heard some settings we should do there. So pleasw someone help. How to unbrick it easily. I am a noob here so.. Pls
Click to expand...
Click to collapse
Someone please help. I tried the almost everything available and main problem is pc isnt recognising the phone even as a qualcomm driver.. Adb sideload failed due to the same thing. I can access to the twrp but nothing is there in the internal storage to installand qithout my pc recognising it.. There is no way out

I'm sorry to hear that buddy.. i wish i am expert enough to help you out, but i hope someone comes and helps you
Sent from my ONE A2003 using XDA-Developers mobile app

I haven't used the Qualcomm fastboot recovery flasher. But I guess you just have to boot up the bootloader/fastboot mode, change the drivers under device manager for the Qualcomm ones (might need you to disable driver signing requirement if the driver is unsigned and your running Windows 8 or newer). And from there just run the Qualcomm flasher and watch it complete. However I'm guessing you've been playing around with the experimental beta ROMs and thereby changing bootloader, so you should be able to restore bootloader back to the 2.2.1 one by first running fastboot flash recovery recovery.img with a twrp recovery.img which is compatible with your bootloader (the chinese 3.0 i suppose) and then from there flash the revert to Lollipop zip using TWRP and then fastboot flash recovery the TWRP for OxygenOS 2.2.x/CM13 bootloader.
Skickat från min ONE A2003 via Tapatalk

Hi Alwin,
If TWRP is working on your oneplus 2, you can simply flash the stock firmware by downloading the stock firmware and transferring it to a USB, then using a USB otg connector to flash the zip while in TWRP.
You can find link to stock firmware in benkxda's post.
Hope it helps.

NamanPuri said:
Hi Alwin,
If TWRP is working on your oneplus 2, you can simply flash the stock firmware by downloading the stock firmware and transferring it to a USB, then using a USB otg connector to flash the zip while in TWRP.
You can find link to stock firmware in benkxda's post.
Hope it helps.
Click to expand...
Click to collapse
Thanks..

A little help please...

I have the US version of the ZTE Axon 7 running the B29 build.
I recently unlocked the bootloader successfully, When I flashed the TWRP recovery via fastboot soon after, it worked perfectly. Phone booted properly and worked normally. When I tried to install the TWRP app in the OS, I was told to download the latest TWRP version from the website and flash it (even though I had the latest version already flashed from fastboot). I did that. Now I have no recovery menu at all. I have access to the bootloader menu, and I can boot into the phone. When I try to boot into recovery, all I get is a black screen. I tried to reflash the TWRP recovery img from fastboot like I did originally with no success this time. Fastboot recognizes the phone when I type devices, but when I type the fastboot command to flash recovery twrp.img, it says it can't load the file. I then downloaded the ZTE stock recovery img and tried to flash that with the same result. I assume the recovery partition is locked somehow now? What can I do to recover the recovery? Am I stupidly forgetting something trivial.

hello, this happened to me once on a Nexus 7, I did a clear cache/wipe and restore I think, I got it to work.
Not sure if this will solve your issue but you can give it a shot...
good luck

I would never flash a recovery from an app unless there was no other option. Use tennear/tenfar tool to flash twrp.

lafester said:
I would never flash a recovery from an app unless there was no other option. Use tennear/tenfar tool to flash twrp.
Click to expand...
Click to collapse
yeah. live and learn. too late to help at this point. I'll try the tool you suggested

Bucci83 said:
hello, this happened to me once on a Nexus 7, I did a clear cache/wipe and restore I think, I got it to work.
Not sure if this will solve your issue but you can give it a shot...
good luck
Click to expand...
Click to collapse
Thanks for your suggestion. I cant wipe/flash/ recover/or even reset to factory because I have no recovery menu at all. Unless there's a way to do that outside of the recovery boot menu.
At least it's not bricked.

[email protected] said:
Thanks for your suggestion. I cant wipe/flash/ recover/or even reset to factory because I have no recovery menu at all. Unless there's a way to do that outside of the recovery boot menu.
At least it's not bricked.
Click to expand...
Click to collapse
I think he means go to fadtboot and do fastboot clear cache or something like that, Google fastboot cache clear command

needing help with huawei Y3 II LUA-L03 (softbricked/bootloop)

hi everyone.
a friend of mine was trying to root his huawei but now it cant boot anymore.
he followed a wrong guide for the Y5 II and flashed a custom recovery (bootloader unlocked) TWRP.
now the phone its on bootloop with the stock OS. i think that its due to the wrong recovery flashed on the partition.
so im requesting help for this phone.
is there a solution for this?
can anyone bring me the stock firmware for this model?
i need it as update.app to extract the stock recovery, not as ota update (dload/update.zip) cuz i need to flash it using fastboot. the phone just can use fastboot cuz recovery partition is corrupted and normal boot doesnt work (bootloop).
plz someone can help me?
i already googled long for a solution but i can figure out how to make it work.
the phone comes with android 5.1 lollipop and is from chile.
pd: the phone can only enter fastboot by pressing vol+ and power. if i try to turn it on normally it bootloops. when on fastboot menu, if i select recovery, it bootloops. if i select fastboot, it works using adb from pc (i mean, i can download data to it, it doesnt boot via fastboot option).
if i just had the original recovery.img maybe i can flash it and make it boot normally again.

rivenroth740 said:
hi everyone.
a friend of mine was trying to root his huawei but now it cant boot anymore.
he followed a wrong guide for the Y5 II and flashed a custom recovery (bootloader unlocked) TWRP.
now the phone its on bootloop with the stock OS. i think that its due to the wrong recovery flashed on the partition.
so im requesting help for this phone.
is there a solution for this?
can anyone bring me the stock firmware for this model?
i need it as update.app to extract the stock recovery, not as ota update (dload/update.zip) cuz i need to flash it using fastboot. the phone just can use fastboot cuz recovery partition is corrupted and normal boot doesnt work (bootloop).
plz someone can help me?
i already googled long for a solution but i can figure out how to make it work.
the phone comes with android 5.1 lollipop and is from chile.
pd: the phone can only enter fastboot by pressing vol+ and power. if i try to turn it on normally it bootloops. when on fastboot menu, if i select recovery, it bootloops. if i select fastboot, it works using adb from pc (i mean, i can download data to it, it doesnt boot via fastboot option).
if i just had the original recovery.img maybe i can flash it and make it boot normally again.
Click to expand...
Click to collapse
I don't know much about Huawei, but if firmware is available you should be able to flash back to stock. Personally, I would try to find the right TWRP and flash it...then it will boot and you can root of you still desire.
I'm not sure if this is the right one, but if bootloader is unlocked it won't hurt to try. https://twrp.me/devices/huaweiy300.html
Sent from my XT1609 using Tapatalk

RealWelder said:
I don't know much about Huawei, but if firmware is available you should be able to flash back to stock. Personally, I would try to find the right TWRP and flash it...then it will boot and you can root of you still desire.
I'm not sure if this is the right one, but if bootloader is unlocked it won't hurt to try. https://twrp.me/devices/huaweiy300.html
Click to expand...
Click to collapse
I'll try.. thanks

RealWelder said:
I don't know much about Huawei, but if firmware is available you should be able to flash back to stock. Personally, I would try to find the right TWRP and flash it...then it will boot and you can root of you still desire.
I'm not sure if this is the right one, but if bootloader is unlocked it won't hurt to try. https://twrp.me/devices/huaweiy300.html
Click to expand...
Click to collapse
Well.. it's no use.. he had to buy a new phone.

Phone bricked?

Hello. I flashed TWRP and then LineageOS onto my Mi 9T. I didn't like it too much so I started downloading the global rom. In preparations to reflash the stock rom, I wiped the phone from TWRP and then turned the phone off until it was completed downloading. I was planning to install the ROM through OTG, but when I tried to go into recovery, nothing happens and I go back to boot screen. I tried reflashing TWRP with adb, but it seems I forgot to turn USB debugging back on when I was transferring files. What can I do now? Is my phone bricked?

No it's not bricked.
Just flash fastboot rom and then
Flash twrp again ,free to do any job

Masih_zh said:
No it's not bricked.
Just flash fastboot rom and then
Flash twrp again ,free to do any job
Click to expand...
Click to collapse
Will it still work even though USB debugging is off? Sorry I am new to this.

tagkd said:
Hello. I flashed TWRP and then LineageOS onto my Mi 9T. I didn't like it too much so I started downloading the global rom. In preparations to reflash the stock rom, I wiped the phone from TWRP and then turned the phone off until it was completed downloading. I was planning to install the ROM through OTG, but when I tried to go into recovery, nothing happens and I go back to boot screen. I tried reflashing TWRP with adb, but it seems I forgot to turn USB debugging back on when I was transferring files. What can I do now? Is my phone bricked?
Click to expand...
Click to collapse
Flash stock dtbo.img and recovery.img from fastboot

tagkd said:
Will it still work even though USB debugging is off? Sorry I am new to this.
Click to expand...
Click to collapse
The "USB debugging" you're talking about assumes there's a running OS on your system. It's not applicable here. Boot into fastboot and see if the phone is recognized. If yes, you're good. Flash twrp via fastboot then boot into recovery and go from there with removing old files and flashing new rom

Thanks for the help everyone. I found a v 10.3.6 fastboot rom and was able to get phone working again.