i cant install no roms every rom i put in stay stuck at boot screen doesnt freeze just hangs on boot what can i do???????:crying::crying::crying:
crimedave1987 said:
i cant install no roms every rom i put in stay stuck at boot screen doesnt freeze just hangs on boot what can i do???????:crying::crying::crying:
Click to expand...
Click to collapse
are you s-on or s-off?
mattlowry said:
are you s-on or s-off?
Click to expand...
Click to collapse
s-on
crimedave1987 said:
i cant install no roms every rom i put in stay stuck at boot screen doesnt freeze just hangs on boot what can i do???????:crying::crying::crying:
Click to expand...
Click to collapse
Need more info. What ROM.....S-on, S-Off......what recovery......you know. As much of a description of what you're working with as you can think of. How are you flashing, what had you done right before this happened if anything, etc., etc......
WeekendsR2Short said:
Need more info. What ROM.....S-on, S-Off......what recovery......you know. As much of a description of what you're working with as you can think of. How are you flashing, what had you done right before this happened if anything, etc., etc......
Click to expand...
Click to collapse
i was trying to install rubix senceless 4.0 , cyanogen mod 9 , bulletproof 1.1 and i have cwm recovery 5.5.0.4 and im just flashing all thru cwm Recovery it will install okay then once i reboot bulletproof rom will hang on the t-mobile mytouch 4g slide other roms like rubix and cyanogen will hang at the boot animation screen prob i did something wrong cause when i wanted to install a new fresh rom i thought formatting everything wont damage the phone but here is what i format
on cwm-based recovery5.5.0.4
wipe data/factory reset - passed but with an error E:format_volume: make_extf4fs failed on /dev/block/mmcblk1p2
wipe cache partition - passed
advanced/wipe dalvik cache wiped - passed
wipe battery stats - passed fix permissions - passed
This is why I have cwm v4.0.0.9
Sent from my myTouch 4G Slide using xda premium
K7Cobb said:
This is why I have cwm v4.0.0.9
Sent from my myTouch 4G Slide using xda premium
Click to expand...
Click to collapse
ok whyy?????
will this recovery fix my problem?
crimedave1987 said:
i cant install no roms every rom i put in stay stuck at boot screen doesnt freeze just hangs on boot what can i do???????:crying::crying::crying:
Click to expand...
Click to collapse
damn this long no response is telling me i damaged my phone
crimedave1987 said:
ok whyy?????
will this recovery fix my problem?
Click to expand...
Click to collapse
Have you by any chance tried out CWM 6.0 and decided to go back to 5.5.0.4? Did you extract the "boot.img" file from the ROM & fastboot flash boot boot.img thru ADB AFTER you flashed your ROM.zip file since you are S-On?
---------- Post added at 08:22 AM ---------- Previous post was at 08:17 AM ----------
K7Cobb said:
This is why I have cwm v4.0.0.9
Sent from my myTouch 4G Slide using xda premium
Click to expand...
Click to collapse
You won't be too happy with 4.0.0.9 if you ever let your phone go COMPLETLY dead. It will brick it.
WeekendsR2Short said:
Have you by any chance tried out CWM 6.0 and decided to go back to 5.5.0.4? Did you extract the "boot.img" file from the ROM & fastboot flash boot boot.img thru ADB AFTER you flashed your ROM.zip file since you are S-On?
---------- Post added at 08:22 AM ---------- Previous post was at 08:17 AM ----------
You won't be too happy with 4.0.0.9 if you ever let your phone go COMPLETLY dead. It will brick it.
Click to expand...
Click to collapse
well im using the aio toolkit by hansoon
and the latest cwm is 5.0.2.7 for mt4gs
crimedave1987 said:
well im using the aio toolkit by hansoon
and the latest cwm is 5.0.2.7 for mt4gs
Click to expand...
Click to collapse
Hasoon's toolkit is for unlocking, installing CWM & superuser if my memory serves me though. You can flash your ROMs thu recovery (CWM) but with S-On you will have to extract the "boot.img" file and flash it seperately thru ADB because HBoot will stop an unsigned file it sees as a Radio from flashing if S-On.
There ARE a couple of other versions of CWM....5.5.0.4 & 6.0.0.0. (6.0 has some REAL issues though and has bricked several phones so IF you notice it....don't USE it.)
This will explain it much better to you...... http://forum.xda-developers.com/showthread.php?t=1508556
is there anything i can do to fix this problem cause i really need the phone
okay just now i flashed cwm ver 5.0.2.7 and before when i had it i had the option (mounts and storage menu)
i formatted the cache/data/sd-ext/system is that what i did wrong?
crimedave1987 said:
is there anything i can do to fix this problem cause i really need the phone
okay just now i flashed cwm ver 5.0.2.7 and before when i had it i had the option (mounts and storage menu)
i formatted the cache/data/sd-ext/system is that what i did wrong?
Click to expand...
Click to collapse
If you flashed your ROM and then the boot image after you did that it shouldn't be a problem. Did you read the post above yours and answer those question though? Did you check the link I provided and understand fully what it was talking about? That is VERY important.
WeekendsR2Short said:
If you flashed your ROM and then the boot image after you did that it shouldn't be a problem. Did you read the post above yours and answer those question though? Did you check the link I provided and understand fully what it was talking about? That is VERY important.
Click to expand...
Click to collapse
can you explain step by step cause its not giving me details
i extracted just the boot.img from the rom put it in a new folder then copied the rom.zip file to the same new folder im not doing the command prompt right? please help sorry im a noob
crimedave1987 said:
can you explain step by step cause its not giving me details
i extracted just the boot.img from the rom put it in a new folder then copied the rom.zip file to the same new folder im not doing the command prompt right? please help sorry im a noob
Click to expand...
Click to collapse
do you have adb and fastboot setup?
http://forum.xda-developers.com/showthread.php?t=928370 - adb and fastboot the easy way
mattlowry said:
do you have adb and fastboot setup?
Click to expand...
Click to collapse
i dont think so
WeekendsR2Short said:
This will explain it much better to you...... http://forum.xda-developers.com/showthread.php?t=1508556
Click to expand...
Click to collapse
this is the step by step instructions
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
crimedave1987 said:
i dont think so
Click to expand...
Click to collapse
if you dont you need to do this ASAP because when you are on you have to fastboot .img files to make it work im not too familiar as i am s-off. follow my first link to set up adb and fastboot then go to the link weekend posted. (which is stickied in the development section).
Move your ROM.zip file to the root directory of your phone first. Then put the boot.img file in the root directory of your computer since it's already in the windows path. that's " C:\ " Since you already have Hasoon's toolkit installed we'll use that instead of putting you thru the ADB installation right now for time & simplicity's sake.
Go to Windows Explorer & navigate to the folder you have his toolkit in and copy the name of the folder down EXACTLY. Then you can pull up your command prompt window again. When it initiates it will say C:\ sumpthin....sumpthin...sumpthin. From there type CD\ and it will "change directory" back to C:\ THEN you can type cd\ "whatever you named the folder that has Hasoon's toolkit in it".
That will take you to that folder just like explorer will do. Just let it sit there for a second.
On your phone in Recovery you wipe user data/ factory reset 3 times then you can....
Wipe cache 3 times and toggle down to "Advanced"
That will take you to another screen where you will see "Dalvik Cache"
Wipe that 3 times as well.
Then hit "Go back" & return to the previous screen & select "install zip from SD card"
Once complete leave your phone sitting & still plugged in to the usb
NOW....go back to your computer and type....
reboot bootloader
fastboot flash boot boot.img
fastboot reboot
Once your phone reboots, leave it alone for 5 minutes to let everything settle in and you should be "good to go".
WeekendsR2Short said:
Move your ROM.zip file to the root directory of your phone first. Then put the boot.img file in the root directory of your computer since it's already in the windows path. that's " C:\ " Since you already have Hasoon's toolkit installed we'll use that instead of putting you thru the ADB installation right now for time & simplicity's sake.
QUOTE]
the method for adb i posted is quick and easy. unzip to c: drive and you are done
Click to expand...
Click to collapse
mattlowry said:
this is the step by step instructions
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
if you dont you need to do this ASAP because when you are on you have to fastboot .img files to make it work im not too familiar as i am s-off. follow my first link to set up adb and fastboot then go to the link weekend posted. (which is stickied in the development section).
Click to expand...
Click to collapse
If we can do it like this the first time it may keep him from going into sensory overload. LMAO!
---------- Post added at 09:48 AM ---------- Previous post was at 09:45 AM ----------
mattlowry said:
WeekendsR2Short said:
Move your ROM.zip file to the root directory of your phone first. Then put the boot.img file in the root directory of your computer since it's already in the windows path. that's " C:\ " Since you already have Hasoon's toolkit installed we'll use that instead of putting you thru the ADB installation right now for time & simplicity's sake.
QUOTE]
the method for adb i posted is quick and easy. unzip to c: drive and you are done
Click to expand...
Click to collapse
You're right. It IS very easy. Either way should work but sometimes my mind doesn't go down the easiest path.
Try Matt's way first CrimeDave......
---------- Post added at 10:10 AM ---------- Previous post was at 09:48 AM ----------
mattlowry said:
WeekendsR2Short said:
Move your ROM.zip file to the root directory of your phone first. Then put the boot.img file in the root directory of your computer since it's already in the windows path. that's " C:\ " Since you already have Hasoon's toolkit installed we'll use that instead of putting you thru the ADB installation right now for time & simplicity's sake.
QUOTE]
the method for adb i posted is quick and easy. unzip to c: drive and you are done
Click to expand...
Click to collapse
Mattlowery....I COMPLETLY forgot about the shortcut tool for setting up ADB!! My bad.
CrimeDave, I defer to Matt's way completly. I just now followed his link. I was trying to get you around something you didn't HAVE to get around in the first place. OH well..... LOL
Sorry if I confused you.....
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Related
I was on 1.85, but couldn't get it to root no matter how many times I tried. I updated to 2.2 and was able to successfully root and unlock. I decided to install this rom: http://forum.xda-developers.com/showthread.php?t=1804223. I flashed the boot img from the boot loader. After I flashed it, I tried to reboot into recovery from ADB, but it said the device was not connected. So I went ahead and rebooted the device. I got back to the boot loader and booted into recovery from there. At that point, I mounted the sd card and copied over the zip file of the rom and the gapps. I unmounted the phone and installed the rom and gapps and rebooted. Now im stuck on the Initiating swagger screen. It just sits on this screen and looks like its loading, but nothing happens. Any ideas as to what I have done wrong??
Thanks in advance.
Did you full wipe before flashing? Ie system data cache
a box of kittens said:
Did you full wipe before flashing? Ie system data cache
Click to expand...
Click to collapse
Yes. Would the version of the recovery that I am using make a difference?
Welcome to hboot 1.14 and having to fastboot the boot images from now on
Sent from my HTC One XL
I'm a little confused o where you're getting stuck at ? If its just stuck installing in recovery reboot and reflash
---------- Post added at 06:56 AM ---------- Previous post was at 06:55 AM ----------
954wrecker said:
Welcome to hboot 1.14 and having to fastboot the boot images from now on
Sent from my HTC One XL
Click to expand...
Click to collapse
He did flash bootimg
a box of kittens said:
I'm a little confused o where you're getting stuck at ? If its just stuck installing in recovery reboot and reflash
---------- Post added at 06:56 AM ---------- Previous post was at 06:55 AM ----------
He did flash bootimg
Click to expand...
Click to collapse
The rom said it installed fine, the gapps said it installed fine. I rebooted the phone from recovery. The HTC screen came up and now it's stuck on the screen that has a unicorn and rotating gears and says initiating swagger.
What recovery are you on? You flashed the right boot img correct?
I read he flashed it but he probably screwed it up. It's just more to go wrong when adding more steps 1.09 would have been so simple
Sent from my HTC One XL
a box of kittens said:
What recovery are you on? You flashed the right boot img correct?
Click to expand...
Click to collapse
I flashed 2.4.0.0 version of TWRP. Should I try an older version?
954wrecker said:
he probably screwed it up.
Sent from my HTC One XL
Click to expand...
Click to collapse
Most likely
954wrecker said:
I read he flashed it but he probably screwed it up. It's just more to go wrong when adding more steps 1.09 would have been so simple
Sent from my HTC One XL
Click to expand...
Click to collapse
It said that it flashed, but when I went to reboot the phone into recovery, ADB said it was no longer connected.
Monkeydias said:
It said that it flashed, but when I went to reboot the phone into recovery, ADB said it was no longer connected.
Click to expand...
Click to collapse
You flashed it with fastboot right? Not using an adb command
a box of kittens said:
You flashed it with fastboot right? Not using an adb command
Click to expand...
Click to collapse
No. I used ADB. I guess that is the problem. How do I flash with fastboot?
http://forum.xda-developers.com/attachment.php?attachmentid=1179735&d=1344782533
Download that
2. Put the boot img in that folder
3 get your phone into bootloader than scroll down and select fastboot
4 now open a command prompt within the adb fastboot folder and type "fastboot flash boot boot.img" with out the quotes
Ok I think I have completely screwed myself. I wiped the data and now I cannot mount my sd card.
Monkeydias said:
Ok I think I have completely screwed myself. I wiped the data and now I cannot mount my sd card.
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/showthread.php?t=1942519
How'd you do that?
---------- Post added at 07:35 AM ---------- Previous post was at 07:34 AM ----------
Format sd
exad said:
Try this: http://forum.xda-developers.com/showthread.php?t=1942519
Click to expand...
Click to collapse
Thanks everyone for your help. I found this questions asked before http://forum.xda-developers.com/showthread.php?t=2096912&highlight=cannot+mount+sd+card+in+recovery And followed the instructions on the fourth post and loaded up this rom http://forum.xda-developers.com/showthread.php?t=1868236. Now I am finally up and running. Thank you all very much for being up at this hour and answering my questions!
Np glad you hot everything up and running
Enjoy viperxl it is a great rom
Sent from my HTC One XL
Hey guys,
i flashed Paranoid Android and gApps last night, and it froze during the loading screen. I went back to recovery, and i could not install anything from TWRP. It showed no files, and my phone said there was no OS installed. My computer would not read my phone after this. I am on a Windows XP machine right now because i normally use a Mac but i cant flash images through that.
How do i fix this? and this is my first rom flash, so i would appreciate all the help!
Thanks!
Ill try to post pictures later, but they will be images taken from an iphone. I just want to get back to ParanoidAndroid!
Not enough information. When you plug your phone in does it ask you to format it? Can you still get to twrp? Where did you get the paranoid android from?
Sent from my VENOMized HoxL
area51avenger said:
Not enough information. When you plug your phone in does it ask you to format it? Can you still get to twrp? Where did you get the paranoid android from?
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
I got it from an xda link. I don't have it cuz I'm on my fiancés iPhone four. It can get into twrp but It shows no files when I try to install. And I I plug in to the computer it just makes noise and goes to htc screen with red lettering.
You probably just did this:
http://forum.xda-developers.com/showpost.php?p=38471340&postcount=11
Try the above fix, and come back here, and tell is if it worked or not.
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
experimentation said:
I got it from an xda link.
Click to expand...
Click to collapse
That's amazingly vague. What area51avenger is trying to figure out, is if you tried flashing a ROM meant for the quad core version of the One X (code named Endeavoru), which can be real bad news. If you can figure out what you flashed, and tell us, it would be helpful.
But the fact your screen still comes on is good news. Try to format the SD, and you might have to install TWRP again, but I don't think it will be that hard to get you fixed.
redpoint73 said:
You probably just did this:
http://forum.xda-developers.com/showpost.php?p=38471340&postcount=11
Try the above fix, and come back here, and tell is if it worked or not.
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
That's amazingly vague. What area51avenger is trying to figure out, is if you tried flashing a ROM meant for the quad core version of the One X (code named Endeavoru), which can be real bad news. If you can figure out what you flashed, and tell us, it would be helpful.
But the fact your screen still comes on is good news. Try to format the SD, and you might have to install TWRP again, but I don't think it will be that hard to get you fixed.
Click to expand...
Click to collapse
It was a file named pa-evita.zip from xda somewhere. I am jut trying to figure out how to get twrp to reinstall it. Since nothing shows up now.
experimentation said:
It was a file named pa-evita.zip from xda somewhere.
Click to expand...
Click to collapse
That's good news. Its the proper version of PA for our phone (EVITA) rather than the quad core varian (EVDEAVORU).
experimentation said:
I am jut trying to figure out how to get twrp to reinstall it. Since nothing shows up now.
Click to expand...
Click to collapse
I'd try to reformat SD first, as already mentioned.
If that doesn't work, you can re-install TWRP a couple ways:
1) Flash using fastboot. You will find a fastboot flashable version if you search the TWRP thread (posted by another user). http://forum.xda-developers.com/showthread.php?t=1677447
2) Use the All-In-One Toolkit: http://forum.xda-developers.com/showthread.php?t=1952426
---------- Post added at 10:26 AM ---------- Previous post was at 10:24 AM ----------
And the original cause of all this may be very simple: you may have forgotten to flash boot.img using fastboot, after flashing Paranoid Android. This is mandatory if you are hboot 1.14 or higher, and S-On.
When the phone failed to boot, did you go into hboot and do a factory reset?
redpoint73 said:
That's good news. Its the proper version of PA for our phone (EVITA) rather than the quad core varian (EVDEAVORU).
I'd try to reformat SD first, as already mentioned.
If that doesn't work, you can re-install TWRP a couple ways:
1) Flash using fastboot. You will find a fastboot flashable version if you search the TWRP thread (posted by another user). http://forum.xda-developers.com/showthread.php?t=1677447
2) Use the All-In-One Toolkit: http://forum.xda-developers.com/showthread.php?t=1952426
---------- Post added at 10:26 AM ---------- Previous post was at 10:24 AM ----------
And the original cause of all this may be very simple: you may have forgotten to flash boot.img using fastboot, after flashing Paranoid Android. This is mandatory if you are hboot 1.14 or higher, and S-On.
When the phone failed to boot, did you go into hboot and do a factory reset?
Click to expand...
Click to collapse
Honestly I don't remember. I was rebooting after flashing gapps and I just rebooted nornally, not using flash boot. So after work today ill try all this and report back. Thanks guys. I do love my phone running paranoid!!
experimentation said:
Honestly I don't remember. I was rebooting after flashing gapps and I just rebooted nornally, not using flash boot. So after work today ill try all this and report back. Thanks guys. I do love my phone running paranoid!!
Click to expand...
Click to collapse
Well, update. I am trying to mount my phone to my windows xp machine, and i cannot get it to read. I can get to device manager, but I cannot figure out how to format sd. I know I am probably being a noob about this, I just want this to get solved. Help!
Ok good news. I have it formatted. What is my next step?
experimentation said:
Ok good news. I have it formatted. What is my next step?
Click to expand...
Click to collapse
1. Install TWRP - You can find the lastest version here
Once you've downloaded it put it in your adb/fastboot folder. In your adb/fastboot folder shift + right click > open command window here.
Type, adb reboot bootloader, enter. Now that your phone is in the bootloader and says FASTBOOT USB.
Type in the cmd that is open, fastboot flash recovery openrecovery-twrp-2.4.2.0-evita.img, enter. This should install the newest TWRP recovery.
2. Now make sure that pa-evita.zip and a copy of the boot.img from the zip as well as the gapps.zip for the rom is in your adb/fastboot flolder.
type in cmd, fastboot flash boot boot.img, enter. Now on your phone goto BOOTLOADER and hit the power button, scroll down to RECOVERY and hit the power button again rebooting your phone into TWRP recovery.
type in cmd, adb push pa-evita.zip /sdcard/TRWP, enter
type in cmd, adb push gapps.zip /sdcard/TRWP, enter
3. From TWRP.
Install > navigate to the sdcard/TWRP > pa-evita.zip > Swipe to confirm Flash > Wipe Cache & Dalvik > Back > Home
Install > navigate to the sdcard/TWRP > gapps.zip > Swipe to confirm Flash > Wipe Cache & Dalvik > Back > Reboot System.
All the bold adb and fastboot commands are copy paste-able but make sure the file names are correct
Okay, so I decided to do something stupid and forget to backup my HTC One S while rooting. I installed CM10, and it got stuck in a bootloop, so stupid me decided to also do a factory reset and basically delete everything I needed to get out of it. I've tried numerous things, including ADB sideloading a ROM, but whenever I do that, it also gets stuck in a boot loop. I have no idea how to use RUU's, and if anybody could help me to fix my phone, that'd be really really helpful. I'm also kindof a n00b towards this stuff, so step-by-step instructions would be much appriciated Thanks.
~MuZiiX
Is your device S-off and do you have supercid?
Then I believe you can just use any RUU file for your phone to get it back to stock.
A Ruu is basically a file that installs the stock ROM onto your device.
Find the Ruu you need here: http://forum.xda-developers.com/showthread.php?t=2094414
Just download it, connect your phone with a USB and run the Ruu file ( it's an .exe ) on your PC.
I hope this helps. Don't just listen to my advice. I'd wait till someone confirms my advice to be safe/correct. I'm still a bit of a noob after all who's trying to help and learn.
CuzCrostyPwns said:
Is your device S-off and do you have supercid?
Then I believe you can just use any RUU file for your phone to get it back to stock.
A Ruu is basically a file that installs the stock ROM onto your device.
Find the Ruu you need here: http://forum.xda-developers.com/showthread.php?t=2094414
Just download it, connect your phone with a USB and run the Ruu file ( it's an .exe ) on your PC.
I hope this helps. Don't just listen to my advice. I'd wait till someone confirms my advice to be safe/correct. I'm still a bit of a noob after all who's trying to help and learn.
Click to expand...
Click to collapse
I think my device is s-off...i used the HTC One S all in one toolkit, and I have no idea what supercid is :s I've tried a couple RUU's before (don't know if i used them correctly, but i did relock the bootloader when i did it) but none of them helped. It just stayed at a black screen with "htc" in the middle. No error triangles or anything.
Did you run the RUU files like you would run an .exe file on your pc with your phone connected by USB?
I'm not sure how your PC will recognize your phone when you're not in fastboot (bootloader).. Or am I misunderstanding something.
Wait. Can you get into your recovery? Do you still have that installed?
CuzCrostyPwns said:
Did you run the RUU files like you would run an .exe file on your pc with your phone connected by USB?
I'm not sure how your PC will recognize your phone when you're not in fastboot (bootloader).. Or am I misunderstanding something.
Wait. Can you get into your recovery? Do you still have that installed?
Click to expand...
Click to collapse
Yeah, the RUU's were .exe's with my phone connected through USB. I can get into recovery, I have CWM installed.
I'm not sure if CWM has this option, but maybe you can mount your phone through recovery.
Then just place a new ROM on your SD card and flash it.
CuzCrostyPwns said:
I'm not sure if CWM has this option, but maybe you can mount your phone through recovery.
Then just place a new ROM on your SD card and flash it.
Click to expand...
Click to collapse
Well thats what I've been trying to do with the ADB sideloading, because it wont let me mount my sd card. It just says 'ERROR MOUNTING SD CARD" and when I've tryed flashing a new ROM from ADB sideloading, it just gets stuck in a bootloop again.
My best bet is to run the RUU file.
To know which one is the correct one is to see which RUU title fits your phone's Stock 'settings' the best (ie: provider, country, android version)
---------- Post added at 08:42 PM ---------- Previous post was at 08:20 PM ----------
Oh and this thread should be moved to the Q&A forum I just realized
CuzCrostyPwns said:
My best bet is to run the RUU file.
To know which one is the correct one is to see which RUU title fits your phone's Stock 'settings' the best (ie: provider, country, android version)
---------- Post added at 08:42 PM ---------- Previous post was at 08:20 PM ----------
Oh and this thread should be moved to the Q&A forum I just realized
Click to expand...
Click to collapse
I've tried running multiple RUU files, and I have no idea what one to use. The phone when I got it was unlocked, and the android version was ICS I'm pretty sure.
I dunno how to find my stock settings because I cant get past the loading screen.
Did you try flashing the boot.IMG from adb. It sounds to me, that since every ROM you try results in a bootloop that you did not flash the boot.IMG
Sent from my HTC One S using xda app-developers app
did you flash boot.img? most of roms will bootloop without it
Roundtableprez said:
Did you try flashing the boot.IMG from adb. It sounds to me, that since every ROM you try results in a bootloop that you did not flash the boot.IMG
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Pardon my stupidity, but what boot.IMG would I flash? As I stated before, I'm not that good at this kind of stuff :s
MuZiiX said:
Pardon my stupidity, but what boot.IMG would I flash? As I stated before, I'm not that good at this kind of stuff :s
Click to expand...
Click to collapse
the boot.img is located in the zip you downloaded from get.cm
NQNH said:
the boot.img is located in the zip you downloaded from get.cm
Click to expand...
Click to collapse
So what command would I use while flashing the boot.IMG file? (again sorry for not getting this, I just wanna get my phone working again)
MuZiiX said:
Pardon my stupidity, but what boot.IMG would I flash? As I stated before, I'm not that good at this kind of stuff :s
Click to expand...
Click to collapse
You failed to follow the instructions to install the rom. That is why you phone wouldn't boot.
Download or build from source
Download gapps
wipe unless you're upgrading from an earlier CM10 ROM
flash rom in recovery
flash gapps in recovery
unless you have s-off fastboot flash boot boot.img
Click to expand...
Click to collapse
Take your CM10 Rom and open it up. Inside you'll find a file called boot.img. Copy that file to the location where you installed the toolkit. Place it in the data folder there. Then open the toolkit and press the "flash a kernel" button. Just follow the instructions to flash the file.
You phone should now be fixed just reboot it.
Next time, make sure you read the instructions and if you aren't sure what's going don't move forward. Or use the search button. Finally, questions like this one go in the Q&A forum. :good:
dc211 said:
You failed to follow the instructions to install the rom. That is why you phone wouldn't boot.
Take your CM10 Rom and open it up. Inside you'll find a file called boot.img. Copy that file to the location where you installed the toolkit. Place it in the data folder there. Then open the toolkit and press the "flash a kernel" button. Just follow the instructions to flash the file.
You phone should now be fixed just reboot it.
Next time, make sure you read the instructions and if you aren't sure what's going don't move forward. Or use the search button. Finally, questions like this one go in the Q&A forum. :good:
Click to expand...
Click to collapse
Thanks, I'll try that and see how it goes. I totally forgot to do a backup, and I now know that I should do one...and sorry, I'm kinda new to the forum and went here as a last resort.
MuZiiX said:
Thanks, I'll try that and see how it goes. I totally forgot to do a backup, and I now know that I should do one...and sorry, I'm kinda new to the forum and went here as a last resort.
Click to expand...
Click to collapse
It not really a big deal. Your problem is the most common one we see in Q&A. Also, once you finish flashing the boot.img keep in mind that CM10 can take a few minutes to boot the first time.
Also, just a heads up while the toolkits are helpful learning the command yourself actually lets do you a lot more things a lot faster.
heres how to do it using fastboot:
Http://forum.xda-developers.com/showthread.php?t=1752270
Sent from my One S using xda app-developers app
CuzCrostyPwns said:
heres how to do it using fastboot:
Http://forum.xda-developers.com/showthread.php?t=1752270
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Thanks for the quick responses guys, I'm going to try that once I get home. Do I absolutely need USB debugging enabled? Because mine Isn't :s
MuZiiX said:
Thanks for the quick responses guys, I'm going to try that once I get home. Do I absolutely need USB debugging enabled? Because mine Isn't :s
Click to expand...
Click to collapse
Nope, just gotta do it one of the three ways mentioned. If debugging isn't enabled use option 1.
This can either be done via
1 powering off and keeping volume up & the power-button pressed
2 the extended power-menu (If your ROM has it, just select "reboot" & then "bootloader")
3 via adb, connect your phone with the pc, make sure it says "USB debugging connected", go to Android/platform-tools/ & then press shift while you perform a right click with the mouse, then choose "open prompt here", type
Click to expand...
Click to collapse
This is the hboot ONLY from the latest OTA (4.4.3/2.21.605.2) update 9/11/14 with red warning text removed!
flash from bootloader via fastboot commands:
fastboot oem rebootRUU
fastboot flash zip VZW_2.21.605.2_NoRedText_hboot.zip
fastboot reboot
*profit*
https://drive.google.com/file/d/0B2yDp308YPB8YlJTLTN0QW84WG8/edit?usp=sharing
hungsolow said:
This is the hboot ONLY from the latest OTA (4.4.3/2.21.605.2) update 9/11/14 with red warning text removed!
flash from bootloader via fastboot commands:
fastboot oem rebootRUU
fastboot flash zip VZW_2.21.605.2_NoRedText_hboot.zip
fastboot reboot
*profit*
https://drive.google.com/file/d/0B2yDp308YPB8YlJTLTN0QW84WG8/edit?usp=sharing
Click to expand...
Click to collapse
Thanks man!
So this is okay to flash if I am running Venom 2.40?
can I rename this as 0P6BIMG.zip and flash it through hboot?
when I tell fastboot to flash the file.. it says error: cannot open (filename)
Bump...
Any ideas?
hungsolow said:
This is the hboot ONLY from the latest OTA (4.4.3/2.21.605.2) update 9/11/14 with red warning text removed!
flash from bootloader via fastboot commands:
fastboot oem rebootRUU
fastboot flash zip VZW_2.21.605.2_NoRedText_hboot.zip
fastboot reboot
*profit*
https://drive.google.com/file/d/0B2yDp308YPB8YlJTLTN0QW84WG8/edit?usp=sharing
Click to expand...
Click to collapse
good looks
---------- Post added at 06:24 PM ---------- Previous post was at 06:22 PM ----------
OdinValknir said:
Bump...
Any ideas?
Click to expand...
Click to collapse
you can always try renaming to something easier, but it looks right, i renamed mine so its not a mess to type
OdinValknir said:
when I tell fastboot to flash the file.. it says error: cannot open (filename)
Click to expand...
Click to collapse
Zip file in the same folder as fastboot.exe? If not there's ur problem lol
---------- Post added at 05:51 PM ---------- Previous post was at 05:49 PM ----------
Side note: Drive is the crappiest place to host a file, ever. F*ck drive.
Ah.. I was not aware the zip had to be in the same file... See I knew there was something missing... Now I know what the ???? Are before profit lol
Sent from my HTC6525LVW using XDA Free mobile app
OdinValknir said:
when I tell fastboot to flash the file.. it says error: cannot open (filename)
Click to expand...
Click to collapse
it can't find the file.
1 or 2 things is going on here.
1) you have the file named differently and there was a mis-type thus, not finding the file to fastboot flash.
2) you do not have the file in the same folder as your CMD prompt.
Hmmm ok so put file into folder where fastboot etc is... Still no joy
Still getting error cannot open
EDIT: ohwell.. having the red text didnt bother me too much before.. I guess until i can figure this out i will deal with it some more
Edit: figured it out... Was opening the cmd from the start menu... Had to open from the platform tools folder..
Tnx for help
Works great.
Thanks
OdinValknir said:
Hmmm ok so put file into folder where fastboot etc is... Still no joy
Still getting error cannot open
EDIT: ohwell.. having the red text didnt bother me too much before.. I guess until i can figure this out i will deal with it some more
Click to expand...
Click to collapse
it's your user error, the OP did a great job making this.
I suggest doing some reading on fastboot, adb, etc....
this is like 1st grade stuff for rooting, and can cause serious issues if you don't know what you're doing and I def wouldn't want to see that. ESP with hboot, flashing hboot is dangerous as it is.
here is what I do..
I have a folder name "ADB"
I have this in my C; drive
I suggest doing the same.
This you put all your files needed for adb, fastboot, etc.
you put the file you download from this threads OP into said ADB folder.
Go to the top of the folder like the internet bar, type in CMD
and it will open a CMD prompt in the folder, and I don't see how it wouldn't work.
I attached my ADB folder for you, if you want to play with it..
andybones said:
it's your user error, the OP did a great job making this.
I suggest doing some reading on fastboot, adb, etc....
this is like 1st grade stuff for rooting, and can cause serious issues if you don't know what you're doing and I def wouldn't want to see that. ESP with hboot....
Click to expand...
Click to collapse
No I finally got it... Just had to open my cmd prompt from platform tools folder.... I've only messed w this stuff once back when I first got the phone... I'm just relearning is all
OdinValknir said:
No I finally got it... Just had to open my cmd prompt from platform tools folder.... I've only messed w this stuff once back when I first got the phone... I'm just relearning is all
Click to expand...
Click to collapse
I hope my post didn't come off rude, that was not my intention. (but yes it was user error, )
I just wouldn't want to see you damage your device.
Flashing hboot.img can be dangerous
(Also, like I said, 1 or 2 things.. the file wasn't in the correct folder, or was named wrong. it was in the correct folder, you just weren't opening the CMD prompt for that folder)
Always good learning without hurting phone.
Thanks to the OP for his efforts. :good:
For those wanting the Faux Locked version, I have both the No Red Text and Faux Locked versions made and posted in my m8 hboot thread: HERE
santod040 said:
Thanks to the OP for his efforts. :good:
For those wanting the Faux Locked version, I have both the No Red Text and Faux Locked versions made and posted in my m8 hboot thread: HERE
Click to expand...
Click to collapse
the Faux Hboot worked like a charm. I would have hit the thanks button but I reached my max of 8 thanks for the day.
Is there any way to make this so I can put it on my sd card and flash it with hboot
sent from my thumbs
jaymccoubrey said:
Is there any way to make this so I can put it on my sd card and flash it with hboot
sent from my thumbs
Click to expand...
Click to collapse
Yeah you can do it just like the firmware method.
Rename to 0P6BIMG.zip and put it on root of SD card.
Then boot to hboot and follow the prompts to update.
Irish Cream said:
So this is okay to flash if I am running Venom 2.40?
Click to expand...
Click to collapse
I don't think anyone responded to you, but it's not the ROM/version you are running, but the firmware. You will want to download/flash the 4.4.3 firmware file first, then this file. Here's a link for the new firmware: http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-3-s-off-onlynewest-t2873144
---------- Post added at 04:39 PM ---------- Previous post was at 04:36 PM ----------
BTW, thank you OP for this... worked flawlessly!
I have tried TWRP (twrp.me/devices/googlepixel.html) and the Unified Android Toolkit (skipsoft.net/download/uat-v156/) to root the Pixel I bought directly from Google. With TWRP, I cannot see the .zip I downloaded (the phone is encrypted and /sdcard/* are all gibberish names; I'm never prompted for a decrypting password when booting for recovery) and with the Toolkit I end up in a reboot loop (I've tried twice with the same results).
I'm surprised that the Toolkit thinks my build is "Verizon" (NDE63X). I'm not sure if that matters.
Thoughts? Pointers? Diagnostics? TIA.
go get the new alpah2 of twrp.
---------- Post added at 01:51 PM ---------- Previous post was at 01:48 PM ----------
Save v4 root on sd. Save alpha 2 img on desktop, and .zip on sd on phone. fastboot img, enter pin or pattern, then flash alpha2 zip. restart in recovery, flash v4 root. Done.
computercarl said:
go get the new alpah2 of twrp.
---------- Post added at 01:51 PM ---------- Previous post was at 01:48 PM ----------
Save v4 root on sd. Save alpha 2 img on desktop, and .zip on sd on phone. fastboot img, enter pin or pattern, then flash alpha2 zip. restart in recovery, flash v4 root. Done.
Click to expand...
Click to collapse
Thanks. That gets me further. I put twrp-pixel-installer-sailfish-3.0.2-0-alpha2.zip and SR3-SuperSU-v2.78-SR3-20161103171345.zip on the SD card. I booted with twrp-3.0.2-0-alpha2-fastboot-sailfish.img and I could see the zips. I installed alpha2.zip, reboooted, installed SuperSU, rebooted. I don't see SuperSU in my app list. I'm missing something. I'm not sure what you mean by "v4 root".
ChrisNelsonPE said:
Thanks. That gets me further. I put twrp-pixel-installer-sailfish-3.0.2-0-alpha2.zip and SR3-SuperSU-v2.78-SR3-20161103171345.zip on the SD card. I booted with twrp-3.0.2-0-alpha2-fastboot-sailfish.img and I could see the zips. I installed alpha2.zip, reboooted, installed SuperSU, rebooted. I don't see SuperSU in my app list. I'm missing something. I'm not sure what you mean by "v4 root".
Click to expand...
Click to collapse
Since you have to temp boot twrp, I just use adb sideload to flash the twrp and SuperSU zips.
I reflash stock boot img
Boot into twrp from fast boot
Sideload twrp zip
Reboot recovery
Sideload supersu sr4 zip
GeekMcLeod said:
Since you have to temp boot twrp, I just use adb sideload to flash the twrp and SuperSU zips.
...
Sideload supersu sr4 zip
Click to expand...
Click to collapse
I found download.chainfire.eu/1013/SuperSU/SR4-SuperSU-v2.78-SR4-20161115184928.zip. Trying that shortly.
ChrisNelsonPE said:
I found download.chainfire.eu/1013/SuperSU/SR4-SuperSU-v2.78-SR4-20161115184928.zip. Trying that shortly.
Click to expand...
Click to collapse
Just let me know if you need any help. I'd happily help you get your phone rooted.
GeekMcLeod said:
Just let me know if you need any help. I'd happily help you get your phone rooted.
Click to expand...
Click to collapse
SU4 did it for me.
And a shout out to the Helium app for moving my data, even without root. Best $5 I spent this year!
ChrisNelsonPE said:
SU4 did it for me.
And a shout out to the Helium app for moving my data, even without root. Best $5 I spent this year!
Click to expand...
Click to collapse
I'm curious, I think I have ADB set up correctly but I have never had any luck I. Using it before ( mainly because of ADB language and commands to do what I want to do). Is there a guide that tells people like myself what to type and where to put files? Man that would be nice .
quinejh said:
I'm curious, I think I have ADB set up correctly but I have never had any luck I. Using it before ( mainly because of ADB language and commands to do what I want to do). Is there a guide that tells people like myself what to type and where to put files? Man that would be nice .
Click to expand...
Click to collapse
I highly recommend that if you're going to be doing stuff like this to your phone you get familiar with ADB and fastboot otherwise you're just asking for trouble. Each of the threads on custom recovery and root have the links and instructions including commands, read everything twice since you're new to this and I mean everything.