Related
If this has been asked before then please forgive me...
I can not go back to any backup I had of CM7 or Gingerbread Sense ROM since upgrading to some Alpha ICS roms. I've tried wiping everything & started from scratch on these roms but I always get stuck at "failed to write boot partition from /tmp/boot.img" It doesn't matter what Gingerbread ROM I choose with the exception of MIUI rom (don't know why). I thought maybe I could use that as a stepping stone to go back from there but nogo. I've used RA's recovery & CWM with no success. Any ideas?
davidnjessicacruz said:
If this has been asked before then please forgive me...
I can not go back to any backup I had of CM7 or Gingerbread Sense ROM since upgrading to some Alpha ICS roms. I've tried wiping everything & started from scratch on these roms but I always get stuck at "failed to write boot partition from /tmp/boot.img" It doesn't matter what Gingerbread ROM I choose with the exception of MIUI rom (don't know why). I thought maybe I could use that as a stepping stone to go back from there but nogo. I've used RA's recovery & CWM with no success. Any ideas?
Click to expand...
Click to collapse
I would recommend tracking down calkulins format zip for the evo
1brainsurgeon said:
I would recommend tracking down calkulins format zip for the evo
Click to expand...
Click to collapse
Yeah... tried that already... Didn't fix it...
davidnjessicacruz said:
If this has been asked before then please forgive me...
I can not go back to any backup I had of CM7 or Gingerbread Sense ROM since upgrading to some Alpha ICS roms. I've tried wiping everything & started from scratch on these roms but I always get stuck at "failed to write boot partition from /tmp/boot.img" It doesn't matter what Gingerbread ROM I choose with the exception of MIUI rom (don't know why). I thought maybe I could use that as a stepping stone to go back from there but nogo. I've used RA's recovery & CWM with no success. Any ideas?
Click to expand...
Click to collapse
I can say with certainty that I don't have this problem. I've flashed every ROM from here to Timbuktu, AOKP, Deck's, Evervolv, and have had no problem restoring a nandroid of, or flashing MikG, Mik3D, MikRunny, The Express, or any other ROM I may have forgotten.
That boot partition error doesn't sound good, though. What HBOOT version do you use?
Captain_Throwback said:
I can say with certainty that I don't have this problem. I've flashed every ROM from here to Timbuktu, AOKP, Deck's, Evervolv, and have had no problem restoring a nandroid of, or flashing MikG, Mik3D, MikRunny, The Express, or any other ROM I may have forgotten.
That boot partition error doesn't sound good, though. What HBOOT version do you use?
Click to expand...
Click to collapse
HBOOT 0.97 is what I'm still using... never upgraded... should I & how do you recommend that I do so?
davidnjessicacruz said:
HBOOT 0.97 is what I'm still using... never upgraded... should I & how do you recommend that I do so?
Click to expand...
Click to collapse
No reason to upgrade - just wondering.
I'd recommend you flash a stock ROM in the bootloader - that should normalize everything, and then try those other ROMs again.
Captain_Throwback said:
No reason to upgrade - just wondering.
I'd recommend you flash a stock ROM in the bootloader - that should normalize everything, and then try those other ROMs again.
Click to expand...
Click to collapse
I assume your talking about in the recovery (aka amon ra/ clockworkmod), if so then I've tried that as well. Same issue.... This is not sounding good for me.
davidnjessicacruz said:
I assume your talking about in the recovery (aka amon ra/ clockworkmod), if so then I've tried that as well. Same issue.... This is not sounding good for me.
Click to expand...
Click to collapse
I believe he's talking about a RUU
Sent from my PC36100 using XDA App
evo4gnoob said:
I believe he's talking about a RUU
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
The stock one? Wow... don't even know how to flash that back.... hmm... I'll see if I can find it here, if not then I'll google it. I'll keep you informed.... hopefully bricking does not ensue.... any help here would be great as well
davidnjessicacruz said:
The stock one? Wow... don't even know how to flash that back.... hmm... I'll see if I can find it here, if not then I'll google it. I'll keep you informed.... hopefully bricking does not ensue.... any help here would be great as well
Click to expand...
Click to collapse
In the first "My Links" link in my sig, there are 3 of them.
They're PC36IMG files - you rename the file to exactly that - PC36IMG.zip - and put the file on the root of your sd card. Then you reboot your device into bootloader (HBOOT) mode. From a powered off state, hold the Volume down button and then press and hold the power button until you see the HBOOT screen. The file should be recognized and loaded, and after a minute or so it will ask you to update. Press Volume Up to accept, and then wait for a while.
NOTE: This will upgrade your HBOOT, but that's no big deal. The phone will reboot into the bootloader once near the beginning of the process by itself - that is also okay. Don't touch anything while it's updating.
At the end of the process, you'll need to find a PC36IMG for your preferred recovery (RA-supersonic-v2.3 recommended), which you will flash the same way as the ROM (in fact, you can replace the ROM file with the recovery file - unless you want to hold on to it, then you can just move or rename it).
Captain_Throwback said:
In the first "My Links" link in my sig, there are 3 of them.
They're PC36IMG files - you rename the file to exactly that - PC36IMG.zip - and put the file on the root of your sd card. Then you reboot your device into bootloader (HBOOT) mode. From a powered off state, hold the Volume down button and then press and hold the power button until you see the HBOOT screen. The file should be recognized and loaded, and after a minute or so it will ask you to update. Press Volume Up to accept, and then wait for a while.
NOTE: This will upgrade your HBOOT, but that's no big deal. The phone will reboot into the bootloader once near the beginning of the process by itself - that is also okay. Don't touch anything while it's updating.
At the end of the process, you'll need to find a PC36IMG for your preferred recovery (RA-supersonic-v2.3 recommended), which you will flash the same way as the ROM (in fact, you can replace the ROM file with the recovery file - unless you want to hold on to it, then you can just move or rename it).
Click to expand...
Click to collapse
Failed on #4 Boot.... it stated "failed - PU" "Partition failed" Fun times.... Now the phone is a brick (stuck at the white screen).... Where there is a will then there is a way so I'll find a way.... any help would be appreciated though....
Sooo... I was able to flash back my alternate recovery using a PC36IMG version of it. Thank god for the rooted community.... Restoring back my last backup. Funny though, that I still could not restore a rooted stock backup I had or a new upgraded .zip that I wanted to use. Common denominator in all this (even when trying to use the 4.24.651.1 version of the stock software PC36IMG), it can not write the boot.img Any one else had this problem? Next I will try to RUU which will technically make me lose root but I should be able to get it back, assuming I'm successful, since I still have S-OFF.
PS: My HBOOT now, btw, is 2.16.0001 so I know that the original attempt to get back to gingerbread was succesful
Hello guys !
First of all i want to say that I've tried EVERYTHING around to resolve the issue, but it seems that nothing is working. So long story short :
My friend bought used HTC Desire since i own DHD and he liked it alot but didnt have the money to buy DHD ,so the day he got it he tried to root it , He said that it was sucessfully and he instaleld some custom rom and went to bed,when he woke up in the morning his Desire Display was flashing with the boot animation(the ROM one) over and over again.He treid to install other ROM and the effect was the same,stuck at animation repeating over and over again.So He called me,i got to his house and tried to solve the issue but i didnt have luck there ,so i got the phone with me at my home. I started digging where the problem was...i was sure it was the rom ,tried to install 5-6 oter roms - no luck . Tried to flash with RUU- no luck ,kept getting " The main version is older" error . So i kept digging and tried to install the RUU throught H-boot by making PB99IMG.zip file,got the same error.Tried to use the update.zip solution - still no luck.Tried to change the recovery from clockwork to any other recovery ,but didnt have luck since i cant access the android and i am getting errors if i try to archive the file to update.zip.
So i need some help if its possible,sorry for my english and if the info that i provided is not that good ask me whatever u like.
also in The H-boot menu it says :
BRAVO PVt4 Ship S-ON
H-Boot-0.93.0001
MICROP-051d
TOUCH PANEL - SYNT0101
RADIO-5.11.05.14
from what i got by reading is that i cant s-off cuz of the bravo pvt4 ..
Did you wipe data after flashing?
localh0st said:
Did you wipe data after flashing?
Click to expand...
Click to collapse
Full wipe + wipe from the advanced menu !
Lol, read thru the OP and same thing going over and over in my head "Did you wipe? Did you wipe? Did you wipe?"
When you start out with "I've tried EVERYTHING", make sure you actually did try everything, because it's pretty obvious you didn't.
Did it also display flash bootanimation over and over again after Ruu?
Sent from my HTC Desire using XDA
vladrak said:
from what i got by reading is that i cant s-off cuz of the bravo pvt4 ..
Click to expand...
Click to collapse
Have a read of this
localh0st said:
Did you wipe data after flashing?
Click to expand...
Click to collapse
You have to wipe BEFORE flashing, not after.
Some Roms store important parts on /data, which will be erased during the wipe.
Sent from my HTC Desire using xda premium
Tillus said:
You have to wipe BEFORE flashing, not after.
Some Roms store important parts on /data, which will be erased during the wipe.
Sent from my HTC Desire using xda premium
Click to expand...
Click to collapse
This is true lol. If you install then wipe you prob won't be able to get further than the boot screen.
Sent from my HTC Desire using xda premium
Take it your mate didn't take a nandroid back-up before trying to flash, so he could restore it in case any issues occurred? Have you done full wipe then tried flash ROM from recovery then? Does the ROM need an ext partition - will boot loop if one doesn't exist.
Depending on the HBOOT version, using alpharev or revolutionary will S-OFF PVT4s - but this isn't the solution to your current problem unless you're trying roms that need non-stock hboots, in which case try something that doesn't first. S-OFF via AlphaRev also best done with rooted stock ROM, some custom sense ROMs also seem to work (don't know about revolutionary as i took alpharev route) - but get custom ROM running first before thinking about doing anything else.
JustAnotherCider said:
This is true lol. If you install then wipe you prob won't be able to get further than the boot screen.
Sent from my HTC Desire using xda premium
Click to expand...
Click to collapse
Dude i wiped all b4 installing any rom, anyways i finally fixed it,been trying for 2 days ,I'll explain in the next post !
beachcomber said:
Take it your mate didn't take a nandroid back-up before trying to flash, so he could restore it in case any issues occurred? Have you done full wipe then tried flash ROM from recovery then? Does the ROM need an ext partition - will boot loop if one doesn't exist.
Depending on the HBOOT version, using alpharev or revolutionary will S-OFF PVT4s - but this isn't the solution to your current problem unless you're trying roms that need non-stock hboots, in which case try something that doesn't first. S-OFF via AlphaRev also best done with rooted stock ROM, some custom sense ROMs also seem to work (don't know about revolutionary as i took alpharev route) - but get custom ROM running first before thinking about doing anything else.
Click to expand...
Click to collapse
Just saw your post. Too bad it's too late. Anyways the situation was kinda funny: So the HTC kept booting untill the "rom logo" (You know the logo after the HTC one), tried to install other ROM's (Full wipe before ofcourse) and it didn't work ofcourse, so I kept digging and i saw some threats where people were saying that clockwordrecovery wasn't working with my version h-boot, ah and trying installing RUU didnt work too(also trying to install PB99IMG.zip from sdcard didnt work too) ,was always getting "The main version is older" error! So we flashed AlphaRev, and finally the phone was S-Offed, after this i got my DHD's sd card since it was a gold card and i put it into the Desire , i had a PB99IMG.zip file from the previous day on it! So i started the bootloader, it detected the PB99IMG.zip file and I didn't get the "Main Verison is older" error, it asked if the file should be updated and i pressed "yes" and the phone gone off...guess what it was compleatly bricked,only vibrating and the screen didn't work....we were like OMG WTF ...so we installed SDK tools and started looking for adb commands/guides ...after 4 hours we were on about to quit and suicide ourselves cuz we didnt get anything and it was getting late...i was like " duh,lets blind try the PB99IMG.zip method again and rest till tomorrow" ,i downloaded the newest PB99IMG.zip from shipped-roms.com ,got it on my sd card and got the sd card back in the desire . Pressed Power + vol down,waited 2 mins and pressed vol up again,waited like 10 more mins,nothing happaned...we got all emo and mad ,2 more friends of us came to my mate's flat ( they are not into phones or anything ,complete noobs),one of them got the phone took of the baterry and the sdcard ,put the baterry back,pressed Power ON button and the phone ****ing started ....we all were like WOOOOOOOOT OMG OMG ,it was like magic xD ...so its fixed now and it has the stock rom and its unrooted...
Hi All, let me start with a warning…
total Android n00b here, doing his first ROM flash on a newly rooted T-Mobile G2. I’ve read and searched a bit in the forum threads to see if I could solve this on my own, but I do need help.
VISION PVT SHIP S-OFF
HBOOT - 0.82.0000 (PC1010000)
MICROP - 0425
RADIO - 26.02.01.15_M2
eMMC - boot
Aug 20 2010, 16:51:01
This is from using the instructions in Strawmetal’s PDF guide to Downgrading from Gingerbread to Froyo and Root. I am working with a G2 phone that was set to Factory Reset before rooting, so there is no user data to backup or worry about.
1. I downloaded the Andromadus Mimicry 1.1.2 ROM image, and verified the md5 checksum on my sdcard using the AFV Legacy application. The Gapps image also was verified as well.
2. Using ROM Manager 5.0.0.8 from the Google Market, I ran Clockwork Recovery to install the Andromadus image. I left all settings on defaults and the installer ran fine.
3. When it restarted, I was left stuck at the white HTC screen for ages… the longest I left it was 20 mins. After that, I pulled the battery and restarted. Same white HTC screen.
4. I tried using Volume (+) key and Power On to get back to Clockwork Recovery, but the phone vibrated (buzzed) 3x times quickly, and the Power LED lamp pulsed an amber color. Again, yank battery, restart, same white HTC screen.
5. finally I decided to read more of the help for adb, and found the command “adb reboot-bootloader”. This let me get into the default Recovery mode, and it proceeded to find the PC10IMG.zip I still had on the sdcard from doing the Froyo downgrade. Recovery checked it out, ran it and restored the stock Froyo image and my phone did a proper restart. WHEW.
After that, I had to run adb to install the hboot recovery image file, and the busybox checksums were valid according to Strawmetal’s PDF instructions to get permanent root back after restoring the stock Froyo image.
I have done this process about 4 times, and am really good at typing inside adb now
But I’m lost…
-did I pick a ROM that doesn’t work with the G2? Other posters to the forum thread appear to be using the HTC Vision or G2.
-is ROM Manager not a good way to install a ROM?
-when I tried to get back into Recovery, what do the 3x buzzes/amber power LED mean?
-I never got to install the Gapps image; was I supposed to install that first, then the ROM image?
I imagine I did something wrong (duh!), but I can’t spot it. If someone can help me through this, I’d appreciate some advice very much.
thanks!
Rather than clockwork, use 4EXT recovery, much better for our device. ROM manager and clockwork have grown very iffy over the past year. Don't use rom manager to install a rom, download the zip yourself and manually install it in recovery.
Next you need to find the "superwipe+ext4.zip" floating around here, it is indispensable for FULLY wiping your phone when switching roms.
Mimicry works fine on the G2, in fact everything (except a few sense roms that need a Desire Z hboot) in the development section runs fine on the G2.
So....get the ROM, GApps for that ROM, the Superwipe zip (you will flash this right before you begin flashing the rom) on your SD card and make sure you are using 4EXT recovery (find the link in the dev section).
Make sure before you do ANYTHING you make a Nandroid backup (using your recovery).
Your issue is actually addressed in the Mimicry OP, please read it first. That said, the problem is almost certainly because you're coming from GB without a full wipe. You can use 4ext to repartiton/wipe all, or you can use superwipe+ext4 as mentioned by Nospin.
Sent from my HTC Vision using xda premium
Hi Nospin,
Thank you very much for your suggestions!
I will revise my root and remove Clockwork, and switch to 4EXT instead.
I appreciate the idea of "superwipe"; I will look for that as well today.
If I understand everything right...
-replace CWM with 4EXT
-place superwipe.zip, Gapps.zip and the Mimicry ROM.zip on the top level of the sdcard first.
-reboot the phone and run 4EXT recovery
-select superwipe to run first, then the ROM and then Gapps
-then restart the phone
When I used CWM before to install the ROM, it rebooted on its own before I could install Gapps. Will 4EXT let me do each install right after each other or do I have to return to 4EXT for each separate install?
regards,
motionmonk
Nospin said:
Rather than clockwork, use 4EXT recovery, much better for our device. ROM manager and clockwork have grown very iffy over the past year. Don't use rom manager to install a rom, download the zip yourself and manually install it in recovery.
Next you need to find the "superwipe+ext4.zip" floating around here, it is indispensable for FULLY wiping your phone when switching roms.
Mimicry works fine on the G2, in fact everything (except a few sense roms that need a Desire Z hboot) in the development section runs fine on the G2.
So....get the ROM, GApps for that ROM, the Superwipe zip (you will flash this right before you begin flashing the rom) on your SD card and make sure you are using 4EXT recovery (find the link in the dev section).
Make sure before you do ANYTHING you make a Nandroid backup (using your recovery).
Click to expand...
Click to collapse
Hi blk_jack,
I went back to the Mimicry page and re-read the FAQ section.
I think what I got out of it the first time was that if the ROM flash failed, it could be a corrupt ROM image. I will definitely use 4EXT to repartition before I try again with a ROM flash.
I guess I am still getting used to the terms for everything; can 4EXT do the nandroid backup? or is there a better process for setting that up?
thank you!
motionmonk
blk_jack said:
Your issue is actually addressed in the Mimicry OP, please read it first. That said, the problem is almost certainly because you're coming from GB without a full wipe. You can use 4ext to repartiton/wipe all, or you can use superwipe+ext4 as mentioned by Nospin.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Yes, you should be able to flash the rom and then GApps without rebooting. Give me a few and I will send you a PM with a few links....
Shot you a PM.
Thanks! I'll check it out :good:
Nospin said:
Shot you a PM.
Click to expand...
Click to collapse
Update-not working
Ok...
I re-flashed back to stock Froyo, and did a permanent root.
Installed 4ext Recovery (instead of Clockwork), and got a copy of SuperwipeG2+ext4;
I copied new checksum'd copies of Mimicry 1.1.2 ROM and GApps to my sdcard.
Booted into 4ext Recovery and installed from .zip the SuperwipeG2+ext4 file.
System, data and cache are all converted to ext4 partitions.
Wiped the system and data and cache partitions.
Installed from inside Recovery the Mimicry ROM and then the GApps archives.
No errors reported.
Upon reboot, I still get the white HTC screen. UGH.
I've left it on in that state for 30 mins... I had to yank the battery after that in shame...
I have tried to make sure that I read up on background steps, and I feel I do understand the overall process, but something is still getting in the way. I am doing this as I mentioned in an earlier post on a factory reset G2 with a clean erased SD card (has the stock Froyo image, Andromadus Mimicry ROM and GApps only). There is no SIM card installed either, wifi is off (to avoid OTA upgrade requests).
Are there other things I can try, or info I can supply that would help? I think I'm so close to getting this done... I must be overlooking something obvious.
I run that by rom along with Cm9 beta..... Try adding that to your boot process. Just Cm9 beta..... Other than version of crash.... That's just what I have experienced
Sent from my HTC Vision using xda premium
Hi amogil,
Just to be sure I understand, are you saying you are swapping between Andromadus and CM9 beta on your phone?
Did you flash CM9 first? and then Andromadus?
or just carrying the CM9 beta image and running Andromadus?
Sorry, I'm all sorts of confused here lol
thanks
amogil said:
I run that by rom along with Cm9 beta..... Try adding that to your boot process. Just Cm9 beta..... Other than version of crash.... That's just what I have experienced
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Ugh....it's frustrating isn't it?
Can you boot into any other rom? For example if you downloaded CM7.2? If you don't have any problems we can eliminate some possibilities.....
I had a similar problem booting into Mimicry my first time, in that I could get past the white HTC screen but after that my screen would just go black. After a couple frustrating hours what ended up working for me was downloading the older version (1.1.1 I think?) and that booted up fine . Then after letting that boot I went back into recovery and flashed 1.1.2 without wiping (I might have wiped cache and dalvik...). Everything worked great after that. Not the same problem as you, but similar.....
It's definitely a thought, and I believe that's what amogil is telling me too...
Ya, I can try a different ROM and report back.
I guess I should go back to stock Froyo and then start from CM7.2, and if that boots, try Mimicry again?
-from the Andromadus FAQ, it says it if a different ROM is based on ICS9, you shouldn't have to wipe. But with CM7, I'd have to wipe the Dalvik cache, yes?
-since CM7 is obviously not based on ICS9, would being able to launch into that show some details I can't see at present? Just was curious.
Or, do you think it better to go stock Froyo and then the older Mimicry ROM?
Either way, I'll make sure that I use the Superwipe to set things to ext4 first.
thanks guys for the ideas,
motionmonk
Nospin said:
Ugh....it's frustrating isn't it?
Can you boot into any other rom? For example if you downloaded CM7.2? If you don't have any problems we can eliminate some possibilities.....
I had a similar problem booting into Mimicry my first time, in that I could get past the white HTC screen but after that my screen would just go black. After a couple frustrating hours what ended up working for me was downloading the older version (1.1.1 I think?) and that booted up fine . Then after letting that boot I went back into recovery and flashed 1.1.2 without wiping (I might have wiped cache and dalvik...). Everything worked great after that. Not the same problem as you, but similar.....
Click to expand...
Click to collapse
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
SUCCESS!
Woohoo!
It works!
Since I had an ICS9 ROM already in place and was planning to wipe back to stock anyways, I tried flashing the older Andromadus 1.1.0 ROM.
What a surprise and treat to see the startup animation!
After poking around for an hour inside it, I then tried Recovery to reflash to the newest 1.1.2 ROM.
YAY! It works!
OMG, having a new ROM is like having a new phone-- there are so many improvements to the UI and it's quick and speedy versus GB. Dang, I'm happy now :victory:
Observations:
1. I did notice that inside Recovery, my touchscreen was barely functional when I tried to update from 1.1.0 up to 1.1.2-- I had to use the Volume +/- and the d-pad button to make selections. After the flash, the touchscreen is as responsive as ever.
2. it's got me thinking, that there must be a setting that is expected in the v1.1.2 ROM that the v1.1.0 ROM installed. Or could something else be the issue? I mean absolutely no disrespect to the developers... but on the technical side, I'm just curious what possibilities exist that might lead to this situation.
3. backup question... when I use MyBackup Pro, I know I can make an archive of the apps I've installed, and an archive of the data (documents, music, settings). Is a nandroid backup different from that? when I see the backup/restore options inside of 4ext Recovery, what are those doing that's different from what I get from MyBackup Pro?
thanks for all the help and encouragement. I have a new ROM installed! :good:
strawmetal said:
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Oooh, a possibility. We will see if he can boot a different rom.
Whenever you switch roms (even if they are using the same Android version as a base) I suggest a full wipe. (Wipe all user data + Dalvik Cache + Cache, or just flash the superwipe zip). When upgrading the rom you are currently on (say upgrading CM Nightlies or going from Mimicry 1.1.1 to 1.1.2) you only need to really wipe cache and dalvik cache. Unless the dev states otherwise of course.
Hi strawmetal,
It turns out that I did have s-off after all...
1. after one of the many attempts to flash the ROM image and restoring back to stock Froyo, I said that "I'm gonna start this entire process over to be sure." So I get stuck using the fre3vo tool for about 30 minutes, rebooting and trying different address ranges to find the exploit.
Never found one... oh no, what did I do to the phone now??
-then it hit me; if it can't find an exploit... then it must already been used!
2. also, I did check each time I was in bootloader that my S-OFF was there and the radio and hboot were not changing versions.
3. Hehe, and the best indication was... being able to boot up finally!
I also have your Strawmetal.CM.V6.zip on my sdcard; if the downflash (?) to the Andromadus older ROM didn't work, yours was the CM7 image I wanted to try. If it's ok, I think I want to play around inside CM9 for a bit and then try yours out after that. I don't want to overwhelm my poor brain!
thank you for your suggestion... that definitely would be something to check as well.
strawmetal said:
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Thank You All!
A big shout out to:
Nospin
blk_jack
amogil
strawmetal
for taking the time out to help a total n00b stumble through his first ROM flash.
I really appreciate the points you guys made, and the help provided.
Thank you!
I hope that one day I can help someone else out with a problem and pass the kindness forward.
Yay! I have a working ROM!
motionmonk
motionmonk said:
Hi strawmetal,
It turns out that I did have s-off after all...
1. after one of the many attempts to flash the ROM image and restoring back to stock Froyo, I said that "I'm gonna start this entire process over to be sure." So I get stuck using the fre3vo tool for about 30 minutes, rebooting and trying different address ranges to find the exploit.
Never found one... oh no, what did I do to the phone now??
-then it hit me; if it can't find an exploit... then it must already been used!
2. also, I did check each time I was in bootloader that my S-OFF was there and the radio and hboot were not changing versions.
3. Hehe, and the best indication was... being able to boot up finally!
I also have your Strawmetal.CM.V6.zip on my sdcard; if the downflash (?) to the Andromadus older ROM didn't work, yours was the CM7 image I wanted to try. If it's ok, I think I want to play around inside CM9 for a bit and then try yours out after that. I don't want to overwhelm my poor brain!
thank you for your suggestion... that definitely would be something to check as well.
Click to expand...
Click to collapse
The bootloader can show a false s-off. I've personally experienced this. By the time "HTCDev bootloader unlock" came out i was already rooted. But as curious as I was I decided to try it out. Flashed an RUU ( my my why would I do that ) Got back s-on( guess this was false too) then I used HTCDev method to prove i'm a total noob. Then i relocked it using Nipqer's guide and followed setherio's method again. I was able to use the stock froyo, but no other rom would boot( false s-off being the culprit ). This time I ran to #g2root on freenode. Nipqer saved me.
WOW. i just realized there is SO MUCH I need to catch up on!
I'll have to look up some of these guides later today... but the RUU is the ROM upgrade, right?
Did you ever find a reason why you got the false S-OFF flag? It's clear that the way I was looking at the failed fre3vo exploit as proof of S-OFF isn't always going to be true... but how would you separate a false S-OFF flag from lets say a wrong hboot image?
BTW, your PDF on downgrading and rooting the G2 was a godsend. Very very helpful and clear.
One of the reasons why I took so long to try rooting was that I was confused by the different methods and the replies of X not working, Y is a better way... going through your guide and the info here on xda cleared alot of things up. :good:
strawmetal said:
The bootloader can show a false s-off. I've personally experienced this. By the time "HTCDev bootloader unlock" came out i was already rooted. But as curious as I was I decided to try it out. Flashed an RUU ( my my why would I do that ) Got back s-on( guess this was false too) then I used HTCDev method to prove i'm a total noob. Then i relocked it using Nipqer's guide and followed setherio's method again. I was able to use the stock froyo, but no other rom would boot( false s-off being the culprit ). This time I ran to #g2root on freenode. Nipqer saved me.
Click to expand...
Click to collapse
issue has been SOLVED thanks lo2ay
seems a clear head works wonders.
Ok this is gonna take some explaining which i will try my best to do, hopefully somebody can point out my error or solution.
Today i thought id go back to sense rom (doesnt matter which as i will explain) mtds all reset back to stock p wilfredfire or whatever your called lol) full fresh wipes and temp 2.5 cwm flashed (i dont use rom manager, its deleted from my roms) so temp cwm recovery 2.5 boots and the 1st strange thing occurs... The screen menus are all split in half! Eg have you ever taken a screenshot and found it split in half? Well thats what my menu options look like! On each option selected via up/down using vol key it changes to normal, split, normal split etc etc same in sub menus too.
So i just get on with things and try to flash sense rom....... Now i get some error, something to do with 1.sysE sdext not found? 2.chown xbin a2sd? 3.maybe something else cant read it as its all shown on the split screen lol.
Ive installed permanent 2.5 cwm and get same errors but not split screen issues?
Now ive never had this problem before but i have changed my sdcard and it has a 1gb partition which is only ever used for on sense roms and is partitioned from cwm 5.0.2.8 version just like my previous sdcard was.
I have 2 theories as too whats going on but not convinced.
1. Maybe my sdcard is ****e and it wasnt the sdcard i used to s-off with!! Does a new sdcard need to be goldcarded? I really dont think this is the issue.
2. I was having issues with some data/app duplication files from external roms which i used a while back. I fixed these issues by deleting all found existing files containing a2sd wording but i cant recall the paths of them eg. Some from etc/init'd but also others from outside of system folder! Maybe sys and others too but it was a while back and been on lewa for so long without any issues regarding this problem.
So is it possible ive deleted some file that is not recreated with a fresh rom install? Eg its a phone file that remains no matter what rom or cwm used?
This is only happening when im trying to flash roms/restores that dont require edify i.e 2.5 cwm needed and when im back using cwm 5.0.2.8 all roms and restores are fine. even rempuzzle which is sense but doesnt require using 2.5.
So im stumped as i can flash a sense rom but not older sense roms via temp or permanent 2.5 cwm, its nothing to do with my mtd, if it was a permanent file i deleted then it should be consistent across all roms/cwm but isnt. Ive changed sdcards lots of times but they have been used as goldcards in the past where my new one has not?
Ive tried rom manager too, still get split screen and same errors!?
Tricky one eh!! Lol.
Forum fishing.... Who's biting!
Maybe your cwm zip got corrupted..
saadislam said:
Maybe your cwm zip got corrupted..
Click to expand...
Click to collapse
Was my first thought, too (but I guess you already checked this?)
Indeed a tricky one. For the sd card guess: nah, I've dropped my stock 2 gb (I made the gold card with) for a 8 gb class 4 and later on for a 8 gb class 10 and never had any issues.
Regarding a missing "permanent" file: I'd also doubt this as such a file should be damaged or deleted in many other cases, too (flashing/formatting/factory resets/partitioning etc), at least once in a while. I'm quite sure this would happen more often, at least.
I also thought it could be a problem with the display driver but I don't know enough about the hard- and software to say it could...
Is rempuzzle still froyo or already gb?
If it has to do with leftovers or missing stuff I'd more likely guess that something with the different cwm versions has been messed up. But like I said: I don't really know enough about it.
Swyped from my HTC Wildfire (Buzz)
slymobi said:
Ok this is gonna take some explaining which i will try my best to do, hopefully somebody can point out my error or solution.
Today i thought id go back to sense rom (doesnt matter which as i will explain) mtds all reset back to stock p wilfredfire or whatever your called lol) full fresh wipes and temp 2.5 cwm flashed (i dont use rom manager, its deleted from my roms) so temp cwm recovery 2.5 boots and the 1st strange thing occurs... The screen menus are all split in half! Eg have you ever taken a screenshot and found it split in half? Well thats what my menu options look like! On each option selected via up/down using vol key it changes to normal, split, normal split etc etc same in sub menus too.
So i just get on with things and try to flash sense rom....... Now i get some error, something to do with 1.sysE sdext not found? 2.chown xbin a2sd? 3.maybe something else cant read it as its all shown on the split screen lol.
Ive installed permanent 2.5 cwm and get same errors but not split screen issues?
Now ive never had this problem before but i have changed my sdcard and it has a 1gb partition which is only ever used for on sense roms and is partitioned from cwm 5.0.2.8 version just like my previous sdcard was.
I have 2 theories as too whats going on but not convinced.
1. Maybe my sdcard is ****e and it wasnt the sdcard i used to s-off with!! Does a new sdcard need to be goldcarded? I really dont think this is the issue.
2. I was having issues with some data/app duplication files from external roms which i used a while back. I fixed these issues by deleting all found existing files containing a2sd wording but i cant recall the paths of them eg. Some from etc/init'd but also others from outside of system folder! Maybe sys and others too but it was a while back and been on lewa for so long without any issues regarding this problem.
So is it possible ive deleted some file that is not recreated with a fresh rom install? Eg its a phone file that remains no matter what rom or cwm used?
This is only happening when im trying to flash roms/restores that dont require edify i.e 2.5 cwm needed and when im back using cwm 5.0.2.8 all roms and restores are fine. even rempuzzle which is sense but doesnt require using 2.5.
So im stumped as i can flash a sense rom but not older sense roms via temp or permanent 2.5 cwm, its nothing to do with my mtd, if it was a permanent file i deleted then it should be consistent across all roms/cwm but isnt. Ive changed sdcards lots of times but they have been used as goldcards in the past where my new one has not?
Ive tried rom manager too, still get split screen and same errors!?
Tricky one eh!! Lol.
Forum fishing.... Who's biting!
Click to expand...
Click to collapse
I'm also having the same issue,i used rom manager to get temp. 2.5 recovery to flash the radio, and got split screen. i flashed it anyway successfully.
This might sound noobish, but i think mokee os and a few foreign roms are to blame (roms from the same source you got mokee).
I'm saying this because it all started when i reverted back to cm9 from mokee and few of those foreign ones.
just sharing my experience, i might be wrong coz I'm not technically sound as you ppl are.
Sent from my HTC Wildfire using Tapatalk 2
I've had that split screen before, it happened to me when my permanent recovery was 5.0.2.8
and temporary was 5.0.2.0
any older temp recovery with 5.0.2.8 as permanent will make this bug. But everything is working tho.
That's a tricky one indeed
Sent from my HTC Wildfire using Tapatalk 2
Wasimk32 said:
I'm also having the same issue,i used rom manager to get temp. 2.5 recovery to flash the radio, and got split screen. i flashed it anyway successfully.
This might sound noobish, but i think mokee os and a few foreign roms are to blame (roms from the same source you got mokee).
I'm saying this because it all started when i reverted back to cm9 from mokee and few of those foreign ones.
just sharing my experience, i might be wrong coz I'm not technically sound as you ppl are.
Sent from my HTC Wildfire using Tapatalk 2
Click to expand...
Click to collapse
Its a good point you make, as it could well be that but that would mean that one of the external roms we used has a bogus file sticking after full wipes and rom changes?? I cant see it being that but maybe wrong?
lo2ay said:
I've had that split screen before, it happened to me when my permanent recovery was 5.0.2.8
and temporary was 5.0.2.0
any older temp recovery with 5.0.2.8 as permanent will make this bug. But everything is working tho.
That's a tricky one indeed
Sent from my HTC Wildfire using Tapatalk 2
Click to expand...
Click to collapse
Mmmm so cwm 5028 perm is the split screen cause you say? Will go install 5020 and test.
Forum fishing.... Who's biting!
lo2ay i think i love you man. solved.
and heres how.............
unzipped a pc49img.zip and put in recoveryimg of 5.0.2.0 booted into bootloader and ran the update. rebooted then booted into recovery 5.0.2.0 wiped all and flashed temp 2.5 ( woo woo all full screen) flashed wildpuzzle (woo woo no errors)
SO CONCLUSION IS THAT CWM 5.0.2.8 IS MISSING SOMETHING NEEDED FOR OLDER EDIFY ROM INSTALLS EVEN WHEN USING THE TEMP 2.5 CWM.
I JUST REMEMBERED TOO that in the past i was on 5.0.2.0 and not 5.0.2.8 so i dont know why i started using the 5.0.2.8 anyway ??? well that has now found its way to the recycle bin lol.
so simple in the end lol.
many thanks to lo2ay for sending me in the right direction. xxxxxxxx lol
Glad I helped
Sent from my HTC Wildfire using Tapatalk 2
Did you get the other issue resolved? That chown etc error?
The error came because of the following.
1. You flashed CM rom from sense, you had MTD (For example 135 & 5)
2. This will install system partition and data partition for this MTD
3. Now you decide to go back to sense. and flashed MTD (250 40)
4. Even though you flash this MTD bravo file, your sense rom cant fit into your 135 system partition the 250 partition will be written only on boot of your ROM. Before that sense ROM must be written into your system
5. So error will come throwing all nonsense on the screen like chown error etc
6. How to solve this??
Flash a CM rom with MTD as 250 and 40 MTD. Once your ROM is on, check you have 175Mb as total memory, not more than that in your storage setting
7. Now flash a sense rom booting into recovery.. viola no errors
I guess it worked for you because you got fed up and flashed a CM rom over 250 40 MTD
and then flashed this recovery problem and then turned to sense..
At that point, no issues with system partition and wildpuzzle would have fitted correctly
Am i right???
Sam3087 said:
Did you get the other issue resolved? That chown etc error?
The error came because of the following.
1. You flashed CM rom from sense, you had MTD (For example 135 & 5)
2. This will install system partition and data partition for this MTD
3. Now you decide to go back to sense. and flashed MTD (250 40)
4. Even though you flash this MTD bravo file, your sense rom cant fit into your 135 system partition the 250 partition will be written only on boot of your ROM. Before that sense ROM must be written into your system
5. So error will come throwing all nonsense on the screen like chown error etc
6. How to solve this??
Flash a CM rom with MTD as 250 and 40 MTD. Once your ROM is on, check you have 175Mb as total memory, not more than that in your storage setting
7. Now flash a sense rom booting into recovery.. viola no errors
I guess it worked for you because you got fed up and flashed a CM rom over 250 40 MTD
and then flashed this recovery problem and then turned to sense..
At that point, no issues with system partition and wildpuzzle would have fitted correctly
Am i right???
Click to expand...
Click to collapse
Yes and no ? My mtds had been reset then flashed cm to confirm.so in theory I was all ready to flash sense as partition was showing the size at 250 40 but must have been a false reading! I know exactly what your saying and it makes sense,I triple reset my mtds but obviously something stuck somewhere lol.I've done this 100s of time but like I've said it was always with cwm 5.0.2.0 not 5.0.2.8 which I can't understand why or when I was using this version. I pre edit my roms and normally have a universal mtd setting that is acceptable for any of my roms I flash so its gotta be the cwm. its all fixed now with a clean cwm.cheers though.
sent mysteriously via OTA
slymobi said:
Yes and no ? My mtds had been reset then flashed cm to confirm.so in theory I was all ready to flash sense as partition was showing the size at 250 40 but must have been a false reading! I know exactly what your saying and it makes sense,I triple reset my mtds but obviously something stuck somewhere lol.I've done this 100s of time but like I've said it was always with cwm 5.0.2.0 not 5.0.2.8 which I can't understand why or when I was using this version. I pre edit my roms and normally have a universal mtd setting that is acceptable for any of my roms I flash so its gotta be the cwm. its all fixed now with a clean cwm.cheers though.
sent mysteriously via OTA
Click to expand...
Click to collapse
Oh
Anyways am glad that its working back alright..
I can keep an eye on the "show your display thread" again :good: :laugh:
slymobi said:
Yes and no ? My mtds had been reset then flashed cm to confirm.so in theory I was all ready to flash sense as partition was showing the size at 250 40 but must have been a false reading! I know exactly what your saying and it makes sense,I triple reset my mtds but obviously something stuck somewhere lol.I've done this 100s of time but like I've said it was always with cwm 5.0.2.0 not 5.0.2.8 which I can't understand why or when I was using this version. I pre edit my roms and normally have a universal mtd setting that is acceptable for any of my roms I flash so its gotta be the cwm. its all fixed now with a clean cwm.cheers though.
sent mysteriously via OTA
Click to expand...
Click to collapse
Do you have the off charge bug with 5.0.2.0? That´s the reason I have 5.0.2.8 instead.
DMarzal said:
Do you have the off charge bug with 5.0.2.0? That´s the reason I have 5.0.2.8 instead.
Click to expand...
Click to collapse
I thought that was on 4.0.1.4?
DMarzal said:
Do you have the off charge bug with 5.0.2.0? That´s the reason I have 5.0.2.8 instead.
Click to expand...
Click to collapse
not what i know of but then again i never have my phone off to charge.
Hey Guys Thank You For Taking A Look At My Thread.Lets Cut To The Chase.I Have A HUGE PROBLEM with my Replacement Incredible 2.I Rooted my phone with Tacoroot,and everything was fine.Flashed Condemed CM7.2 and started realizing i didn't like it as much,so i made a BACKUP just in case i wanted to return to the CM goodness.Went to TSMTrinity's Sense 2.1 Version 4.5 S,and here's where the problem started happening. After I set up everything on my Sense 2.1 ROM,i backed it up,the screen would get to the boot animation,get past the boot animation,id see my lock screen for 1 SECOND,and then it would start the bootup again.seeing as this was a problem,i WIPED All Cache and Factory Reset/Wipe Data on My Revolutionary Recovery.Then,I Restored the 2.1 Backup that i created and everything was fine again.Then again,i decided to Flash Mikrunny's Sense 3.5 ROM,which after i set up,worked fine,UNTIL YESTERDAY.I was driving in my car yesterday,listening to music on The STOCK HTC Music app on Sense 3.5,and the phone rebooted on its own.And it would not stop until i took the battery out.I got home,charged the battery for a bit,(shut down that is),then headed to recovery.I took out the SD card and rebooted the phone,but no luck.tried this rebooting process for an hour,until i decided to wipe cache and factory reset to my 2.1 ROM BACKUP.it works,but i just wanna know,am i doing something noobingly wrong when backing up and restoring roms? Also,i use Revolutionary's Backup,or I think its called Nandroid,to do backups and restores,and ROM MANAGER to edit their names and delete them.Also,an added side to his problem,when i boot to the Hboot screen,when it loads,for a few of the items it says,missing or wrong image.could that be the problem?? THANK YOU SO MUCH WHO REPLIES AND HELPS.:crying:
DroidUser_Wind said:
Hey Guys Thank You For Taking A Look At My Thread.Lets Cut To The Chase.I Have A HUGE PROBLEM with my Replacement Incredible 2.I Rooted my phone with Tacoroot,and everything was fine.Flashed Condemed CM7.2 and started realizing i didn't like it as much,so i made a BACKUP just in case i wanted to return to the CM goodness.Went to TSMTrinity's Sense 2.1 Version 4.5 S,and here's where the problem started happening. After I set up everything on my Sense 2.1 ROM,i backed it up,the screen would get to the boot animation,get past the boot animation,id see my lock screen for 1 SECOND,and then it would start the bootup again.seeing as this was a problem,i WIPED All Cache and Factory Reset/Wipe Data on My Revolutionary Recovery.Then,I Restored the 2.1 Backup that i created and everything was fine again.Then again,i decided to Flash Mikrunny's Sense 3.5 ROM,which after i set up,worked fine,UNTIL YESTERDAY.I was driving in my car yesterday,listening to music on The STOCK HTC Music app on Sense 3.5,and the phone rebooted on its own.And it would not stop until i took the battery out.I got home,charged the battery for a bit,(shut down that is),then headed to recovery.I took out the SD card and rebooted the phone,but no luck.tried this rebooting process for an hour,until i decided to wipe cache and factory reset to my 2.1 ROM BACKUP.it works,but i just wanna know,am i doing something noobingly wrong when backing up and restoring roms? Also,i use Revolutionary's Backup,or I think its called Nandroid,to do backups and restores,and ROM MANAGER to edit their names and delete them.Also,an added side to his problem,when i boot to the Hboot screen,when it loads,for a few of the items it says,missing or wrong image.could that be the problem?? THANK YOU SO MUCH WHO REPLIES AND HELPS.:crying:
Click to expand...
Click to collapse
1..update your recovery which is probly clockwork mod....i suggest you get your phone usable for a few minutes and go to 4ext.net and download and install that..its touch based recovery or also check out twrp if you want an alt if you dont like it
2....update your radio ...newest one can be found in the venom rom thread i think there are directions there http://forum.xda-developers.com/showthread.php?t=1953899
3.....wipe everything ....check out my wipe script in the dev section if you want max cleanification http://forum.xda-developers.com/showthread.php?t=2013242
4...flash what ever rom...if you like sense use viper i hear good things or check out my incredibly paranoid rom or all the other roms ..pick your poison
chillybean said:
1..update your recovery which is probly clockwork mod....i suggest you get your phone usable for a few minutes and go to 4ext.net and download and install that..its touch based recovery or also check out twrp if you want an alt if you dont like it
2....update your radio ...newest one can be found in the venom rom thread i think there are directions there http://forum.xda-developers.com/showthread.php?t=1953899
3.....wipe everything ....check out my wipe script in the dev section if you want max cleanification http://forum.xda-developers.com/showthread.php?t=2013242
4...flash what ever rom...if you like sense use viper i hear good things or check out my incredibly paranoid rom or all the other roms ..pick your poison
Click to expand...
Click to collapse
DUDE.THANK YOU so MUCH FOR REPLYING.Ill try what you told me tonight,and ill let you know how it goes down.thanks again chills.:good:
chillybean said:
1..update your recovery which is probly clockwork mod....i suggest you get your phone usable for a few minutes and go to 4ext.net and download and install that..its touch based recovery or also check out twrp if you want an alt if you dont like it
2....update your radio ...newest one can be found in the venom rom thread i think there are directions there http://forum.xda-developers.com/showthread.php?t=1953899
3.....wipe everything ....check out my wipe script in the dev section if you want max cleanification http://forum.xda-developers.com/showthread.php?t=2013242
4...flash what ever rom...if you like sense use viper i hear good things or check out my incredibly paranoid rom or all the other roms ..pick your poison
Click to expand...
Click to collapse
What OP wrote applies to me as well. I am looking for something better than aerovan's CM9 (which has been my DD), and thought I would give Viper a try. Without fail, bootlooping (which I could have guessed since I did tacoroot and this seems to be an issue with sense based roms).
That said, I tried steps 1 through 4 and the bootlooping stopped in Viper - it goes through startup and just shuts down before leaving the boot screen. One strange thing that I noticed is that the ICS Firmware/radio with Viper (which I loaded in CWM), wouldn't load in 4ext. Maybe I'll give paranoid a go if I can't resolve this bootlooping issue in Viper! I hope OP has better luck.
U don't flash radio in cwm..look for a how to.. can't explain I'm working sry
Sent from my Incredible 2 using xda app-developers app
I'm not as knowledgeable as Chilly, but a thought did occur to me. if the cm9 rom included a kernel on the flash and then you went to a sense based rom that didn't include a kernel that could cause a problem. I believe that I read that cm using a kernel that is asop based while sense roms use a different based kernel. You may check to see what kernel you have and then check for the recomended kernel for that rom and flash that kernel. don't forget to wipe.
Jasonp0 said:
I'm not as knowledgeable as Chilly, but a thought did occur to me. if the cm9 rom included a kernel on the flash and then you went to a sense based rom that didn't include a kernel that could cause a problem. I believe that I read that cm using a kernel that is asop based while sense roms use a different based kernel. You may check to see what kernel you have and then check for the recomended kernel for that rom and flash that kernel. don't forget to wipe.
Click to expand...
Click to collapse
All of the roms come with a kernel for our phone, but certainly, don't flash a sense kernel with aosp or vice versa after rom flash. Chilly is right. Flashing a newer radio should fix the problem and the radio is flashed with a PG32IMG.zip in the bootloader, not in the recovery.
gtdtm said:
All of the roms come with a kernel for our phone, but certainly, don't flash a sense kernel with aosp or vice versa after rom flash. Chilly is right. Flashing a newer radio should fix the problem and the radio is flashed with a PG32IMG.zip in the bootloader, not in the recovery.
Click to expand...
Click to collapse
Good call. When chilly said you don't flash kernels in recovery I hit my head. I flashed the radio, but now my challenge is getting back into recovery since I renamed the file and bootloader always finds it and wants to reboot or I load CM9 which stays on flash screen. I'll figure something out, maybe with adb. Thanks.
Power down, pop the sd out, boot to recovery, rename file, profit.
gtdtm said:
Power down, pop the sd out, boot to recovery, rename file, profit.
Click to expand...
Click to collapse
Didn't think of that. adb did the trick though. In business with VenomInc!
Thank you all.
digitalshepard said:
Didn't think of that. adb did the trick though. In business with VenomInc!
Thank you all.
Click to expand...
Click to collapse
good lucking going back to aosp lol
almost thesame problem
chillybean said:
U don't flash radio in cwm..look for a how to.. can't explain I'm working sry
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
i made a stupid mistake of flashing radio in recovery, in fact the radio is for Samsung at&t and now my phone vibrates it doesnt show htc quietly brilliant, only vibrates and orange light with black screen untill i pull out the battery... i was able to return to stuck and it can only boot if its connected to power, it doesn't read sd card while android is booted and in recovery to, only in bootloader it reads sd... error in mounting if i try to... i flashed RUU.exe 2.3.3 and 2 other RUUs for my droid inc 2 but it keeps vibrating... please help me!!! thanks
I made the same mistake when i first gained s-off for my dinc2. the thing with the venom rom tho is if you ever want to go back to aosp ull need to gets chill's anti-venom zip and flash it through recovery because doing a normal wipe wont do the trick. also a helpful trick that worked for me with roms if i ever start getting boot loops i go into recovery from the bootloader menu and i wipe the dalvik cache under advanced and then wipe the chache under mounts and storage and it always works like a charm for me. but ive also learned that you have to be careful which kernel you flash with the rom of your choice because not only will it cause lags if you happen to get past the boot animation to the main screen but in some cases it can cause breaks in your framework like your wifi data etc. im not an expert tho those are just suggestions that im familiar with because theyve already happened to me before. hope this helps in any way.