[Q] Which partitions need to be mounted? - One (M7) Q&A, Help & Troubleshooting

So earlier today, I S-offed, and changed my CID, but now for the life of me either using a RUU or sideloading a custom rom, it just hangs at the HTC One boot screen with the beatsaudio at the bottom. When I go into ClockworkMod recover, the /data and /system partitions are usually unmounted. I've tried mounting them, then sideload a rom, or leaving and sideloading, but neither works. Basically cannot get my phone to boot past there. Obviously I can warranty my phone, but I'd rather not have to do that. The rom I use when sideloading is ARHD 10.2. Might be forgetting some stuff, end of my day and pretty tired. Thanks for the help in advance.
EDIT: Also had flashed the 2.17 firmware.

Try with TWRP
And, sideloading don't need any mounted partition...

Same results, just hangs during boot.
EDIT: Still need to know which partitions should be mounted though. Like which are when a phone that is normally booting boots.

Related

Does not boot

I was trying to go from Drizzy's touchflo 3D to JACxDrizzy's ROM.
I have fat32, ext3, and linux-swap, all the appropriate size
So, i followed the usual steps:
boot to recovery, nandroid backup (i have 1.4 recovery btw), wipe, flash, boot.
Except, the phone got stuck in a bootloop. So i booted to fastboot, then used the "fastboot flash ____ ____img" commands to restore.
Also a bootloop.
I thought of using the 1.4's nandroid restore function, but that does not work since after backing up, I moved the backup to my desktop, changed the folder name, and deleted the backup from my phone. I tried to adb push the files back in, but recovery still said that the backups were not in the phone.
So I wiped everything, including ext3, then tried again, this time going back to my previous build, Drizzy's touchflo 3d. It seemed to be working - i went to recovery and selected the flash update.zip option. Then the options disappeared, as usual, and the text (showing the progress of the flashing) began to show up. However, the phone froze after the first two lines of text.
I decided to wait. Eventually, my phone shut down. I tried to boot my phone in all 3 ways (standard, recovery, and fastboot) but none of them worked. The red LED blinked twice and the phone has no response.
How do I get my G1 to boot, and after that, how do i get nandroid to work?
EDIT: Ok I feel stupid now. The phone just ran out of battery. But the question still stands: How do i get nandroid to work?
since you nuked your ext3 your nandroid probably will not work because the hero rom will be looking for the files necessary for it on your ext3 but they are not there so it will bootloop. try flashing whatever rom you want to with a cleanly formatted card and see if it will boot up.
I don't know why, by Drizzy's builds always require EXT formatting, but JAC's don't. So you got a bootloop because you didn't wipe your ext3. I always just use Cyan's recovery to restore a nandroid backup. If that flails I guess you have to start over.

Big troubles after flashing CyanogenMod 5.0.7

Hi,
I tried flashing the brand new CyanogenMod 5 with Eclair for G1, and I seem to be in "serious" trouble now.
Before flashing:
I had already installed DangerSPL for a few months with no issue
Had the latest radio
Was happily running SuperD1.9.3 with WG Kernel and JIT enabled
Made a Nandroid backup just in case I wished to go back
Wiped Dalvik-cache and Data/Cache to avoid boot loops
All of this with Cyan's Recovery 1.4.
After flashing the ROM and the Gapps, my phone restarted and got stuck on the G1 screen (no boot screen) for, maybe 15 to 30 minutes, which seemed a bit long for me... I finally decided to remove the battery, went back to recovery and made a Nand restore.
But after the restore, rebooting had the same effect : stuck on G1 screen.
I tried flashing several custom roms with no luck (all stuck on G1 screen).
I finally decided to flash the official ADP1.6 ROM from HTC (signed-dream_devphone_userdebug-ota-14721.zip) which installed fine (and updated the radio by the way), and it finally booted on stock Donut.
I tried then to reinstall custom roms but get stuck on G1 screen everytime I try... and flashing Amon_RA's recovery won't work (i keep booting on the stock recovery). But as a workaround, I can use fastboot to boot into Amon_Ra's recovery.
The questions now are :
did I lose root access, thus preventing from installing custom ROMs ?
if so, is it possible to downgrade while being under DangerSPL ? Won't it brick the phone ?
Is there anybody else who had the same problem with upgrading to Cyan's 5 ?
I really need to get custom roms back, stock sucks on G1... but there is no way i can afford bricking my phone.
Thanks for help guys!!
As long you can get to your custom recovery menu, you still have root access.
Keep the Danger SPL, not worth changing it and the Danger SPL has fastboot also.
It takes a while to boot into a newly flashed ROM so just wait 5-15 min.
Do these steps:
1)Do a FULL WIPE of the phone (data, dalvik-cache, ext, battery stats, and rotation ****You won't have some of these options with Cyanogen's recovery. Just wipe what you can****)
2)Repair the ext partition
3)Flash CyanogenMod 5.0.7-DS-Test 1 (this is the g1/mt3g version)
4)Without wiping or rebooting, flash the gapps .zip file
5)Reboot and set up the ROM
6)Flash the latest Amon_RA recovery for your device. Cyanogen uses Amon-RA's recovery now.
1. Upgrade your recovery....cyanogen stopped working on his a while ago, upgrade to Amon_RA's recovery.
2. You only have to wipe data/dalvik, and maybe sd-ext. you do NOT have to wipe battery stats or rotation EVER.
3. Flash CM Rom
4. Flash gapps
Unfortunately, exact same thing.
Stuck on G1 screen.
Reverted back again to adp 1.6
Any other suggestions ?
alou2 said:
Unfortunately, exact same thing.
Stuck on G1 screen.
Reverted back again to adp 1.6
Any other suggestions ?
Click to expand...
Click to collapse
Give us your spl (hboot) and radio. Go into fastboot and type exactly what you see.
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA20000)
CPLD-4
RADIO-2.22.19.26I
Good ?
alou2 said:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA20000)
CPLD-4
RADIO-2.22.19.26I
Good ?
Click to expand...
Click to collapse
Try upgrading your radio? You shouldn't HAVE to, but it might work.
Are you on Amon_RA's recovery now?
I'll try upgrading radio, but it's weird I can't switch back to other custom donut builds...
I've used Amon-RA's recovery to wipe and install the ROM this time.
For some odd reason though, it seems i can't "install" Amon_RA recovery (it seems to switch back to stock recovery), but just boot it through fastboot...
alou2 said:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA20000)
CPLD-4
RADIO-2.22.19.26I
Good ?
Click to expand...
Click to collapse
make sure you're flashing the right recovery. dream still has two options. just like mytouch has H or G.
the one with "R" on the end of it is for rogers, one without it is for USA ones.
What files are you flashing? It sounds like you're flashing an old 1.6 base that has a recovery image included. Are you flashing the DRC83 Defanged as a base?
OK so I tried to take a fresh start on this.
I installed Amon_RA's 1.6.2 as recovery (not the Roger's one, I'm in France and the US tools always worked)
did a nandroid backup to stop reinstalling everything over again each time I want to make a phone call...
used it to repartition the SD (FAT / EXT2 / SWAP), thus formatting everything
wiped everything (except battery and orientation)
Flashed DRC83 Defranged
Without rebooting flashed CM5.0.7-t1
Without rebooting flashed Gapps
And it still gets stuck on the first boot screen (left it for about 20mn on it)...
Then I tried installing DRC83 defranged and it still gets stuck on the damned boot screen !!!
Through adb I can get to shell while on recovery, but the su command prints out :
/sbin/sh: su: not found
Is it normal ?
I can't find the /proc/last_kmsg file (just /proc/kmsg). Is there any log file that could help here ?
I'm going to nand back to stock 1.6, hoping it will start without having to flash the radio+recovery one again...
I noticed something weird when i nand back to my pre-CM5 WG-SuperD backup :
when it boots, it gets to the first boot screen and if USB is connected, i get a "fastboot usb" in a red box on top left of the screen.
To sum up :
phone's definitely not bricked, but won't run any custom rom anymore, but it still permits custom recovery installation/boot.
Something must have been broken/deleted somewhere.
Still asking the (dumb?) question : do I still have root, since su doesn't works (even using terminal server) ?
By the way, I really appreciate you guys taking time to read and answer my posts. Really
alou2 said:
OK so I tried to take a fresh start on this.
I installed Amon_RA's 1.6.2 as recovery (not the Roger's one, I'm in France and the US tools always worked)
did a nandroid backup to stop reinstalling everything over again each time I want to make a phone call...
used it to repartition the SD (FAT / EXT2 / SWAP), thus formatting everything
wiped everything (except battery and orientation)
Flashed DRC83 Defranged
Without rebooting flashed CM5.0.7-t1
Without rebooting flashed Gapps
And it still gets stuck on the first boot screen (left it for about 20mn on it)...
Then I tried installing DRC83 defranged and it still gets stuck on the damned boot screen !!!
Through adb I can get to shell while on recovery, but the su command prints out :
/sbin/sh: su: not found
Is it normal ?
I can't find the /proc/last_kmsg file (just /proc/kmsg). Is there any log file that could help here ?
I'm going to nand back to stock 1.6, hoping it will start without having to flash the radio+recovery one again...
I noticed something weird when i nand back to my pre-CM5 WG-SuperD backup :
when it boots, it gets to the first boot screen and if USB is connected, i get a "fastboot usb" in a red box on top left of the screen.
To sum up :
phone's definitely not bricked, but won't run any custom rom anymore, but it still permits custom recovery installation/boot.
Something must have been broken/deleted somewhere.
Still asking the (dumb?) question : do I still have root, since su doesn't works (even using terminal server) ?
By the way, I really appreciate you guys taking time to read and answer my posts. Really
Click to expand...
Click to collapse
I run into the same issue, I was upgrading from the latest cm 1.6 and after trying a few different things, after wiping with alt+w, I reinstalled danger-spl then installed the cm update, then the google apps; after doing this, it worked fine. BTW, it took about 15 mins to boot up though.
alou2 said:
OK so I tried to take a fresh start on this.
I installed Amon_RA's 1.6.2 as recovery (not the Roger's one, I'm in France and the US tools always worked)
did a nandroid backup to stop reinstalling everything over again each time I want to make a phone call...
used it to repartition the SD (FAT / EXT2 / SWAP), thus formatting everything
wiped everything (except battery and orientation)
Flashed DRC83 Defranged
Without rebooting flashed CM5.0.7-t1
Without rebooting flashed Gapps
Click to expand...
Click to collapse
There is your problem. DO NOT FLASH THE DRC83 BASE!!!
Just repartition your sdcard (if you want to), upgrade to ext3 or ext4, then follow the last 2 steps.
Hi UberMario,
I just reinstalled DangerSPL using Amon_ra's recovery, and then directly flashed CM5 + Gapps (no reboot inbetween).
It's been stuck on the 1st splash screen for 30 minutes now...
I'm letting it for another 30mn (although I think it's useless) and will eventually revert back to stock 1.6... again...
I just don't get what's wrong...
I'm going to try redownloading the archives in case they would've been corrupted, but being unable to install anything else than an official htc firmware seems like a symptom to me... isn't it ?
alou2 said:
Hi UberMario,
I just reinstalled DangerSPL using Amon_ra's recovery, and then directly flashed CM5 + Gapps (no reboot inbetween).
It's been stuck on the 1st splash screen for 30 minutes now...
I'm letting it for another 30mn (although I think it's useless) and will eventually revert back to stock 1.6... again...
I just don't get what's wrong...
I'm going to try redownloading the archives in case they would've been corrupted, but being unable to install anything else than an official htc firmware seems like a symptom to me... isn't it ?
Click to expand...
Click to collapse
I'm not sure if this will make a difference, but flash Gapps first then flash CM5 then reboot and everything should work...
or
You might want to check and make sure your MD5 is correct too..
why would you flash gapps first? you have to flash it on top of cm5.
Yeah... quite sure this won't help.
What could prevent the phone from booting custom firmwares but still allowing to install them ? (and finally I can still run the su command through adb, and get root access, but apps can't get root...)
tehseano said:
why would you flash gapps first? you have to flash it on top of cm5.
Click to expand...
Click to collapse
I rooted my G1 for the first time. I flashed CM 5.0.7 then GApps (no reboot in between). When the phone booted, none of the Google Apps were on the phone. Went back to recovery and did a wipe and flashed GApps then CM (no reboot) and everything installed correctly. Someone said to flash CM first then GApps, but that didn't work for me. Weird.

[Q] Nothing present after custom ROM install

I have spent a day and a half trying to fix all of my issues before I finally turned here but I am at my wits end.
This all started with my attempt to flash Viper to my HTC one. I installed clockwork touch loaded Viper to the drive and went to install. During the install process something happened and my install failed. When I rebooted the phone it returned to the fasboot screen and there was no recovery present. I had heard that sometimes TWRP works better for installing some ROMs so I decided to switch courses and try that. Before installing I went and formatted cache, data, ect. When I tried to install Viper this time it appeared to be a successful install. However, I was once again I was returned to the fastboot screen and no recovery was present. I tried this a few more times with either clockwork or TWRP using sideload with no luck. I also trried using fastboot to flash a sprint stock recovery boot and image. When the phone rebooted it showed the white HTC Screen but nothing happened for a half hour so I restarted the phone again only to be dropped into the fastboot. I also tried locking and unlocking the boot loader and tried a Sprint HTC one RUU with no success.
So at this moment this is where I stand:
I am on the fastboot screen with no recovery.
HBOOT 1.56.0000
S-ON
Any help you can provide would be GREATLY appreciated. Thanks for your time.
Betraythesway said:
I have spent a day and a half trying to fix all of my issues before I finally turned here but I am at my wits end.
This all started with my attempt to flash Viper to my HTC one. I installed clockwork touch loaded Viper to the drive and went to install. During the install process something happened and my install failed. When I rebooted the phone it returned to the fasboot screen and there was no recovery present. I had heard that sometimes TWRP works better for installing some ROMs so I decided to switch courses and try that. Before installing I went and formatted cache, data, ect. When I tried to install Viper this time it appeared to be a successful install. However, I was once again I was returned to the fastboot screen and no recovery was present. I tried this a few more times with either clockwork or TWRP using sideload with no luck. I also trried using fastboot to flash a sprint stock recovery boot and image. When the phone rebooted it showed the white HTC Screen but nothing happened for a half hour so I restarted the phone again only to be dropped into the fastboot. I also tried locking and unlocking the boot loader and tried a Sprint HTC one RUU with no success.
So at this moment this is where I stand:
I am on the fastboot screen with no recovery.
HBOOT 1.56.0000
S-ON
Any help you can provide would be GREATLY appreciated. Thanks for your time.
Click to expand...
Click to collapse
You probably should RUU and stay over.
Sent from my Slim Photon using xda app-developers app
So I have my phone up an running on a stock RUU but I seem to have the same issues with and error when installing Viper. Any ideas as to what the issue could be?
Betraythesway said:
So I have my phone up an running on a stock RUU but I seem to have the same issues with and error when installing Viper. Any ideas as to what the issue could be?
Click to expand...
Click to collapse
... now that its up and running, i recommend you get s-off 1st. it eases many things. then flash twrp 2.7.0.4 recovery and try to flash viper :victory: ...
I was in this situation myself. If you can adb twrp recovery onto your phone. Dont try to flash viper with cwm it will mess stuff up. After you have a recovery loaded flash the viper rom. If it boots up be sure to check about phone section in the settings and see if there is a baseband version present. If not just flash the latest firmware and you should be good to go. This was what i had to do.
Same here, about a month ago. They really need to just remove that option to flash CWM. I managed to get a recovery installed, but now it seems like half the ROMs I try to flash won't boot. I don't even know what Rom I am using, because it has disappeared from XDA. It's a 4.4.2 Sense 5.5 ROM, and it is odexed and came with Xposed Installer. It's the only ROM that seems to work anymore, so I have to wonder if my firmware got messed up. I'm S-On, with no way to S-off for the foreseeable future until I can fix my laptop. Since my laptop is unavailable, I'm a bit hesitant to mess with the phone much more, since I can't fix it again without the computer.
Sent from my HTCONE using Tapatalk
I've read a number of these threads, and many have Viper in common. Viper by itself is an amazing ROM. Maybe too amazing... Incredible amount of customization. I have to remind myself occasionally that as much as I flash ROMs and lurk around here that I am not a dev.
I would do my best to achieve S-OFF if you have any plans for custom ROMs. It's always useful. I would also suggest trying one of the Sense 6 ROMs. They are all amazing.
Sent from my One using Tapatalk
S-OFF is necessary for some ROMs to work, although I'm not sure about Viper. Use firewater.
greywolf928 said:
S-OFF is necessary for some ROMs to work, although I'm not sure about Viper. Use firewater.
Click to expand...
Click to collapse
I am very sorry I know this is a slow response. So I tried to first root my phone so I could use firewater but I ran into issues. First, I tried to place supersu on the internal hard drive via windows but when I rebooted into recovery I was not able to find any of the folders I had access to. So i tried using side load but got errors that I could not mount cache and could not mount system. Do you have any suggestions on how to proceed?

[Q] Did CM installer brick my phone?

Soft brick after CM installer
Hi guys, I could really need some help here. I tried the Cyanogenmod installer and everything went fine, except my phone was stuck in
bootscreen for too long time (never booted).
In CWM recovery I did a factory reset/wipe, reboot, but to no avail; still stucked on CM bootscreen.
I then tried to flash CM11 by recovery sideloader. This goes to 100% and recovery says "Installing update", but nothing happens.
Is it supposed to install and finally reboot by itself, or should I do something?
I tried to installed zip from SD-card, but got "E:Can't mount /sdcard". I guess that means that I can't push the .zip over ADB to /sdcard
either.
What else can I try?
Edit: I wiped /data and then I could suddenly push the .zip to /data/media and the, finally flash the .zip from sdcard!
Why on earth the installer didn't wipe everything from the beginning, I don't get...
Did I miss anything obvious about the wiping thing?
A factory reset should do the trick normally. But if you ever get a message that you can't mount something you have to wipe that partition in recovery. I haven't used CWM in a long time. I prefer twrp as a recovery these days
Sent from my HTC One using XDA Premium 4 mobile app
Thanks, I'll remember that, should it ever happen again. What's the benefit for TWRP over CWM?
in Htc One i always had this problem.
I'm pretty sure you will never be able to mount SD
but its not a big problem since you can still sidepush the zip file.
and to be honest there is not much difference between TWRP and CWM . its a matter of preference.
On my Htc one i always used TWRP but on other android devices for some reason i sticked with CWM.
Ayman.y88 said:
in Htc One i always had this problem.
I'm pretty sure you will never be able to mount SD
but its not a big problem since you can still sidepush the zip file.
and to be honest there is not much difference between TWRP and CWM . its a matter of preference.
On my Htc one i always used TWRP but on other android devices for some reason i sticked with CWM.
Click to expand...
Click to collapse
Unfortunately, I was not able to sideload the image, the transfer went well, the phone said "Installing update" but nothing happened!
sblar said:
Unfortunately, I was not able to sideload the image, the transfer went well, the phone said "Installing update" but nothing happened!
Click to expand...
Click to collapse
i guess u will have to install back the official ruu and after it add the rom u want to flash on the sd card and flash it ...
let me know if it works with you.
GL
Ayman.y88 said:
i guess u will have to install back the official ruu and after it add the rom u want to flash on the sd card and flash it ...
let me know if it works with you.
GL
Click to expand...
Click to collapse
Post 2 implies op was able to flash the zip successfully after wiping /data.
Correct, and I could probably also have sideloaded after wiping /data...

[Solved] I think I trashed my phone... wont boot custom or stock ROM.

I recently flashed a new recovery to my phone, which went well, but when I try to flash a new ROM, it wont boot. I've tried Sensational I as well as the stock ROM, same thing happens with both. I have done all the correct steps as far as I can tell. Factory reset, flash ROM, flash Gapps, flash boot.img, reboot. It simply doesn't work. I've tried to download other ROMs but its not possible, they all are no longer on the server at the link presented. I have even reformatted /system and /data as all the available types. ext2/3/4 and fat, same results on each. I have re-flashed everything many times and I'm starting to lose hope. Nothing works at all. I don't get any error messages in TWRP besides "Kernel does not support reading SELinux context", which isn't red text so I think its a warning or info. Sorry for quick rushed post, I had written out a much longer more detailed one, but I lost it all when I tried to preview it. If anyone wants more specific information, just ask. I'll do my best to supply anyone with any information about the problem.
images
Edit: I stumbled across the solution... My phone had S-ON which didn't seem to allow me to flash boot images from recovery. Flashing the boot.img from fastboot on my PC solved the issue.

Categories

Resources