Database Info

[S4] Flashing from CM10 to TrickDroid 7.1 does not work

Hey Guys,
yesterday I wanted to revert my ROM from CM10 to TrickDroid 7.1. In TWRP 2.2.1 I wiped caches and did a factory reset and then flashed TD 7.1 following torxx's instructions (wipe, install ROM, flash boot.img with his boot flash script, let the ROM boot). After the reboot the phone hang. The startup sound came through but then no further action for about 7 Minutes.
Was that too little time waiting? Or is there any other issue interfering the boot process after reverting from Android 4.1.1 to 4.0.4 Sense?
If anyone can help is much appreciated. Even if I look stupid afterwords
Burkhard

herzbert said:
Hey Guys,
yesterday I wanted to revert my ROM from CM10 to TrickDroid 7.1. In TWRP 2.2.1 I wiped caches and did a factory reset and then flashed TD 7.1 following torxx's instructions (wipe, install ROM, flash boot.img with his boot flash script, let the ROM boot). After the reboot the phone hang. The startup sound came through but then no further action for about 7 Minutes.
Was that too little time waiting? Or is there any other issue interfering the boot process after reverting from Android 4.1.1 to 4.0.4 Sense?
If anyone can help is much appreciated. Even if I look stupid afterwords
Burkhard
Click to expand...
Click to collapse
Perhaps your hboot does not allow flashing or boot.img? Have you tried the fastboot method of flashing boot.img? How about reverting to a nandroid of a sense based ROM, then flashing TD?

el_smurfo said:
Perhaps your hboot does not allow flashing or boot.img? Have you tried the fastboot method of flashing boot.img? How about reverting to a nandroid of a sense based ROM, then flashing TD?
Click to expand...
Click to collapse
Prior to CM10 I was on latest stock ROM. Before that I had custom ROMs. HBoot on my phone after the OTA update is 1.14. Flashing the boot image of CM10 was no problem.
In order to use the phone I reinstalled CM10 and it works.
The boot images were flashed within fastboot. I do not know any other way to flash a boot image.
I dont have a nandroid backup.

Checked MD5?

torxx said:
Checked MD5?
Click to expand...
Click to collapse
They correspond.
If nothing else helps I will try to install the latest RUU and then flash a ROM. But I wanna circumvent the relock and unlock procedure.
Btw: Did anybody notice that the unlock code changes after an update of HBoot? Nobody mentioned that when the new base was released.

Same here... But fine now
herzbert said:
They correspond.
If nothing else helps I will try to install the latest RUU and then flash a ROM. But I wanna circumvent the relock and unlock procedure.
Btw: Did anybody notice that the unlock code changes after an update of HBoot? Nobody mentioned that when the new base was released.
Click to expand...
Click to collapse
Hey there,
I was having the same problems as you messioned. I flashed the boot.img through fastboot myself and some how it then worked Did not have an problems with flashing the boot.img before. But maybe its worth a try.

Of course you need to use fastboot!!

Did not try yet to flash the RUU. There was an update of CM10 yesterday. The heavy battery drain is gone with this update and there is no urgent need to go back to TrickDroid right now.

herzbert said:
Prior to CM10 I was on latest stock ROM. Before that I had custom ROMs. HBoot on my phone after the OTA update is 1.14. Flashing the boot image of CM10 was no problem.
In order to use the phone I reinstalled CM10 and it works.
The boot images were flashed within fastboot. I do not know any other way to flash a boot image.
I dont have a nandroid backup.
Click to expand...
Click to collapse
HBoot 1.14 is the problem. Anything above 1.09 needs special steps to flash unlike simply flashing with twrp as with 1.09 and below.
Sent from my HTC VLE_U using Xparent SkyBlue Tapatalk 2

LikeaG2root said:
HBoot 1.14 is the problem. Anything above 1.09 needs special steps to flash unlike simply flashing with twrp as with 1.09 and below.
Alright, so, what are these special steps? Can you tell? If its not flashing the within recovery and push the boot.img via fastboot to the phone I would be very interested. My previous HBoot version was 1.13. Flashing ROMs was never a big deal. Also not going to CM9 and back to sense based ROMs.
Click to expand...
Click to collapse

I am on hboot 1.14 and it worked via fastboot. Like you mentioned yourself you reinstalled CM10 and it booted, therefore your previous flash of the boot.img didn't work. So just flash the boot.img via bootloader and fastboot and you should be good...

HighRoIIer said:
I am on hboot 1.14 and it worked via fastboot. Like you mentioned yourself you reinstalled CM10 and it booted, therefore your previous flash of the boot.img didn't work. So just flash the boot.img via bootloader and fastboot and you should be good...
Click to expand...
Click to collapse
I did also flash the boot.img via fastboot. Why do you say that anyway? Is there another method to flash a boot.img?

you didn't mention wiping System as part of the full wipe--needs done

Partially solved
rugmankc said:
you didn't mention wiping System as part of the full wipe--needs done
Click to expand...
Click to collapse
Right, I did not mention it because system is wiped by TWRP during flashing the ROM. So there was no need to wipe it seperately. But maybe my mistake was not to wipe data and the new "asec" folder messed things up.
I'll never know because yesterday I did a complete wipe including the SDCard. Afterwards I was able to install TrickDroid flawlessly.
Thank you all for your efforts.

Viper XL and boot.img

Hey guys I just wanna to check and make sure I'm doing everything right before I flash cause I don't need anymore paperweights
1.I have successfully unlocked my bootloader and installed twrp recovery and rooted.
2. Now I want to back up my entire setup: rom, apps, setting, data, everything so that if I ever want to return to stock then I can. I have booted into twrp and ran backup and selected all options. Is that how you perform a nandroid backup in twrp or is there more to it?
3. I want to install team venom viper xl rom. Do I have to first flash boot.img first or is the kernel the same in stock and viper xl so that isn't necessary? Do I have to do I factory reset first or what?
I'm still new to this stuff so please bear with me. Thank for all your help!!

ImagioX1 said:
Hey guys I just wanna to check and make sure I'm doing everything right before I flash cause I don't need anymore paperweights
1.I have successfully unlocked my bootloader and installed twrp recovery and rooted.
2. Now I want to back up my entire setup: rom, apps, setting, data, everything so that if I ever want to return to stock then I can. I have booted into twrp and ran backup and selected all options. Is that how you perform a nandroid backup in twrp or is there more to it?
3. I want to install team venom viper xl rom. Do I have to first flash boot.img first or is the kernel the same in stock and viper xl so that isn't necessary? Do I have to do I factory reset first or what?
I'm still new to this stuff so please bear with me. Thank for all your help!!
Click to expand...
Click to collapse
Wipe flash Rom flash boot IMG sit back enjoy

ImagioX1 said:
Hey guys I just wanna to check and make sure I'm doing everything right before I flash cause I don't need anymore paperweights
1.I have successfully unlocked my bootloader and installed twrp recovery and rooted.
2. Now I want to back up my entire setup: rom, apps, setting, data, everything so that if I ever want to return to stock then I can. I have booted into twrp and ran backup and selected all options. Is that how you perform a nandroid backup in twrp or is there more to it?
3. I want to install team venom viper xl rom. Do I have to first flash boot.img first or is the kernel the same in stock and viper xl so that isn't necessary? Do I have to do I factory reset first or what?
I'm still new to this stuff so please bear with me. Thank for all your help!!
Click to expand...
Click to collapse
Different kernel. it is using the 2.41 RUU. So go ahead and flash the boot.img
Here's what you should do for any new ROM with a different kernel.
Wipe System
Factory Reset
Flash boot.img
Flash the ROM
flash gapps (if AOSP based)
reboot and have fun
When doing a nandroid backup, it is only necessary to backup
System
Data
Boot

Ok thanks for your response but I'm still a little confused. First did I back up my current rom properly so that I can return to it later on? Secondly does viper and boot img have to be flashed or can they be installed from sdcard via twrp? If they have to be flashed whats the fastboot command.?

ImagioX1 said:
Ok thanks for your response but I'm still a little confused. First did I back up my current rom properly so that I can return to it later on? Secondly does viper and boot img have to be flashed or can they be installed from sdcard via twrp? If they have to be flashed whats the fastboot command.?
Click to expand...
Click to collapse
You backed up fine, it just takes up a little more space.
You have to extract the boot.img from the ROM and put it in the same folder as fastboot.exe
open command prompt, and navigate to the folder fasboot.exe is in and do the following command
fasboot flash boot boot.img
If it gets stuck at waiting for device, reboot into your bootloader, boot into fastboot from there. and then try again.

ImagioX1 said:
Ok thanks for your response but I'm still a little confused. First did I back up my current rom properly so that I can return to it later on? Secondly does viper and boot img have to be flashed or can they be installed from sdcard via twrp? If they have to be flashed whats the fastboot command.?
Click to expand...
Click to collapse
Viper is the Rom u flash it from twrp it's. azip file that's fkashable so make it easy and flash viper there and than flash the boot IMG from fastboot the command is all over the forums I thinks it fastnoot flash boot.img

don't be confused. read.
you always have to flash boot.img in fastboot "fastboot flash boot boot.img" then flash the zip in twrp make sure to wipe, and don't download international roms. you still have to flash the boot.img from your backed up rom.
like a hundred threads asking the same stuff because no one wants to read

DvineLord said:
don't be confused. read.
you always have to flash boot.img in fastboot "fastboot flash boot boot.img" then flash the zip in twrp make sure to wipe, and don't download international roms. you still have to flash the boot.img from your backed up rom.
like a hundred threads asking the same stuff because no one wants to read
Click to expand...
Click to collapse
I'm sorry but I did read. I saw that if you have the same kernel as that of the rom you're flashing you don't have to flash boot.img. So I asked to see if stock and viper have the same kernel. I don't want to flash anything that will brick my phone.
Now one more question if you don't mind answering. I also saw that you can't downgrade RUU. So if viper is based on 2.41 RUU and stock is 2.20 RUU then will I be able to go stock after flashing viper?
I really do appreciate yalls help. i would be where I am if it weren't for you.

ImagioX1 said:
I'm sorry but I did read. I saw that if you have the same kernel as that of the rom you're flashing you don't have to flash boot.img. So I asked to see if stock and viper have the same kernel. I don't want to flash anything that will brick my phone.
Now one more question if you don't mind answering. I also saw that you can't downgrade RUU. So if viper is based on 2.41 RUU and stock is 2.20 RUU then will I be able to go stock after flashing viper?
I really do appreciate yalls help. i would be where I am if it weren't for you.
Click to expand...
Click to collapse
Yes. Just wipe you system and do a factory reset , and flash the boot.IMG for 2.20 and then flash the Rom.
If you want true stock 2.20 then you will have to relock your bootloader and then run the 2.20 RUU. You would only want to do this if making a warranty claim or something. If you want stock rooted, then yes, do what I said above
Sent from my HTC One XL using xda app-developers app

absolutelygrim said:
Yes. Just wipe you system and do a factory reset , and flash the boot.IMG for 2.20 and then flash the Rom
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Ok got it. I do appreciate your help. Flashing now.

downgrading only refers to the ruu not the zipped roms. so you can't run 1.85 ruu after running 2.20 ruu/ota but you can still flash a rom based on 1.85.
if you are reflashing the same rom you don't have to reflash boot.img but if you are flashing a new rom then you need to flash boot.img. 7-zip will tell you the crc32 of files so you see tell if it's a different checksum.

Viper Xl's great. Seems to be slightly slower than stock on some task, but the lack of bloatware, and the extensive customization is worth it. Haven't found any bugs or nothing so far. If anyones familiar with viperxl though what is the last app in the app drawer? Its got a chinese name? When it loads it says Dolby Surround but all the writing is in chinese?

ImagioX1 said:
Viper Xl's great. Seems to be slightly slower than stock on some task, but the lack of bloatware, and the extensive customization is worth it. Haven't found any bugs or nothing so far. If anyones familiar with viperxl though what is the last app in the app drawer? Its got a chinese name? When it loads it says Dolby Surround but all the writing is in chinese?
Click to expand...
Click to collapse
That's because you flashed the Voodoo mod, it's apart of the mod, theres a chinese part and a english one called "Dolby Digital" or "Dolby Surround"

When I flash ViperXL 3.1.0 JB do I need to flash a radio too? My phone has hboot 1.4 and software 2.2, so I understand that I cant flash radio with hboot 1.4? Does this mean I need to downgrade my hboot/software version?

CrossFire78 said:
When I flash ViperXL 3.1.0 JB do I need to flash a radio too? My phone has hboot 1.4 and software 2.2, so I understand that I cant flash radio with hboot 1.4? Does this mean I need to downgrade my hboot/software version?
Click to expand...
Click to collapse
Most people have good luck w/out flashing another radio.

ronnie498 said:
Most people have good luck w/out flashing another radio.
Click to expand...
Click to collapse
Hmm. Might there be a patch I'm missing out on? I just flashed one file -ViperXL 3.1.0 JB - Android File Host (692MB)
edit- Works now after another reinstall installed boot image first this time.

[Q] Problems with MD5 file trying to flash CD10 rom

I have an ATT HTC One X 2.20 Hboot 1.14 using twrp 2.4.1 and have been trying to install roms but continue to have an issue with the MD5 file. I have followed the instructions about flashing the boot.img of CM10 but it seems no matter what I do, it can't find the MD5 and says it is skipping MD5. I know just enough not to get out of a bootloop but I am quite new to this. The one odd thing I see is when I go to mount my phone in order to copy the CM10 zip file into the phone, the options I get are different than others I see online: Mount System (unchecked), Mount Data,(unchecked), Unmount Cache (checked), Unmount SD Card (checked). Any help would be awesome.

quick update; same problem
SWell, going through some of other posts and videos, I tried using goo manager to download the CM 10 zip file. But Im still stuck on boot loop. And it still says that the MD5 file was not found. I used the onexroot.com tutorial to root my phone and have superuser and twrp. Not sure what else to try. Ideas on other stable JB roms I could try? Thanks again.

In TWRP, when you install the ROM, do you have the option checked to force MD5 checked?

force check
redpoint73 said:
In TWRP, when you install the ROM, do you have the option checked to force MD5 checked?
Click to expand...
Click to collapse
I'm pretty sure I do. I have always left it unchecked. Should I check it and try again?

I've always left it unchecked (no MD5 check). If its a bad download, all that will happen is the phone will get stuck on boot, anyway.
I'd go into TWRP, and see if its checked or not. And if so, uncheck and try to flash again.

Update: No Luck
I just tried wiping system, factory reset, and cache, flashing the cm10 boot.img and then installing the CM10 zip file and checking the force MD5 and then the entire process and unchecking the force MD5 and with both attempts I get right back to the same issue. All I can say is that I'm so thankful that I created a backup in twrp. I've restored my phone at least 20 times today, haha. Learning is definitely a process. Ill take any more ideas.

Download the ROM again, may just be a bad download.

Will try
I will try to download the rom again from the CM website. If I were to try another rom (viper xl), the process should be the same correct? Thanks for the help.

alemcc said:
If I were to try another rom (viper xl), the process should be the same correct?
Click to expand...
Click to collapse
Put the ROM on your SD.
Boot into hboot, go into TWRP
In TWRP, factory reset, wipe cache, wipe Dalvik
Install ROM
Reboot
ViperXL should flash boot.img in AROMA, although its not foolproof. If the phone doesn't boot (may take about 5 min first time), then flash boot.img using fastboot.
For most ROMs, you will need to flash boot.img manually. ViperXL is one of the few exceptions (also CleanROM 5.1, I think).

Still no luck
I just tried aokp JB 4.1 with no luck. I do everything I've been told or that I have read on these forums (copy zip to SD, flash boot image, install rom...) but i continue to get the same problem: MD5 not found, skipping MD5 and so on. If anyone has any ideas I'll be happy to give any other info needed. At this point I have a rooted phone but cannot install roms. Argh!

He's not the only one. I'm on viper 3.2.3 but when trying to flash any Rom based off of AOSP or anything similar I bootloop. Yes I flash the boot.img then the Rom to no avail . I started a thread in this department called weird problem if the OP would like to take a look there.
Sent from my HTC One X using xda app-developers app

I'm new to all this, but I don't understand why certain people have this issue but most don't. Aren't all att one x phones pretty much the same?

Same thing i'm wondering
Sent from my HTC One X using xda app-developers app

you dont check any md5 checking for custom roms in twrp
you only rom i know of that you will have a md5 without anything selected is evervolv 4.2 i found a fix where you copy the CERT.SF from evervolv 4.1 to evervolv 4.2 and it will install and boot.
also always remember to "fastboot flash boot boot.img" if you are on hboot 1.14 or newer. if you going changing from sense to aosp always do full wipes no matter what. never factory reset in bootloader.

Yes I've done this countless times as I was on jellybam before going to jokers sense 4+ Rom then viper . I know the processes but something is wrong.
Sent from my HTC One X using xda app-developers app

alemcc said:
I used the onexroot.com tutorial to root my phone and have superuser and twrp.
Click to expand...
Click to collapse
I hate websites like that one. They just ripoff content from XDA, repackage it, and give little or no credit to the actual developer or XDA.
Stupid question, your bootloader is unlocked, right? In bootloader, it says UNLOCKED?
It must, for you to have TWRP. But it doesn't hurt to cover all the possibilities.

What am I missing? Need an OS, haven't S-Off'd yet

I've spent hours, and obviously am not smart enough.
ATT One X, Followed the x-factor root exploit, but didn't realize how important the "and use a recovery ADB shell or install from an update.zip to install Superuser and su" sentence is.
Tried to install a custom ROM, TWRP works great but I wiped it and went for a new Viper install, flashed the boot.img, which I now realize probably won't boot because I don't have S-Off. It just circles. I run the latest SU.zip but it still won't work
I keep trying to install older ROM's but they don't work either. All I get is a black screen and it locks up. I assume because I have Hboot 1.14
So now I have a new hboot, new TWRP, it's "tampered" and "unlocked" but I can't boot up into an old OS, and I'm not S-Off'd so I can't boot into a new OS. The new GUI for S-Off looks like what I should have used, but it would appear that I need to boot into Android first.
What do I do?

You have to flash boot.img from fastboot

Download rom, check md5
Extract rom, copy boot.img
Paste boot.img in folder with fastboot
Copy rom zip to SD card
Wipe cache, dalvik cache, system, factory reset.
Flash rom
Reboot to bootloader
Fastboot flash boot boot.img
Reboot.
If 2.14 hboot, cm10.1 with 3.4 kernel is the only aosp rom with which the touchscreen will work.
All sense roms will work.
Sent from my HTC One X using xda app-developers app
---------- Post added at 08:00 PM ---------- Previous post was at 07:52 PM ----------
RollTribe said:
You have to flash boot.img from fastboot
Click to expand...
Click to collapse
I put the whole thing cut its also possible he didn't wipe properly or something
Sent from my HTC One X using xda app-developers app

exad said:
Download rom, check md5
Extract rom, copy boot.img
Paste boot.img in folder with fastboot
Copy rom zip to SD card
Wipe cache, dalvik cache, system, factory reset.
Flash rom
Reboot to bootloader
Fastboot flash boot boot.img
Reboot.
If 2.14 hboot, cm10.1 with 3.4 kernel is the only aosp rom with which the touchscreen will work.
All sense roms will work.
Click to expand...
Click to collapse
Ok, I did that and I get a variety of problems.
use TWRP to send over the .zip ROM
wipe cache (I let the ROM install do it and manually in TWRP, both the default and advanced and clicking the default "factory reset"
use "install" to select the correct zip with the boot.img copied to my HD for fastboot
reboot into bootloader, fastboot, use DOS, fastboot says "OKAY" twice
bulletproof and cleanROM both just lock up at the white HTC menu with the red developer font. ViperXL3.2.7 just reboots back into recovery mode.
Do I need to do something with SU or Superuser or is that after I actually get a ROM installed? My CID is nothing but 1's and these ROMS are double checked for the Evita
EDIT: Viper 2.4 loads another HTC boot screen with a snake, but then reboots.

Also, I'd be fine with putting it back to stock and starting over, but I've got a CID of 11111111 (didn't write down the original), S-On and software is 2.20, I keep reading about bricks when people tried that.
I have followed the various guides at least 5 times, such as this one http://forum.xda-developers.com/showthread.php?t=1957193 and nothing, I guess I need a way to step backwards.

chris948 said:
Do I need to do something with SU or Superuser or is that after I actually get a ROM installed? My CID is nothing but 1's and these ROMS are double checked for the Evita
Click to expand...
Click to collapse
You don't need SU to flash a ROM. Once the ROMs get booted up properly, they will be rooted by default.
What version of TWRP? The newer builds have been known to be problematic, with 2.5 not working at all with CleanROM (maybe others). Recommend version 2.3, or latest official CWM.

redpoint73 said:
You don't need SU to flash a ROM. Once the ROMs get booted up properly, they will be rooted by default.
What version of TWRP? The newer builds have been known to be problematic, with 2.5 not working at all with CleanROM (maybe others). Recommend version 2.3, or latest official CWM.
Click to expand...
Click to collapse
bingo, that's what I get for logging into a website and downloading the latest version. 2.3.3 and 2.3.1 didn't help but CWM and a different ROM finally did.
thanks

chris948 said:
Also, I'd be fine with putting it back to stock and starting over, but I've got a CID of 11111111 (didn't write down the original), S-On and software is 2.20, I keep reading about bricks when people tried that.
I have followed the various guides at least 5 times, such as this one http://forum.xda-developers.com/showthread.php?t=1957193 and nothing, I guess I need a way to step backwards.
Click to expand...
Click to collapse
I had this same problem, here's what I did:
1. wrote CID back to AT&T's CID (CWS__001), here's a list: http://droider.eu/infodocs/CID list.pdf
2. relocked bootloader
3. ran 2.20 RUU
4. unlocked booloader/ got superCID
5. installed TWRP custom recovery
6. Got S-OFF -THIS WAS THE STEP I SKIPPED THE FIRST TIME
7. ran 3.18 RUU
8. install whatever you want
Hope that helps

Unlock booatloader using toolkit but keep failing rom Flash.

Hi im a bit confused I used hansoons tool kit and unlocked bootloader.
I try to flash a CM rom/kernel but i keep failing and just leaves me stuck at splash screen forcing me to use the recovery.
not sure if im doing it right but i place a folder with the zip in it go to CWM and use the zip file option there.
am i doing something?
also is it normal that after having boot loader it takes more memory?

ok i got it working.
using http://forum.xda-developers.com/showthread.php?t=1912582
not sure if thats a good one but seems up to date.
now im installing gapps "well flashing it through recovery"
any other steps im missing?

Your phone was never bricked if you were able to just reboot into bootloader...also what toolkit are you using and are you S-ON or S-OFF?

Never used a toolkit to root anything before, but I'm under the impression it just unlocks your bootloader and then flashes a recovery for you
The next step would be to download ROM of choice (+any gapps or mods wanted) and but them on sdcard
Now boot to your recovery, wipe all, flash ROM, flash any gapps or whatever
Then if its not a stock based ROM (which is most only 3 or so old stock optimized ROMs) then you need to boot back to your bootloader and flash the kernel through fastboot
Unzip the ROM, find boot.img
Open cmd/terminal in the location of the boot.img
Then type
fastboot flash boot boot.img
fastboot reboot
Now all should work
Sent from my Nexus 4 using Tapatalk 2

yup got it working thanks guys. figured it on my own a bit before.
but im running into a new problem Gapps keeps giving me the unexpected close error "i think i flashed the wrong gapps for my phone"
can i just flash the right gapps to fix it? and where can i find a source for the correct one
Hansoons toolkit,and im pretty sure its S-on is what people state when using that way,,,
also seems liek i screwed up people say dont update it after installing the rom/kernel that i linked "scv's project"
but i updated how can i undo this? do i just reflash again same kernel and zip?

If the gapps aren't specified in the op of your ROMs thread then see what version android your using and Google search
Goo inside me gapps
Then download the appropriate version and flash it in recovery. You may need to do a full wipe and then flash ROM gapps and kernel again
Sent from my Nexus 4 using Tapatalk 2

demkantor said:
If the gapps aren't specified in the op of your ROMs thread then see what version android your using and Google search
Goo inside me gapps
Then download the appropriate version and flash it in recovery. You may need to do a full wipe and then flash ROM gapps and kernel again
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
so i got gapps working
im curious how i can do a fresh wipe of rom and kernel i downloaded a update i wasnt suppose to that reverts it do i just redo the process i did when i first flashed it?
also is there a way to get teh genius button option working again when flashing?