A100 rooted unlocked CarbonRom from pio. My rom works fine, I can still boot into it. But I've become a flasher lately, and want to keep trying other roms. When I boot to recovery and try to wipe data. I get an error that it failed, and the log says unable to mount '/data' (tw_mount). But like I said, i can still boot into my current rom"pio's awesome CarbonRom", I just wanted to try some other roms. I tried 'fastboot flashing a100-fstab-fixed-for-twrp-boot.img', that I got from 2nd post on http://forum.xda-developers.com/showthread.php?t=2431506 . I used the command 'fastboot flash recovery a100-fstab-fixed-for-twrp-boot.img' . Then recovery wouldn't boot at all, and just goes straight to CarbonRom, which I am glad it hasn't bricked. So I boot back into bootload from adb with fastboot, and and reinstalled twrp 2.2.2.1 with 'fastboot flash recovery openrecovery-twrp-2.2.2.1-a100.img' . So now I got a twrp working again, but I was a 2.6, and this one still doesn't mount data. Any tips?
bigbpc said:
A100 rooted unlocked CarbonRom from pio. My rom works fine, I can still boot into it. But I've become a flasher lately, and want to keep trying other roms. When I boot to recovery and try to wipe data. I get an error that it failed, and the log says unable to mount '/data' (tw_mount). But like I said, i can still boot into my current rom"pio's awesome CarbonRom", I just wanted to try some other roms. I tried 'fastboot flashing a100-fstab-fixed-for-twrp-boot.img', that I got from 2nd post on http://forum.xda-developers.com/showthread.php?t=2431506 . I used the command 'fastboot flash recovery a100-fstab-fixed-for-twrp-boot.img' . Then recovery wouldn't boot at all, and just goes straight to CarbonRom, which I am glad it hasn't bricked. So I boot back into bootload from adb with fastboot, and and reinstalled twrp 2.2.2.1 with 'fastboot flash recovery openrecovery-twrp-2.2.2.1-a100.img' . So now I got a twrp working again, but I was a 2.6, and this one still doesn't mount data. Any tips?
Click to expand...
Click to collapse
You flashed kernel over recovery, you really need to triple check commands like that.
fastboot flash boot a100-fstab-fixed-for-twrp-boot.img
Notice its flash boot, that portion tells where to flash the image to, when you said recovery it wrote it there instead.
Sent from my Galaxy Nexus using Tapatalk 2
pio_masaki said:
You flashed kernel over recovery, you really need to triple check commands like that.
fastboot flash boot a100-fstab-fixed-for-twrp-boot.img
Notice its flash boot, that portion tells where to flash the image to, when you said recovery it wrote it there instead.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thank you so much pio_masaki. I should have came to the forums first rather then try to put together fragmented information in my brain. I know little to nothing of adb and fastboot. You are awesome.
Related
Hi, i just got my Galaxy Nexus and unlocked+rooted it with the Toolkit v6.1.
Then i flashed CWM Recovery and tried flashing a Rom (Slim ICS), but i got the error: E: Can't open /sdcard/Base_3.6.zip (bad) Installation aborted.
What is also unnormal: I can't boot into Recovery normally. When i try to get into recovery via Fastboot, i get Screen with a green Android, laying down, chest open, with a red sign in it. Well, doesnt look so good...
I was only able to recovery when i flashed it via Rom Manager and then booted to it via Rom Manager. Whats also strange: After Wiping & trying to flash (back @ stock settings), the recovery seemed to be gone again. I had to reflash it again via Rom Manager, to make it work.
I got the impression, that there is something wrong with my phone's permissions. Any ideas how i can fix that?
Thx for the help!
W4yl4nder said:
..I was only able to recovery when i flashed it via Rom Manager and then booted to it via Rom Manager..
Click to expand...
Click to collapse
thats the problem, flash the recovery via fastboot. rom manager really sucks, im surprised so many people use it. in the end, it causes more headaches than it prevents. btw, you should try twrp recovery instead, its much better than cwm recovery.
Please don't use toolkits or all-in-one's or one-click's unless you understand what they do and how they do it. There's simply no need for a toolkit on this device.
Code:
> fastboot oem unlock
> fastboot flash clockworkmod-recovery.img recovery
Then you know that it's done, and done properly. I bet if you do that, you'll then be able to boot directly into recovery.
codesplice said:
Please don't use toolkits or all-in-one's or one-click's unless you understand what they do and how they do it. There's simply no need for a toolkit on this device.
Code:
> fastboot oem unlock
> fastboot flash clockworkmod-recovery.img recovery
Then you know that it's done, and done properly. I bet if you do that, you'll then be able to boot directly into recovery.
Click to expand...
Click to collapse
actually, it's 'fastboot flash recovery clockworkmod-recovery.img'.
Sent from my Transformer Prime TF201
bk201doesntexist said:
actually, it's 'fastboot flash recovery clockworkmod-recovery.img'.
Sent from my Transformer Prime TF201
Click to expand...
Click to collapse
That too, sorry. Got my head twisted up trying to handle [ CODE ] tags from my phone.
i got the recovery now (forgot to delete auto-reflash-recovery-on-boot file :/), but its still not working. when trying to flash a rom i still get the same error (also in twrp recovery).
W4yl4nder said:
i got the recovery now (forgot to delete auto-reflash-recovery-on-boot file :/), but its still not working. when trying to flash a rom i still get the same error (also in twrp recovery).
Click to expand...
Click to collapse
Verify that the zip is good?
hi i cant flash a diffrent recovery i have twrp 2.3.3 i am having troble flashing recovery using fastboot it just frezzes when its writeing the recovery i cant flash the pg32img it frezzes on boot please help
the recovery is erroring out on alot of things i cant mount eything except the sd card
Did you verify ms5 on recovery image and verify you are flashing correct one? You may also want to try a different cable.
Un1c0de said:
Did you verify ms5 on recovery image and verify you are flashing correct one? You may also want to try a different cable.
Click to expand...
Click to collapse
yes i have a 4 cables i have tryed to flash though fastboot it freezes when its whiting the recovery i haTeam Win Recovery Project 2.3.3 it wont mount cache system data it errors out when im flashing somthing i was trying to flash cm9 what should i do
i have a 2gig sd card in there
Apparently people didn't read my PSA....
what should i do next please
repley
yes i have a 4 cables i have tryed to flash though fastboot it freezes when its whiting the recovery i haTeam Win Recovery Project 2.3.3 it wont mount cache system data it errors out when im flashing somthing i was trying to flash cm9 what should i do
You can always return to stock. Check CS's thread in dev section. Then you need to adb flash custom recovery & superuser, and you should be good.
Sent from PAC-nation
rushhead what do i do how do i use adb from recovery
andriod lover said:
rushhead what do i do how do i use adb from recovery
Click to expand...
Click to collapse
Follow this thread:
http://forum.xda-developers.com/showthread.php?t=1599767
Then, if you don't have adb & drivers, you need the download from this thread:
http://forum.xda-developers.com/showthread.php?t=1751796
From here all you need to do is adb push custom recovery & superuser. Don't downgrade via revolutionary.
Sent from PAC-nation
it gets stuck on updating recovery it dors not go eny further than that
Hi everyone, I'm new here and I have a GNex on my hands.
While I received it to fix; I could not get it past a bootloop from the nexus 4.0.4 Boot.
Problem is I cannot seem to get past the boot animation screen nor upgrade it.
Tried flashing another bootloader via fastboot, and the bootloader does not change, stays in same version.
HW Version : 9
Bootloader version : PRIMEKK15
Baseband version : I9250XXKK6
I proceed doing a fastboot erase bootloader and trying another bootloader, rebooting into another bootloader but no luck
Tried also ODIN flash but no luck; stays into the same
Booting into recovery mode goes into stock recovery and tries to flash a file from /cache
By trying to flash CWM via fastboot flash recovery <cwm image> flashes image but no luck on booting into CWM.
Anbody can lend a hand please?
Thanks!
jhonnyx said:
Hi everyone, I'm new here and I have a GNex on my hands.
While I received it to fix; I could not get it past a bootloop from the nexus 4.0.4 Boot.
Problem is I cannot seem to get past the boot animation screen nor upgrade it.
Tried flashing another bootloader via fastboot, and the bootloader does not change, stays in same version.
HW Version : 9
Bootloader version : PRIMEKK15
Baseband version : I9250XXKK6
I proceed doing a fastboot erase bootloader and trying another bootloader, rebooting into another bootloader but no luck
Tried also ODIN flash but no luck; stays into the same
Booting into recovery mode goes into stock recovery and tries to flash a file from /cache
By trying to flash CWM via fastboot flash recovery <cwm image> flashes image but no luck on booting into CWM.
Anbody can lend a hand please?
Thanks!
Click to expand...
Click to collapse
You can flash a custom recovery like cwm or twrp. Then you can acces the custom recovery and adb push your ROM and gapps. Then you do the wipes and flash the ROM and gapps. If you dont understand anything you just have to tell me
Sent from my Galaxy Nexus using XDA Premium HD app
Thanks mrgnex. I've tried flashing TWRP, but the only thing it does is boot into stock recovery and tries to flash a file from /cache/, which file is: 5a81769b6d01.signed-yakju-IMM76I-from-ICL53F.5a81769b.zip; pretty weird. Issue is the same as this thread: http://forum.xda-developers.com/showthread.php?t=1909331&page=4
use: fastboot boot recovery.img
and "recovery.img" which recovery do you suggest? twrp or a CWM in particular?
doesnt matter. whichever.
jhonnyx said:
and "recovery.img" which recovery do you suggest? twrp or a CWM in particular?
Click to expand...
Click to collapse
I suggest the latest TWRP.
http://www.teamw.in/project/twrp2
Edit: Have you read this?
TheMysteriousOne said:
I suggest the latest TWRP.
http://www.teamw.in/project/twrp2
Edit: Have you read this?
Click to expand...
Click to collapse
While now I'm trying to install latest TWRP (already did and no luck) I'm downloading the pack from the "Have you read this?".
The things that I'm seeing right now that seem to be wrong are:
1 - everytime I reboot the phone, the "fastboot oem unlock" seems to be gone and phone re-locks again (weird!)
2 - every change I make to the filesystem, seems to be non-persistent I/E: push something via adb push and on reboot it's gone! :/
Any help would be greatly appreciated.
jhonnyx said:
While now I'm trying to install latest TWRP (already did and no luck) I'm downloading the pack from the "Have you read this?".
The things that I'm seeing right now that seem to be wrong are:
1 - everytime I reboot the phone, the "fastboot oem unlock" seems to be gone and phone re-locks again (weird!)
2 - every change I make to the filesystem, seems to be non-persistent I/E: push something via adb push and on reboot it's gone! :/
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Can you elaborate on why exactly you were not able to install TWRP?
TheMysteriousOne said:
Can you elaborate on why exactly you were not able to install TWRP?
Click to expand...
Click to collapse
Surely:
1 - Unlock via fastboot oem unlock
2 - fastboot erase recovery (exits with ok)
3 - fastboot flash recovery twrp_versiondoesnotmatter.img (exits with ok)
4 - reboot w/power+vlup+voldown and select reboot recovery
5 - stock recovery appears
an alternate method that i've tried:
1 - Unlock via fastboot oem unlock
2 - fastboot boot twrp_versiondoesnotmatter.img (exits with ok)
3 - TWRP boots and flashes a zipfile from /cache/ then reboots automatically
That's what happens. A mistery, huh?
Also I've tried OMAP Flash, and; the same issue happens over and over again
Have you tried doing a factory reset using the stock recovery?
TheMysteriousOne said:
Have you tried doing a factory reset using the stock recovery?
Click to expand...
Click to collapse
AFAIK, Yes
What happens once I start the stock recovery; as I've already stated; starts flashing a zip file located into /cache/ (5a81769b6d01.signed-yakju-IMM76I-from-ICL53F.5a81769b.zip); then bleh, starts the bootloop again.
I've tried the power+volup then selected wipe cache and wipe system and it's the same.
Did you try flash google's stock images (all of them) ?
Also try flashing TWRP in the boot (kennel) partition by :-
Code:
fastboot flash boot <path to twrp>.img
This will force the phone into Recovery (But you will have recovery bootloop , can be solved by flashing a kernel) .
when you boot into recovery install a Kernel and ROM . also you will lose the recovery after that .
You can flash the TWRP from the TWRP itself (to put it in the right partition) by (in the build in terminal) :-
Code:
dd if=/<path to twrp in SD>.img of=/dev/block/mmcblk0p8
Good Luck .
Sent from my Galaxy Nexus using xda app-developers app
$Parker said:
Did you try flash google's stock images (all of them) ?
Also try flashing TWRP in the boot (kennel) partition by :-
Code:
fastboot flash boot <path to twrp>.img
This will force the phone into Recovery (But you will have recovery bootloop , can be solved by flashing a kernel) .
when you boot into recovery install a Kernel and ROM . also you will lose the recovery after that .
You can flash the TWRP from the TWRP itself (to put it in the right partition) by (in the build in terminal) :-
Code:
dd if=/<path to twrp in SD>.img of=/dev/block/mmcblk0p8
Good Luck .
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
fastboot flash boot <path to twrp>.img does not boot the recovery . I mean; still boots the normal Kernel.
Actually I'm trying what TheMysteriousOne told me by downloading the stock Gnex zip (250Mb) to flash via Odin.
Ohh, bad luck strikes again:
<ID:0/011> system.img
<ID:0/011> Complete(Write) operation failed.
cannot write system.img :/
Any ideas?
Unlock your bootloader with omapflash. Although even if it does unlock, Your emmc/board probably has died.
a manta wrote this.
beekay201 said:
Unlock your bootloader with omapflash. Although even if it does unlock, Your emmc/board probably has died.
a manta wrote this.
Click to expand...
Click to collapse
can you please me guide how to do the omapflash?
I've downloaded a file called OMAPFlash_tuna.zip.
- Set battery of the device aside
- Plug device into USB, let it detect the device and flash the SBF I think.
That'd be all?
beekay201 said:
Unlock your bootloader with omapflash. Although even if it does unlock, Your emmc/board probably has died.
a manta wrote this.
Click to expand...
Click to collapse
Pardon me, if EMMC/Board is dead; why does it boot or get into bootloop? There is something that reflashes itself; it even overrides odin or heimdall...
Have you tried going back to completely stock using the method outlined here? http://forum.xda-developers.com/showthread.php?t=1626895
jhonnyx said:
can you please me guide how to do the omapflash?
I've downloaded a file called OMAPFlash_tuna.zip.
- Set battery of the device aside
- Plug device into USB, let it detect the device and flash the SBF I think.
That'd be all?
Click to expand...
Click to collapse
Read this thread
http://forum.xda-developers.com/showthread.php?t=2016628
a manta wrote this.
I woke up today to a bootloop. After pulling out the battery, I cant turn it on, it was stuck at the google logo. I thought it was some rom issue or something. When I had the time, in the afternoon, I just boot to recovery, and wiped data+sd card. Turns out sd card was not wiped.
Just now, I found a way to boot it. (AFTER WIPING DATA) I used the gnex toolkit and boot with insecure image, and guess wat? My old rom boots. Everything was the way it was, and then it crashed and stuck on the google logo again.(I made sure i wiped things two to three times, data and sd) I did a few experiments:
1) Flash using ODIN
2) Flash CWM using toolkit--it changed back to twrp after reboot
3) Changing the icon on my homescreen after boot--- everything was the same again after booting
4) Flash stock image using toolkit
5) Wipe data using manual adb
6) Try to lock my bootloader
Everything I tried changing, change back to the original state after reboot. What is the problem?
Device: Galaxy Nexus
ROM: Purity 7 sept release
Kernel: Fancy r42
Logs in twrp are showing updating partition, not FAIL. So I really don't think there is a need to show the recovery log.
HELP ME!
are you flashing your recovery or just booting the recovery?
fastboot oem unlock
fastboot flash recovery recovery.img
use ClockWorkMod. I've heard nothing but problems with TWRP.
player911 said:
are you flashing your recovery or just booting the recovery?
fastboot oem unlock
fastboot flash recovery recovery.img
use ClockWorkMod. I've heard nothing but problems with TWRP.
Click to expand...
Click to collapse
umm, i can boot recovery. i cannot flash cwm. i tried, but when i reboot, it went back to twrp.
what is oem unlock for? coz its smth i havent tried.
jacktay94 said:
umm, i can boot recovery. i cannot flash cwm. i tried, but when i reboot, it went back to twrp.
what is oem unlock for? coz its smth i havent tried.
Click to expand...
Click to collapse
Oem unlock will unlock your bootloader and wipe the internal storage in the process. I saw you didn't use fastboot. You could try that. Flash the Factory image via fastboot. If that fails try omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Oem unlock will unlock your bootloader and wipe the internal storage in the process. I saw you didn't use fastboot. You could try that. Flash the Factory image via fastboot. If that fails try omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Yup,I tried it already thru toolkit. Not working either.
Dude the toolkit blows, flash back to stock manually via adb command prompt. There are tutorials around here on how to do it. It's guaranteed to work if you don't screw it up.
Honestly flashing back to stock via adb should be something everyone should learn if you plan on flashing roms.
SoHaunted said:
Dude the toolkit blows, flash back to stock manually via adb command prompt. There are tutorials around here on how to do it. It's guaranteed to work if you don't screw it up.
Honestly flashing back to stock via adb should be something everyone should learn if you plan on flashing roms.
Click to expand...
Click to collapse
i did adb bro, its the last thing i tried, i learnt and try.
Sent to Samsung centre, they told me its my flash IC thats blown. sobs
Howdy Everyone,
So just tried rooting my new m8 and now I'm stuck endlessly booting into TWRP. I thought I did everything correctly: Unlocked the bootloader, installed the USB drivers, installed the ADB fastboot drivers and then flashed twrp 2.7.0.3. I get to the the htc logo screen/warning and, bam, back to twrp everytime.
Does anyone know how to fix this??? The last time i was rooting and installing custom mods was back in samsung galaxy s2 days, so my knowledge is a little dated. Please help!!
Try flashing the recovery again. Download it from the link provided here and confirm the md5 checksum for the zip file.
http://forum.xda-developers.com/showthread.php?t=2694564
Sent from my HTC One_M8 using XDA Premium 4 mobile app
PirateP3t3 said:
Howdy Everyone,
So just tried rooting my new m8 and now I'm stuck endlessly booting into TWRP. I thought I did everything correctly: Unlocked the bootloader, installed the USB drivers, installed the ADB fastboot drivers and then flashed twrp 2.7.0.3. I get to the the htc logo screen/warning and, bam, back to twrp everytime.
Does anyone know how to fix this??? The last time i was rooting and installing custom mods was back in samsung galaxy s2 days, so my knowledge is a little dated. Please help!!
Click to expand...
Click to collapse
some reason doing twrp from terminal on hte m8 gets us stuck (it did for me at least.)
just reflash the insecure boot image.. fastboot flash boot blah.img
that should get you back up
PirateP3t3 said:
Howdy Everyone,
So just tried rooting my new m8 and now I'm stuck endlessly booting into TWRP. I thought I did everything correctly: Unlocked the bootloader, installed the USB drivers, installed the ADB fastboot drivers and then flashed twrp 2.7.0.3. I get to the the htc logo screen/warning and, bam, back to twrp everytime.
Does anyone know how to fix this??? The last time i was rooting and installing custom mods was back in samsung galaxy s2 days, so my knowledge is a little dated. Please help!!
Click to expand...
Click to collapse
I encountered this issue as well. I'm almost certain that when you were flashing recovery, you used this command "fastboot flash boot recovery.img".
The right command should be "fastboot flash recovery recovery.img".
To rectify the issue look for a tread that has the boot.img for your specific M8 model and flash boot back using " fastboot flash boot boot.img".
This should fix the issue you are having
darll said:
I encountered this issue as well. I'm almost certain that when you were flashing recovery, you used this command "fastboot flash boot recovery.img".
The right command should be "fastboot flash recovery recovery.img".
To rectify the issue look for a tread that has the boot.img for your specific M8 model and flash boot back using " fastboot flash boot boot.img".
This should fix the issue you are having
Click to expand...
Click to collapse
Forgot to come back and update this thread, but this is exactly what I did and it worked!!! Now happily rooted and running.
Thanks for the help!
PirateP3t3 said:
Forgot to come back and update this thread, but this is exactly what I did and it worked!!! Now happily rooted and running.
Thanks for the help!
Click to expand...
Click to collapse
I followed the instructions on the TWRP site:
Download the above file. Save it to the root of your /sdcard directly (internal memory only) and rename it to twrp.img
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p43
Then reboot to complete installation.
But that left me in a TWRP bootloop. Can you please give me step by step instructions on how to get out of this bootloop?
Thanks!
First off, being a noob and using dd without even knowing what partiton you're writing to is extremely dangerous.
Just use fastboot.
plug phone into PC in fastboot mode.
Code:
fastboot flash recovery twrpfilename.img
fastboot erase cache
on phone go back to hboot, select, recovery
In TWRP go to wipe, then swipe for a factory reset (Advanced wipe cannot properly wipe cache and dalvik after fastboot erase cache)
then go to advanced, select cache, dalvik and system and swipe to wipe those partitions.
then go to install, select the rom on your phone and flash. follow on screen instructions.
If you don't have the rom on your phone for whatever reason,
connect your phone, while in TWRP to your PC then, using adb on your PC
Code:
adb push romfilename.zip /sdcard/
Wait until it completes with bytes sent.
Then flash using method listed above.
Be careful if you want to keep your phone. I stress this, if you don't know what a command you are issuing does, exactly, DO NOT DO IT until you look it up and understand what you are doing. There is great risk even when you know what you're doing. There's a LOT more when you don't.
exad said:
First off, being a noob and using dd without even knowing what partiton you're writing to is extremely dangerous.
Just use fastboot.
plug phone into PC in fastboot mode.
Code:
fastboot flash recovery twrpfilename.img
fastboot erase cache
on phone go back to hboot, select, recovery
In TWRP go to wipe, advanced, select cache, dalvik and system
then go to install, select the rom on your phone and flash. follow on screen instructions.
If you don't have the rom on your phone for whatever reason,
connect your phone, while in TWRP to your PC then, using adb on your PC
Code:
adb push romfilename.zip /sdcard/
Wait until it completes with bytes sent.
Then flash using method listed above.
Be careful if you want to keep your phone. I stress this, if you don't know what a command you are issuing does, exactly, DO NOT DO IT until you look it up and understand what you are doing. There is great risk even when you know what you're doing. There's a LOT more when you don't.
Click to expand...
Click to collapse
Thanks for the detailed instructions. I opened fastboot on my PC with phone plugged in and entered the code but the cmd prompt just says <waiting for device>
Do you have the HTC drivers installed on your PC with HTC sync uninstalled?
Does it say fastboot USB on your phone?
Sent from my HTC One_M8 using xda app-developers app
Update: I ended up just installing the Viper ROM and the system rebooted fine. It's strange that I couldn't reboot the device to get out of recovery without having to install a custom ROM.
Sent from my HTC6525LVW using Tapatalk
No it's not. You flashed recovery to the boot partition.
Sent from my HTC One_M8 using xda app-developers app
How do i fix TWRP Bootloop on my HTC explorer a310e... ?
How do i fix TWRP Bootloop on my HTC explorer a310e... ?
I hav custom cm11 Kitkat ROM installed on it...
but after I installed the rom, and again tried to reboot
into TWRP recovery, it is just stuck on the blue color
TEAMWIN screen... Please help how to fix it...!
HELP PLEASE
I pressed factory reset on my cm13 rom htc one m8 with twrp and now its just stuck flashing the teamwin logo and i cant do anything, i tried using fastboot but it cant see the device.
Maxxour said:
HELP PLEASE
I pressed factory reset on my cm13 rom htc one m8 with twrp and now its just stuck flashing the teamwin logo and i cant do anything, i tried using fastboot but it cant see the device.
Click to expand...
Click to collapse
You need cwm recovery to factory reset from cm roms.
Also you need to be in FASTBOOT mode for it to detect your device.
Boot to fastboot, erase cache, reinstall twrp.
Next time reset/wipe from recovery.
ashyx said:
You need cwm recovery to factory reset from cm roms.
Click to expand...
Click to collapse
cwm recovery or cm recovery?