Develop Bugs

boot loop after flashing latest manhatten project rom

Ok have been running foxhound 1.1,tried a couple of other roms,kernels,etc and no problem. But now all of a sudden tried to flash manhatten and endless boot loop. I have tried to wipe from cwm several times but no luck. I dont want to lose my pictures from virtual sdcard. I have no access to adb but cwm and fastboot of course. I'm using linux so is there any way to use fastboot to erase everything but keep virtual sdcard. If that can you point me to instructions on how to from fastboot. I have the GSM version

Did you even bother installing another ROM prior to freaking out?
Wipe data
Wipe cache
Wipe dalvik
Format System
install ROM from sd card (please don't tell me you only kept one ROM on there)
your phone should now boot

Samsuck said:
Did you even bother installing another ROM prior to freaking out?
Wipe data
Wipe cache
Wipe dalvik
Format System
install ROM from sd card (please don't tell me you only kept one ROM on there)
your phone should now boot
Click to expand...
Click to collapse
I have wiped several times reflashed foxhound 1.1 even reinstalled cwm recovery touch version but no go. Not sure what happened but why would going back to stock fix it??? I dont want to lose my pictures but if that is the only way. What the hell is causing the boot loop????

tman7510 said:
I have wiped several times reflashed foxhound 1.1 even reinstalled cwm recovery touch version but no go. Not sure what happened but why would going back to stock fix it??? I dont want to lose my pictures but if that is the only way. What the hell is causing the boot loop????
Click to expand...
Click to collapse
You keep saying that you wiped but you're being vague.
Can you specify if you have WIPED DATA, CACHE, DALVIK, FORMATTED SYSTEM, and FORMATTED CAHCHE? If you have not, do that and THEN re-flash Foxhound
This does NOT wipe your internal SD card.

9 out of 10 times its human error when bootloop shows up..... go to the thread of the rom you flashing maybe you missed a important step
Verstuurd van mijn Galaxy Nexus met Tapatalk

Samsuck said:
You keep saying that you wiped but you're being vague.
Can you specify if you have WIPED DATA, CACHE, DALVIK, FORMATTED SYSTEM, and FORMATTED CAHCHE? If you have not, do that and THEN re-flash Foxhound
This does NOT wipe your internal SD card.
Click to expand...
Click to collapse
I have formatted everything but davik cache but when I do that I get" E:unknown volume for path /sd-ext Dalvik Cache Wiped " then reflash foxhound and now I am back to the boot loop all I get is Google with unlock symbol at the bottom and it just loops. There has to be a way to get info off my virtual sdcard..I dont care how hard it is

demon2112 said:
9 out of 10 times its human error when bootloop shows up..... go to the thread of the rom you flashing maybe you missed a important step
Verstuurd van mijn Galaxy Nexus met Tapatalk
Click to expand...
Click to collapse
I didn't use the gapps but the rom should still boot without that gapp version. Also shouldn't I be able to flash another rom without having this issue??? All I did was flash from clockworkmod. maybe the zip file I downloaded got corrupted but I am unable to fix the problem. I had installed the manhatten rom yesterday but went back to foxhound because lack of performance/undervolting settings that apperently are on the rom. just want it to work again..I'm unable to use adb becasue it wont boot. all I have is fastboot and cwm recovery

That error is normal as we don't have an "sd-ext" .
Are you wiping in the correct order? You're wiping all of that first, and then installing ROM correct?
Do you have a back up?
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
If you have ADB installed, or can get to a computer with it.
You can pull your files from the SD card as our fake SD card is actually /DATA/MEDIA

Samsuck said:
That error is normal as we don't have an "sd-ext" .
Are you wiping in the correct order? You're wiping all of that first, and then installing ROM correct?
Do you have a back up?
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
If you have ADB installed, or can get to a computer with it.
You can pull your files from the SD card as our fake SD card is actually /DATA/MEDIA
Click to expand...
Click to collapse
how do I get adb to work if the phone will not boot into android???in fastboot mode if I type adb devices it lists nothing?? if I try adb in cwm recovery I get a bunch of questionmarks followed by no permissions....this is in linux. I can use windows if the toolkit can use adb while in clockworkmod recovery. I'll need detailed instructions becasue I have wiped in every order imaginable and nothing but boot loop???

"adb devices" will return nothing in fastboot.
The correct command is "fastboot devices"

tman7510 said:
how do I get adb to work if the phone will not boot into android???in fastboot mode if I type adb devices it lists nothing?? if I try adb in cwm recovery I get a bunch of questionmarks followed by no permissions....this is in linux. I can use windows if the toolkit can use adb while in clockworkmod recovery. I'll need detailed instructions becasue I have wiped in every order imaginable and nothing but boot loop???
Click to expand...
Click to collapse
You can use ADB in CWM Recovery. I do it all the time in Windows.

El Daddy said:
"adb devices" will return nothing in fastboot.
The correct command is "fastboot devices"
Click to expand...
Click to collapse
yes I know and I have no problem using what little I know of fastboot commands but is there a way to use fastboot to copy my virtual sdcard to my pc?????

Be sure to "mount data" in Recovery
adb shell
type su for superuser.
then ls to list the dirs
and cd to change
You might have to pull files one by one. I'm not sure if there's a way to pull the entire contents of it.

Samsuck said:
You can use ADB in CWM Recovery. I do it all the time in Windows.
Click to expand...
Click to collapse
so how do I mount or do I just use the toolkit because it seems to tell me in bright green letters that I must be in android to use adb?? I guess that is a limitation of the toolkit. I'll try installing the android sdk to windows and see how that works. I will let you know how it goes thank you. Also do you have a link on how to restore it to a stock rom but not have to go through the whole rooting and unlocking process??? Thank you again for your help so far!!

Actually, do this.
Once you have the drivers installed for Windows, and your phone is being recognized "adb devices"
Run
adb pull /data/media/DCIM C:Urname\example\blah
Replace the C:Urname\example\blah with an actual directory of the Windows PC
It might take some time but that should drag your pictures and stuff.

Here's the link with instructions to return to stock. http://forum.xda-developers.com/showthread.php?t=1366806

tman7510 said:
so how do I mount or do I just use the toolkit because it seems to tell me in bright green letters that I must be in android to use adb?? I guess that is a limitation of the toolkit. I'll try installing the android sdk to windows and see how that works. I will let you know how it goes thank you. Also do you have a link on how to restore it to a stock rom but not have to go through the whole rooting and unlocking process??? Thank you again for your help so far!!
Click to expand...
Click to collapse
Hit, Install SDK on the toolkit. It will do it very quick and easy for you.
Since the SD Card on our Nexus is actually /data/media, like I said earlier, just mount data.

Gnex toolkit is a great tool. I'm wondering why I have permission issues with adb in cwm recovery in Linux. not complaining but I wish there was a kit like that for us linux users

any body know why in cwm recovery if run ./adb device in linux you get
devices listed
?????????? no permissions
any linux users out there? I'm saving my files thanks to a windows program gnex tookkit by mskip.
Special thanks to Samsuck for all his help and the rest of the forum

[Q] [VERY STRANGE] Wipe data doesn't work anymore!

Hi everybody,
I'm getting into the new AOKP Milestone 4 from the Codename 1.5.0 - so I downloaded the files and get recovery (clockwork 5.5.0.2) to make the wipes and flash the new rom and gapps... the usual routine.
Wipe data - Wipe Cache - Wipe Dalvik - Flash AOKP - FLASH GAPPS - REBOOT
1st strange thing after that: the Old Franco Kernel bootlogo. And in stuck, obv.
Why the Franco bootlogo? Bah, re-wipe everything and go on...
Nothing, stuck on Franco. So I decided to re.wipe everything again and re install the Codename android, 1.5.0 - the same wich i was coming from - to get the phone work for tomorrow. And here we go for the biggest surprise.
EVERYTHING IS HOW I LEFT BEFORE THE WIPES WHEN I WAS ON CODENAME!!!!!
Same routine, flashed Codename and reboot. Franco logo and then no configuration wizard, no backups.. everything was EXACTLY like how i left before the first attempt!!! My apps, my homescreen, even my login account, like i have never attempt any wipe or flash!!!!
IT DOESN'T WIPE ANYTHING, ANYMORE!
I'm getting mad.. tried this ten times. It's like nothing is getting wiped!
P.s: clockwork is correctly installed.. i've tried TONS of roms on my gnexus, everything has ALWAYS worked fine. No errors during wiping, usuals script "wiping /data .... wiping /cache etc.." until "DONE". No error flashing the AOKP.
Help please..
Fab

Hey there,
mike, the dev from Android Revolution HD, has a super wipe script in his thread, on the first page, might want to try that one.
It works like flashing a ROM
-Syn

You are not wiping correctly. You are having problems because the system and boot partitions were not wiped at all....
Sent from my Galaxy Nexus using xda premium

SynFox said:
Hey there,
mike, the dev from Android Revolution HD, has a super wipe script in his thread, on the first page, might want to try that one.
It works like flashing a ROM
-Syn
Click to expand...
Click to collapse
Already tried. Same results, it ends successfully the superwipe string.. and then no wipe at all!

adb reboot bootloader
fastboot -w (might wipe SD card)
or
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot update update.zip (for installing the rom)

Ok new infos.
From the log file the /data wipe seems to be undone due to the "filesystem is read only".
Any ideas?

Stupid question... but maybe check if the device is still rooted and unlocked correctly?
Maybe something messed up there...

these are signs that the internal hdd is getting screwed up... like the partition values... its a known issue for all samsung devices. the i9000 had it, the nexus s had it. they even have a lot of threads out there reporting issues abt it but no fix till now. i even had it with my nexus s (which is now a paperweight)
some fixed it with a simple wipe using oem lock n unlock, others fastboot wipe....
the most common symptom is that you can see a lot of files on your phone, but can neither delete them nor add anyting to the sdcard.

As anton2009 said, you should try wiping all the partitions, then reflash CWM, then flash your ROM/kernel.
Reboot into fastboot and type the following:
fastboot erase boot
fastboot erase system
fastboot erase recovery
fastboot erase userdata Note this will wipe/sdcard
fastboot erase cache
Then flash CWM and then ROM/kernel.
Sent from my Galaxy Nexus using Tapatalk

I am also having the same issue. However I just reflashed a bunch of roms and even though all my data is still there everything seems to be working fine.

Cptsamir said:
I am also having the same issue. However I just reflashed a bunch of roms and even though all my data is still there everything seems to be working fine.
Click to expand...
Click to collapse
Guys, all of your data is stored on the userdata partition. Most ROMs I don't think flash that partition, so all the data still remains. As well, I don't think every ROM includes a kernel, so the boot partition is not erase either. Wiping in CWM does not wipe /sdcard (which is actually located on the userdata partition as /data/media).
Use what I had posted 2 posts up and it will certainly wipe.

efrant said:
Guys, all of your data is stored on the userdata partition. Most ROMs I don't think flash that partition, so all the data still remains. As well, I don't think every ROM includes a kernel, so the boot partition is not erase either. Wiping in CWM does not wipe /sdcard (which is actually located on the userdata partition as /data/media).
Use what I had posted 2 posts up and it will certainly wipe.
Click to expand...
Click to collapse
I also think your solution will work well.
My only question is about new rom flashing: erasing ALL datas even in the /sdcard how will I be able to flash new roms if there will be nothing more on the phone? Where will i get'em?
Will I need to flash again even the CWM?
Sorry for the stupid question..

fab2disco said:
I also think your solution will work well.
My only question is about new rom flashing: erasing ALL datas even in the /sdcard how will I be able to flash new roms if there will be nothing more on the phone? Where will i get'em?
Will I need to flash again even the CWM?
Sorry for the stupid question..
Click to expand...
Click to collapse
You can still wipe userdata, boot into Android (obviously you can't do this if you wipe system), and download a rom from there. Otherwise you can download a rom onto your computer and then:
adb push /where/your/file/is/rom.zip /data/media/download
This will put the file from your computer to your download folder in your SD card. I'd recommend pulling any necessary files before you wipe userdata (such as music, pictures, etc) or you can pull the whole SD card (adb pull /data/media) and then cherry pick what you want to add back later.

SOLVED.
Wiped all with fastboot, pushed new rom with adb push and flash it.
Just to feel relaxed installed a couple of apps, gone back in recovery and tried to wipe data/cache/dalvick then re-flashed AOKP, everything is now working fine, the wipe erase all app and userdata now.
Hope this won't happen anymore.. thank you all..

fab2disco said:
SOLVED.
Wiped all with fastboot, pushed new rom with adb push and flash it.
Just to feel relaxed installed a couple of apps, gone back in recovery and tried to wipe data/cache/dalvick then re-flashed AOKP, everything is now working fine, the wipe erase all app and userdata now.
Hope this won't happen anymore.. thank you all..
Click to expand...
Click to collapse
Good to hear! Glad everything worked out for you. You can put [Solved] in the thread title so other people with the same problem will know what to do.

anton2009 said:
Good to hear! Glad everything worked out for you. You can put [Solved] in the thread title so other people with the same problem will know what to do.
Click to expand...
Click to collapse
I feel sooooo newbie, but.. how can I do that?

Backing up and restoring /sdcard is very time-consuming and usually unnecessary in these situations. It only takes a minute to fix the filesystem errors on /data and then you can wipe data as normal (in CWM, no need to use fastboot which also erases /sdcard). Just boot into CWM and in an adb shell:
Code:
e2fsck /dev/block/mmcblk0p12
Answer 'y' to everything if prompted. Done.

Jimmy Flip said:
Backing up and restoring /sdcard is very time-consuming and usually unnecessary in these situations. It only takes a minute to fix the filesystem errors on /data and then you can wipe data as normal (in CWM, no need to use fastboot which also erases /sdcard). Just boot into CWM and in an adb shell:
Code:
e2fsck /dev/block/mmcblk0p12
Answer 'y' to everything if prompted. Done.
Click to expand...
Click to collapse
Confirmed working.. Thanks a lot for your help. You are a life saver.

Help
I can't delete anything, i can't flash anything..
everything stay where it is, wipe or format doesn't work.. and my phone is stucked on infinite reboot..
please help!

Dobie999 said:
I can't delete anything, i can't flash anything..
everything stay where it is, wipe or format doesn't work.. and my phone is stucked on infinite reboot..
please help!
Click to expand...
Click to collapse
Try to lock the bootloder and if it fails, your phone is bricked...the emmc is broken.. try warranty

[Q] free beer if you fix my one x!

Hi, if you can help me unbrick my phone I'll buy you a beer (or three!)
I have an htc one x which i managed to unlock the bootloader via htcdev as in various tutorials....
I was too lazy to take a backup
I then tried to install cyanogenmod 10 using cwm recovery.... (by flashing a zip file i had downloaded - one of the nightly builds)
I wiped the cache etc in cwm
it got stuck in a boot loop i think as it got to the spinning cyanogen logo then nothing happened...
I've tried to get it working again using lots of different methods - i downloaded some RUU exes which failed because they said they weren't the correct ROM (even though they should be right) - then i read a tutorial about how to use fastboot to flash system.img onto the phone but it fails giving error code 00000006
I can't push any zip files to the phone using ADB as I get permission denied errors
I've also tried to use fastboot to flash various recoveries but I can't apply any zips because I can't get them onto the phone in the first place
I've also flashed various recovery.img files but when they load, I get a red triangle after a few seconds
If someone could tell me how to use ADB to push a zip file to the phone I'd be really grateful - have tried everything but keep getting permission denied errors
Thanks
(oh and if you manage to help me fix it I WILL buy you a beer... or 3)

oh and ....
ALSO I've googled the problem and tried all of the options I can find which could help - please don't just send me a link to a page because i can guarantee I've probably already tried the solution and failed. When I boot into recovery, I can't use adb push to send files to the phone because it says it's not connected even if i try the option for mount data, or mount storage - the only time windows seems to manage to aknowledge it's existence is on the fastboot screen -
lazclark said:
Hi, if you can help me unbrick my phone I'll buy you a beer (or three!)
I have an htc one x which i managed to unlock the bootloader via htcdev as in various tutorials....
I was too lazy to take a backup
I then tried to install cyanogenmod 10 using cwm recovery.... (by flashing a zip file i had downloaded - one of the nightly builds)
I wiped the cache etc in cwm
it got stuck in a boot loop i think as it got to the spinning cyanogen logo then nothing happened...
I've tried to get it working again using lots of different methods - i downloaded some RUU exes which failed because they said they weren't the correct ROM (even though they should be right) - then i read a tutorial about how to use fastboot to flash system.img onto the phone but it fails giving error code 00000006
I can't push any zip files to the phone using ADB as I get permission denied errors
I've also tried to use fastboot to flash various recoveries but I can't apply any zips because I can't get them onto the phone in the first place
I've also flashed various recovery.img files but when they load, I get a red triangle after a few seconds
If someone could tell me how to use ADB to push a zip file to the phone I'd be really grateful - have tried everything but keep getting permission denied errors
Thanks
(oh and if you manage to help me fix it I WILL buy you a beer... or 3)
Click to expand...
Click to collapse

Have you flashed the cm boot IMG and then erased fastboot cache?
fastboot flash boot pathtoboot.IMG
fastboot erase cache
For the RUU to work you need to have stock recovery and a relocked boot loader.
if you download the latest clockworkmod mounting as USB storage is fixed.
Sent from my HTC One X using xda app-developers app

thanks!
wow that was a quick reply - yes I've flashed the cm boot img and erased the cache - which version of CWM is the latest? - When you say mounting as USB storage is fixed, do you mean that windows will be able to see the device and write files to it?
(I'm really sorry for asking these questions - the problem is that I know a BIT about how android works but not as much as I should do)
treebill said:
Have you flashed the cm boot IMG and then erased fastboot cache?
fastboot flash boot pathtoboot.IMG
fastboot erase cache
For the RUU to work you need to have stock recovery and a relocked boot loader.
if you download the latest clockworkmod mounting as USB storage is fixed.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse

Are you absolutely sure you flashed the boot.img from the rom.zip using fastboot on your computer? Because it really sounds like you didn't

This is a thread I made and it should provide you with a solution if not a starting point if you insist on CM10.
http://forum.xda-developers.com/showthread.php?t=1900127
Good luck!

sorry hope i'm not wasting your time!
I ran the command as follows :-
fastboot flash boot boot_signed.img
(I got the img file from the ruu )
I'm not 100% sure if it worked, but at that stage I didn't see any errors
Michealtbh said:
Are you absolutely sure you flashed the boot.img from the rom.zip using fastboot on your computer? Because it really sounds like you didn't
Click to expand...
Click to collapse

CWM 5.8.4.0 has the USB mounting fixed. You can go to mounts and storage and mount as USB, then the PC will see it.
fastboot flash recovery recovery.img
Wipe cache and dalvik cache.
I'm pretty sure you either didn't flash the boot.img or flashed the wrong one, so get it again to make sure it's the right one and
fastboot flash boot boot.img
And
fastboot erase cache

thanks!
I'll give it a go - to be honest i don't insist on using cm10 at all - i just wanted to see what jellbean was like and it seemed like a reasonable way of achieving that.... i'd be quite happy with any decent rom if it can fix the lag problems i have and some of the other issues.....
great tutorial by the way! - once my phone has charged up again I'll try it
ORStoner said:
This is a thread I made and it should provide you with a solution if not a starting point if you insist on CM10.
http://forum.xda-developers.com/showthread.php?t=1900127
Good luck!
Click to expand...
Click to collapse

ahhhh!
i think i was trying to run CWM 5.8.2.7 which possibly didn't have usb mounting working? Will give that a shot thanks!
BenPope said:
CWM 5.8.4.0 has the USB mounting fixed. You can go to mounts and storage and mount as USB, then the PC will see it.
fastboot flash recovery recovery.img
Wipe cache and dalvik cache.
I'm pretty sure you either didn't flash the boot.img or flashed the wrong one, so get it again to make sure it's the right one and
fastboot flash boot boot.img
And
fastboot erase cache
Click to expand...
Click to collapse

Thanks.
I use CM10 myself at the moment because of the aesthetics, but because of the amount of ram and battery it uses I wish I had stuck with ARHD.
Come October we should see Jellybean ARHD which will have great features like USB OTG without a powered hub.

lazclark said:
i think i was trying to run CWM 5.8.2.7 which possibly didn't have usb mounting working? Will give that a shot thanks!
Click to expand...
Click to collapse
Mount as USB not working on that version, also charging not working either. It was not a great release in terms.of features, but it was updated quickly, that's quite an.old version now.
Do you know which tutorial you followed? It really needs updating, there are a lot of people on this old version struggling more than they need to.

Right, first you're going to flash a recovery which allows you to mount USB storage. Either cwm or TWRP, download the recovery.img and flash through fastboot using fastboot flash recovery rocoveryname.img.
Download a new rom and extract the boot.img from it. Flash that boot.img using the usual fastboot method.
Now boot into the new recovery, connect to your pc and mount USB storage from the option in recovery. Copy over the rom you downloaded. Unmount USB storage. Now do a full wipe through the menu in recovery - format /data, /system and /cache. Now flash the rom and reboot

[Q] HTC ONE -- can't access from computer

Hi all, I ****ed up and didn't make a backup.
I wiped the phone clean from bootloader recovery, but then realized I had forgotten to move the new gapps and cm rom to my phone.
When I plug it in, it is recognized by my computer, but the HTC MTP Device fails to work.
I can't see the phone, and therefore can't put anything on it to flash. If I mount the phone via the bootloader, it pops up in Windows and wants to be formatted.
I have been looking around and trying different things for the past couple hours, and figured it was time to ask someone who might know..
Any ideas?

chriswcs said:
Hi all, I ****ed up and didn't make a backup.
I wiped the phone clean from bootloader recovery, but then realized I had forgotten to move the new gapps and cm rom to my phone.
When I plug it in, it is recognized by my computer, but the HTC MTP Device fails to work.
I can't see the phone, and therefore can't put anything on it to flash. If I mount the phone via the bootloader, it pops up in Windows and wants to be formatted.
I have been looking around and trying different things for the past couple hours, and figured it was time to ask someone who might know..
Any ideas?
Click to expand...
Click to collapse
I tried to take a screen shot, but it won't let me post it as I am noob-status.
Device Manager:
Android USB Devices
MyHTC
.
.
.
Portable Devices
J:/
<!> MTP USB Device
I don't understand why I can't mount or access the phone. Do I not have the right drivers installed?
Is there any way to get around this and put the files on my phone so I can install any old ROM so I can boot it up again??

You need to update the drivers on your PC, there's a few threads on how to do it. You should still be able to use adb push to add files, though.

Drivers are fine ! Go in recovery and mount the sdcard as a usb mass storage device ! In the title you speak of a HTC one......so is it a ONE or a ONE X ?

Thanks for replying!
It is an HTC One X. Should I just install the Android SDK bundle? Or are there other drivers?

Android sdk bundle is good. But you have MYHTC so that's correct. You need to go into the recovery and mount the sdcard as a usb storage device, it will show the drive in windows and then you can copy a rom onto it.

Mr Hofs said:
Android sdk bundle is good. But you have MYHTC so that's correct. You need to go into the recovery and mount the sdcard as a usb storage device, it will show the drive in windows and then you can copy a rom onto it.
Click to expand...
Click to collapse
Hi, so I installed the newest HTC driver (4.2) and all the SDK bundles. When I plug the phone it, it still won't recognize the HTC MTP Device. When I mount from the bootloader, it doesn't let me mount the sdcard (only the system data and cache), and Windows still shows a drive that needs to be formatted.
Do you think it's still a Windows driver I'm missing? If I go Terminal Command on phone it says
E: Unable to mount '/sdcard'
E: Unable to mount storage.

What's the option called you tap inside recovery. And what recovery are you using ?
If it's CWM you go to mounts and storage and tap the last option in that list.....then wait till it pops up on the pc

I'm using TWRP v 2.4.2.0 and I couldn't check the box for mount sdcard.
ADB push worked!
But the ROM failed. Is there anything else I'm missing?
It still says that E: can't mount.

Try this recovery please, i know this one blinded
https://db.tt/MNtVjpOJ

Mr Hofs said:
Try this recovery please, i know this one blinded
https://db.tt/MNtVjpOJ
Click to expand...
Click to collapse
Firstly thank you so much for taking time to help a lost stranger out!
What I did was reformat the J: drive that popped up on Windows, then I was able to put both the CM10.2 and GAPPS on the /sdcard/ (it would then mount)
I could then install both of them successfully, but I don't have a boot.img because my kernel is wiped. Will that file work as a boot.img?

chriswcs said:
Firstly thank you so much for taking time to help a lost stranger out!
What I did was reformat the J: drive that popped up on Windows, then I was able to put both the CM10.2 and GAPPS on the /sdcard/ (it would then mount)
I could then install both of them successfully, but I don't have a boot.img because my kernel is wiped. Will that file work as a boot.img?
Click to expand...
Click to collapse
Or how do I try your recover? Should I push it with adb? If so, to where?
I found two other boot.img files on the webs (boot.img and cm10.img), but I don't know how to get the phone to actually boot off them

The boot.img has to be flashed via Fastboot in the bootloader. So if you installed CM correctly via the recovery then flash the boot.img from the CM.zip ....
Fastboot flash boot boot.img
And a kernel can't be wiped via the recovery by the way. You can only delete/overwrite it via Fastboot commands

Mr Hofs said:
The boot.img has to be flashed via Fastboot in the bootloader. So if you installed CM correctly via the recovery then flash the boot.img from the CM.zip ....
Fastboot flash boot boot.img
And a kernel can't be wiped via the recovery by the way. You can only delete/overwrite it via Fastboot commands
Click to expand...
Click to collapse
Okay! That's good
I think it flashed correctly, now I am just waiting for the phone to boot up. It's been going for about 25 minutes though. Should it be that long?

Nope not good.......make a full wipe in recovery before installing the rom.
Factory reset
Wipe cache partition
Advanced-wipe dalvik cache
Mounts and storage-format cache,data,system
Then install CM and gapps then reboot because you already flashed its boot.img

Mr Hofs said:
Nope not good.......make a full wipe in recovery before installing the rom.
Factory reset
Wipe cache partition
Advanced-wipe dalvik cache
Mounts and storage-format cache,data,system
Then install CM and gapps then reboot because you already flashed its boot.img
Click to expand...
Click to collapse
None of the ROMs I've tried have worked! I think it's because my hboot is version 1.14.

Lol dude you have the evita go to the HTC one XL forum. You are in the completely wrong forum......sorry !!!

chriswcs said:
None of the ROMs I've tried have worked! I think it's because my hboot is version 1.14.
Click to expand...
Click to collapse
Stuck yet again.
I relocked the phone to flash new firmware, but I have CID 1111111, so I can't find anything to unlock the bootloader again.
Double sauced. Ahhhhhh

Unlock the bootloader by flashing the unlock_Code.bin file wich you got the first time when it's unlocked.
Fastboot flash token unlock_code.bin
But you really should continue this in the right forum. Flashing stuff from here may brick the phone !

[Q] Uh-Oh, TWRP not allowing me to mount via USB

$10 paypal to who can help me solve this
Here's the deal people,
My GNex was slowing down and acting all funny with stock 4.3 after about 6 months
I finally decided to try out a 4.4.2 ROM
I had TWRP on the phone so I said I'd just copy the Zip to the root folder along with the Gapps
Long story short, I accidentally wiped the storage.
Then I said no biggie, and figured that I'd just mount the USB to my laptop and transfer the Zip file of the ROM I wanted over to the storage.
BUT when ever I tap on mount USB nothing shows up in the devices.
Now I have nothing to transfer the files to.
I have windows 8 on the computer I'm currently using if that matters.
Forgive me people. I am not an avid flasher like I was when windows phone 6 was still around. So spare the insults . Just need my phone running so I can contact my loved ones

Galaxy Nexus uses MTP instead of Mass Storage mode, so you can't mount it as usual.
However, there's an "ADB sideload" option that lets you sideload a ROM from your PC using the ADB command (if you have the drivers installed, in the command prompt window, just type "adb sideload *THE-PATH-TO-YOUR-ROM-FILE*").
Find out more with Google
throwback1718 said:
$10 paypal to who can help me solve this
Click to expand...
Click to collapse
We Chinese don't use Paypal
Sent from Google Nexus 4 @ CM11

AndyYan said:
Galaxy Nexus uses MTP instead of Mass Storage mode, so you can't mount it as usual.
However, there's an "ADB sideload" option that lets you sideload a ROM from your PC using the ADB command (if you have the drivers installed, in the command prompt window, just type "adb sideload *THE-PATH-TO-YOUR-ROM-FILE*").
Find out more with Google
We Chinese don't use Paypal
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
agh I have read that the drivers don't work on windows 8 PC's . But I'll try
I flash my phone usually 2 or 3x per 12 months. so please pardon me if I forget some things...
In addition, the phone has nothing on it but TWRP
so no OS is on it at the moment. and no USB mounting.

I think USB mount is used for mounting USB flash drives attached through USB OTG.
The essentials. Contains ADB, fastboot and USB drivers from the Android SDK (should work on 8 and 8.1).
ADB_usb-driver.zip (8.79 MB)
To transfer files within TWRP, you need to use adb. Start by installing the driver. To verify for successful driver installation, type in:
Code:
adb devices
It should show you a "List of devices attached" and there's at least 1 item in the list.
Then copy the zip you want to flash into the same folder as adb. Let's say the file is named rom.zip. To "push" it to the phone, use the following command:
Code:
adb push rom.zip /sdcard/rom.zip
After it has finished "pushing" the file, just tap "Install" in TWRP and the zip file should be there!
You can now proceed flashing the ROM of your choice.

If you have wiped the storage without subsequently booting into a working ROM, the internal storage partition will be unformatted and you may have trouble writing to it.
If this is the case and you don't have a bootable ROM, you will need to flash a stock ROM via fastboot first and boot once, then try the whole thing again (don't wipe userdata this time!).

cmstlist said:
If you have wiped the storage without subsequently booting into a working ROM, the internal storage partition will be unformatted and you may have trouble writing to it.
If this is the case and you don't have a bootable ROM, you will need to flash a stock ROM via fastboot first and boot once, then try the whole thing again (don't wipe userdata this time!).
Click to expand...
Click to collapse
THis is my issue now. I was able to get the GNex wugfresh toolkit
I was able to push the original 4.4.2 ROM that I wanted over to the device. But It keeps saying failed at the install point.
Good thing I came back to read this post. Thanks. Ill try to flash by fastboot
EDIT Now im trying to do it via fastboot and its saying AdbWinApi.dllis missing.
I keep hitting these damn road blocks. Im sure I have many people calling and texting me.

Can you temporarily put the SIM in another operable phone to get your calls and texts?
Not sure about the fastboot error. You'd need to download a Google stock ROM image directly from them, and fastboot flash the system and boot partitions. This should be enough for a reboot to regenerate the user data partition. You cannot flash the custom ROM in fastboot unless a version has been made available in that format.
Sent from my Nexus 5 using Tapatalk

throwback1718 said:
EDIT Now im trying to do it via fastboot and its saying AdbWinApi.dllis missing.
Click to expand...
Click to collapse
Might as well use another non-Win8 computer, drivers are hard to mess with.
Sent from Google Nexus 4 @ CM11
---------- Post added at 09:55 AM ---------- Previous post was at 09:53 AM ----------
cmstlist said:
If you have wiped the storage without subsequently booting into a working ROM, the internal storage partition will be unformatted and you may have trouble writing to it.
If this is the case and you don't have a bootable ROM, you will need to flash a stock ROM via fastboot first and boot once, then try the whole thing again (don't wipe userdata this time!).
Click to expand...
Click to collapse
Is that so?
Sent from Google Nexus 4 @ CM11

AndyYan said:
Is that so?
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
Yes, why would I say it if it were not my experience that it is so?
On Nexus devices, a userdata wipe from the bootloader often leaves it in a state where custom recovery cannot write to data. Booting once into a bootable ROM typically fixes this.
Sent from my Nexus 7 using Tapatalk

cmstlist said:
Yes, why would I say it if it were not my experience that it is so?
On Nexus devices, a userdata wipe from the bootloader often leaves it in a state where custom recovery cannot write to data. Booting once into a bootable ROM typically fixes this.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I mean, is it true that after wiping all partitions (data, cache, dalvik, system, internal storage) in recovery, you cannot sideload a ROM as usual? What error does the phone give? And why does wiping breaks partition table, when all it does is *independently* formatting all partitions?
Sent from Lenovo Erazer Z500 @ Android-x86 4.3

AndyYan said:
I mean, is it true that after wiping all partitions (data, cache, dalvik, system, internal storage) in recovery, you cannot sideload a ROM as usual? What error does the phone give? And why does wiping breaks partition table, when all it does is *independently* formatting all partitions?
Sent from Lenovo Erazer Z500 @ Android-x86 4.3
Click to expand...
Click to collapse
I don't have all the answers to that. Wiping data in custom recovery should not be an issue because TWRP & CWM are both designed to keep /sdcard intact and erase the rest, which means it's just deleting files not formatting the whole partition. What I'm saying has to do with when you're in *fastboot* and you either factory reset, reflash userdata.img or wipe userdata.img, or unlock the bootloader.
On my GNex in this situation, circa 1.5 years ago, TWRP gave an error in which it thought the data partition was encrypted. CWM did not give an error but any files I attempted to write did not actually stick. One boot into a working ROM fixed it.
I have also observed that after a fastboot wipe, it starts booting into the ROM, possibly displays the Android "unpacking" screen, and then resets to the Google splash screen one more time, and then the second boot is the successful one. I have no idea if it has to do with permissions, formatting, or whatever else, I just know that it happens.

throwback1718 said:
THis is my issue now. I was able to get the GNex wugfresh toolkit
I was able to push the original 4.4.2 ROM that I wanted over to the device. But It keeps saying failed at the install point.
Good thing I came back to read this post. Thanks. Ill try to flash by fastboot
EDIT Now im trying to do it via fastboot and its saying AdbWinApi.dllis missing.
I keep hitting these damn road blocks. Im sure I have many people calling and texting me.
Click to expand...
Click to collapse
Your 4.4.2 ROM install most likely failed due to outdated TWRP. You must install twrp 2.6.3.2 via fastboot first, then you should be able to install and get going.
Let me know if you need links to anything
---------- Post added at 05:11 AM ---------- Previous post was at 05:10 AM ----------
Also, next time don't "wipe/format data" in twrp. Do factory reset. (Unless they changed the damn name again on us lol)