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

Search This thread

grentuu

Senior Member
Jan 9, 2011
632
262
Just outside of Manchester UK
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)
 
Last edited:

Ideas4ya

Senior Member
Aug 10, 2012
653
171
Oppo Find N
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
 
  • Like
Reactions: grentuu

Ideas4ya

Senior Member
Aug 10, 2012
653
171
Oppo Find N
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

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.
 

exad

Senior Member
Jan 26, 2010
3,459
1,517
Montreal
This thread is about returning to sense. Flashing a firmware is always the same. It's the firmware itself that's different...
 

PunchLick

Senior Member
Jul 1, 2013
92
21
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!
 

exad

Senior Member
Jan 26, 2010
3,459
1,517
Montreal
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.
 
  • Like
Reactions: grentuu

PunchLick

Senior Member
Jul 1, 2013
92
21
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.

So what do I do in this situation with no rom installed only 1.54 firmware and stock recovery.
 

PunchLick

Senior Member
Jul 1, 2013
92
21
You flash recovery via fastboot, no need for a rom.
Just make sure you have the proper fastboot drivers from htc.

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.
 

Ideas4ya

Senior Member
Aug 10, 2012
653
171
Oppo Find N
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.


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...
 
Last edited:
  • Like
Reactions: PunchLick

CB620

Senior Member
Jan 6, 2009
15,090
2,376
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
 

PunchLick

Senior Member
Jul 1, 2013
92
21
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...

Can you elaborate a little on which options etc, because that sounds fantastic and would help me so much!
 

daddioj

Senior Member
Jul 23, 2011
1,456
210
Poconos
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
 

Top Liked Posts

  • There are no posts matching your filters.
  • 113
    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)
    12
    Ack toolkits!!!
    Toolkits are bad. Adb and fastboot are not difficult. People just get intimidated. I think it's the command line?
    No offence to people who develop the toolkits, I know they're trying to help but all they're really doing is breeding ignorance.

    Quick understanding of fastboot and adb:

    Fastboot can only be used in fastboot mode. It has a somewhat limited set of commands allowing you to flash/wipe partitions, boot a custom recovery without flashing or getting information such as cid, mid, etc.
    Most used commands are:

    Checking device connected: Fastboot devices
    Flashing recovery stock or custom: Fastboot flash recovery recoveryfilename.img
    Booting to downloaded recovery without flashing: fastboot boot recoveryfilename.img
    Flashing radio: Fastboot flash radio radiofilename.img
    Going into RUU mode (Used for flashing firmware): Fastboot oem rebootRUU
    Flashing zip files that contain multiple images such as a firmware package while in RUU mode: Fastboot flash zip filename.zip
    Reading your cid: Fastboot oem readcid
    Readinf your cid: Fastboot getvar cid
    Reading all phone info: Fastboot getvar all
    Writing cid: Fastboot oem writecid whatevercid (Must be 8 digits/letters long)

    ADB Can only be used while in custom recovery or while booted into a rom with usb debugging enabled. It has MANY MANY More commands because it's more like actually using your phone in command line from your PC.
    Common commands used but not at all limited to include:

    Checking ADB devices connected: adb devices
    Rebooting: adb reboot
    Rebooting to bootloader: adb reboot bootloader
    Rebooting to recovery: adb reboot recovery
    Pushing files to phone: adb push filename path IE: adb push rom.zip /sdcard/ Will move rom.zip from your computer to your phone's SD card.
    Pulling files from your phone: adb pull /path/filename IE: adb pull /sdcard/rom.zip Will pull rom.zip from your SDcard and put it on your PC in whatever folder your command prompt is currently residing.
    Initiating a shell with your phone allowing you to access your phone remotely as if you were using terminal app on your phone: adb shell

    Hopefully this helps a few of you feel more comfortable with fastboot and ADB. They really aren't difficult to use and often a quick google search can fill you in if you're a little shady on details.
    6
    lol.. Not even worth responding.

    Anyway.. I got my phone back to working fine thanks to the help from a few members. So thanks!

    Out of curiosity.. Lets say you are converted to GPE, but want to flash an AOSP based rom or something. You wouldn't need to take these steps in order to convert back right?

    I will respond though.. but more to just convey in a nicer way what he was trying to say. I have only been using Android since Jan 2011.. Before then I was a die hard blackberry user. I knew NOTHING about Android other than it was made by Google. haha

    I found XDA and I got hooked.. I lurked for a while and I would see other users getting rude with others in ways like "search or get out" or just saying go read stuff before you do it. Now I know guys that have been using Android a lot longer than me, yet I know WAY more... How do I know way more? Because I spent the time reading tutorials.. using google.. and just poking around myself.. I took the initiative to learn on my own... Then less than a year after getting into Android I released my first "dev" project. CWM for the Dell Streak 7. 72 hours after beginning I got it.. I didn't get it by asking people.. I got it by reading, hell I didn't want to ask anyone and come off as a dumb noob.. lol

    So then I started releasing roms and things and THEN I started to see why people would get rude and understand it as I found I was getting snippy.. You have to understand.. We devs take the time to develop something, write detailed instructions etc.. and you have users that don't even bother reading it or reading the thread for that matter or even searching the thread.. This is kinda disrespectful to the dev. I mean Why do 100 people have to ask the same question that has been answered 100 times in previous pages and the person is just too lazy to look..

    Or when you tell someone "Yeah there is a site somewhere that has the file" and they person asks for a link.. hello?? Am I your personal google? The time it took to ask for a link and wait for a response you could find it yourself. It's pure laziness. I search before I post ANYTHING. I read before I do ANYTHING. So the more experienced guys who have put in the time and took the initiative to learn and not asking to be spoon fed everything get upset because you have guys that don't want to put in the time to learn yet want to benefit from YOUR hard work.. How is that fair? If you ask me.. it's take take take and never give..

    So yes, I can understand why people would get upset when a user is not taking the initiative to learn on their own and is expecting everyone to spoon feed them. Most of us took the time to READ and LEARN.. what makes you or anyone else so special where you don't feel you need to read stuff and people should just help you without you even trying to help yourself...

    I always die when I watch this video! It's so true!
    https://www.youtube.com/watch?v=wwleOote5M0

    I will say flaming anyone is wrong.. BUT at the same time.. users need to learn how to search better and not ask the same stuff over and over again..

    Look at the GPE RUU thread.. search how many times someone has asked about stock recovery and the bug droid on his back.. See how many times it was answered.. See how many more times it was asked.. That ALL could have been avoided if the person wasn't too lazy to search and READ
    6
    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

    The steps in the op were taken right from my thread. The steps I actually modified the other day when I was working on trying to get sense ruu going. I converted to gpe edition and then would test the sense ruu(which I'm still having issues with)

    My point is Saturday I went back and forth from converting to gpe back to sense following and rewriting some of the steps. Every single time I followed the steps in the op to the T, I got back to sense. There was once that day I did a step out of order and it wouldn't boot. I have tested multiple times and if they are followed to a T without skipping anything, without mixing up a step.. It will return you to sense. I think I went though the steps at least 5 times Saturday to insure they were correct..


    Sorry to say but 99% of the time it's user error even if the user thinks they know what they are doing. For example.. The rom version I have out.. Some Tmo users weren't getting data.. I swore up and down it had to be an apn issue.. Guys were like "I have entered the apn right.. I'm not some noob, I've been flashing stuff since the g1" and got insulted. They swore up and down they were entering the apn correctly.. What was the cause of them not getting data? Not selecting the ipv4/ipv6 option in the apn settings instead leaving it as ipv4. I had more than a few users swearing they entered it correctly and blamed the rom for not being compatible.. I even had one guy message me saying he has used Linux for 20 Years and knows his stuff.. Point is.. They swore it was the rom and not them.. And it wound up being something they did incorrectly :-$

    I guarantee.. If you follow the steps to the T... You will get back to sense after converting.

    Sent from my HTC One_M8 using Tapatalk
    5
    Moderator information:

    This post has been moved to this thread instead of having a duplicate thread for this topic. @grentuu, if you feel this information is useful please add it to your OP.

    Cheers,

    Heisenberg
    XDA Moderator


    first of all thank the following authors

    ckpv5, Mr Hofs, mikemol


    We have gathered information for 3 long days of questions and tests

    first of all, your computer must be

    Loader unlock 1_boot
    2_twrp-2.8.7.0-m8
    3_ root
    4_ mid change
    Cid Super 4_ 11111111



    steps

    1 back to mid euro

    adb shell
    their
    Echo -ne '\ x30 \ x00 \ x50 \ x00 \ x36 \ x00 \ x42 \ x00 \ x31 \ x00 \ x30 \ x00 \ x30 \ x00 \ x30 \ x00 \ x30' | dd of = / dev / block / mmcblk0p5 bs = 1 seek = 16384

    MID 0P6B10000

    2_ I realize the steps to change the CID to SuperCID and I get the following message
    *
    fastboot oem writecid 11111111

    Oem 3_fastboot rebootRUU
    Fastboot flash zip 4.16.401.10-Firmware-noredtext.zip 4_ (message error) retrying
    5_fastboot flash zip 4.16.401.10-Firmware-noredtext.zip

    Important down

    0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417809_signed.zip and rename 0P6BIMG.zip (not 0P6BIMG.zip.zip)
    *micro sd copy and insert it into your computer in fastboot mode

    key press volume up and ready to wait

    My suffering is over.

    Wippe data




    Downloads

    firnware https://www.androidfilehost.com/?fid=24052804347850101 4.16.401.10

    flash https://www.androidfilehost.com/?fid=95916177934518148