Hello
I got my HTC One S s4 a couple of days ago. It was unlocked. With the guides here I managed to root it and S-off and ass I was feeling confident, I installed Maximus HD 10 rom (I think I had android 4.0.1). I followed the instructions and I even got the error described in there.
My problem starts here:
Code:
Make sure that installation was successful and press enter to reboot device.
Device will boot in system, wait till you can see device on PC and copy ROM on internal SD card once again.
Repeat ROM installation with Aroma installer, do wipe during install.
Congratulations, you have device with fully working Android 4.2.2 and Sense 5.0
The device did boot in system and everything seems to be fine, new android and sense version, ect. I pluged it to PC, copied again the firmware.zip, went to TWRP recovery but the file isn't there. I even placed it inside a folder from root but still the file doesn't apper and that's why I can't continue witht he flashing process even though it seems that there is nothing more to do.
I could leave it like that but what if I want to try another rom some day?
In thephone I see 16 gb of storage, in windows explorer 10 gb more or less. If I mount the folders TWRP lets me, I get a device showing in windows explorer that needs to be formated and it's only 48 mb
What can I do?
thanks a lot!
Hello mate.
I second this.
I am currently having the exact same issue as described here.
I have rooted my phone, superCID, S-OFF, installed MaximusHD, flashed new firmware for MaximusHD and this is where I hit a roadblock.
It began like this:
I went to TWRP, plugged in phone, mounted it (I chose to mount Data in TWRP not SD card, as SD card could not be selected) - system was asking to format the device - I chose no, and moved over the MaximusHD rom (let's call it ROM.zip) using
Code:
adb push ROM.zip /sdcard/ROM.zip
The operation was succesful, TWRP showed the file ROM.zip in /sdcard, however, when I tried flashing it, I couldn't -> the access to SD card was blocked. I followed all the instructions in this thread:
http://forum.xda-developers.com/showthread.php?t=1630459
After this, I went back to TWRP, mounted SD card (this time it was selectable) and pushed ROM.zip onto /sdcard
The operation was succesful, and yet TWRP did not show the file in /sdcard.
Note: System does not ask to format the device anymore, but it shows only 50mb of storage. TWRP also confirms 50mb (47mb, to be exact)
I repeated the process, same result.
I tried to boot into system using TWRP -> reboot -> system, the phone restarts and hangs on HTC One screen.
To try something else, I went into bootloader and locked it using
Code:
fastboot oem lock
The device restarted into system, once again went into HTC One screen but this time, after a couple of seconds began optimizing apps.
A system launched. Weird, considering firmware update supposedly wiped everything off the phone, not even mentioning all the resets and wipes I did by following the thread I posted earlier. I went through first launch steps and was now in a fully functioning MaximusHD system, the one I installed the first time.
The device connected to PC easily and now it showed full storage size, with all the folders and structures inside.
Inside I found two icons which surprised me. They looked like two 0 bytes empty partitions that could not be double clicked or deleted (upon deletion system throws an error that device might have been disconnected). I tried to move ROM.zip onto there, after it finished, instead of ROM.zip now there were three 0 bytes empty partitions. This is when it struck me - my 2 previous attempts to bring ROM.zip onto /sdcard with adb push are those two partitions that were already there. I unplugged and plugged my device back on, the partitions disappeared and ROM.zip showed up.
I went back into recovery and it still showed 50mb storage size and nothing inside SD card (nothing other than two folders, TWRP and .android_secure).
I rebooted the device into system and it hung up on the HTC One screen. I unlocked my bootloader and locked it again using
Code:
fastboot oem lock
and was able to return to system. Somehow, locking my bootloader lets my device get past the HTC One screen. However, the system started fresh again so I lost all the apps that were meanwhile installed (a file manager) and all settings. I went through the process and was back into working system. This is the moment where I am now, confused as to what to do next.
I went into my file manager which I got from Play Store again, which showed the entire folder structure. When I pressed back to go into the root, I was surprised to see that I actually wasn't in /sdcard.
Right now, the exact same folder structure seems to be located in four places on my phone:
/storage/emulated/legacy
/storage/emulated/0
one of these two were on default in the File Manager,
also found one here:
/storage/sdcard0
and also in:
/sdcard
My theory is that the file system in /sdcard gets wiped every time the phone is restarted and somehow brought back fresh onto /sdcard, but it doesn't make much sense and doesn't explain why TWRP shows completely different paths.
I also flashed TWRP to the newest version, to no result.
I fixed my own issue 5 minutes after posting this response...
I skipped the point where you have to install TWRP that is given in the Install Package in RUU mode. This was the root of all problems.
Reflash your firmware, following the instructions here: http://forum.xda-developers.com/showthread.php?p=45621060 (post 68).
What a way to waste 5 hours just because i thought I don't need TWRP because I already had it installed.
Good luck on your issue.
Related
i have a odd issue.
Last night the MIUI 1.10.7 ROM froze up with trinity kernal. After the reboot trinity kernal on boot screen kept freezing.
I did a full whipe re-installed MIUI 1.10.7 flashed nertchy and i was good to go.. once booted up as apps where getting restored from the market random crashed started and now everything force closes.
that is not the issue.. the issue is that i want to do a full whipe again.. how ever i can not do anything with sdcard. i have tried every possible format method and coping files to sdcard...
all it ends up is restoring the files and the file that i have copied to sdcard is gone wth :S
i can boot the system back to what it was even when i re-flash it over again still same system there trying to download files and crashing..
i have reached the end i dont know what it possible could have changed :S
help?
You could try and lock the bootloader and unlock it again. That might reset everything and get it working for you again. I had a problem with the SD card and I wasn't able to mount it in CWM to access any files so I locked and then unlocked the bootloader and everything has been working great again
no go.
earlier i tried pushing some files to sdcard using adb successfully. this only lasted until the phone was rebooted out of recovery and files where back to w/e they where before.
i pushed an filed called update.zip tried flashing.. as if i never tried.
what it seems to me like is that the whole system is preventing updates/changes to the system :S :S
no matter what i try to do to reinstall or format it goes back into its old form with exact same files and exact same problems..
basically unable to flash and delete :S:S
have you went to storage in setting menu and hit erase then erase everything?
yes,
i have tried all of the following:
- factory reset from settings
- unmounted sdcard and formatting from settings
- delete files using file explorer (deleted them but comes back on reboot)
- uninstalling application (error occurs)
- moving application to sdcard from internal storage (not enough space error occurs)
- doing factory reset using cwm
- doing individual deletes using cwm
- creating backup using cwm (error occurs, cant get chm5)
- locking/unlocking bootloader
- mounting sdcard to pc and deleting files (same thing files delete until reboot then restore)
- adb remount (remounts nothing happens)
- adb push file, i can push a file and its only there until phone reboots
- installing pushed file update.zip (miui 2.1.x) installs but still goes back to corrupted miui 1.10.7..
i don't remember what else i have tried. every time file deletes it comes back after reboot. as well as the system.
i can flash a new recovery mod and it will stick but nothing in terms of deleting files or installing new system files.
new development.. i have tried installing update.zip from fastboot menu
and this is what happens:
sending 'system' ... Okay
writing 'system' ....failed (remote: write fail)
it almost seems as if i lost all write access.. is there a way to fix this?
(fix permissions does not fix this problem)
cheers,
as the Nexus s has no actual physical SD card but it purely refers to the storage partition, I am guessing you have some how corrupted the partitions settings and possibly damaged the memory as well, i have also seen from other threads where this issue is nearly identical that the PCB board being changed fixed the problem.
sorry to say either way your Nexus S may need to go under the knife,
hmm, this was the last day i played with it...
i'll have a look tomorrow for a bussins that will take it and try to fix it
cheers, for all those who tried to help.
Today I had about 2 dozen sdcard folders that could not be read by Titanium, MyBackUp Pro, Linda Manager etc. Did nothing since a TWRP backup last nite that went fine.
Tried to wipe card to copy a bu from pc but got notification in windows of corrupted files and they would not delete. Those included the above mentioned folders. Also, no luck with trying to use TWRP to wipe card.
Didn't try Fix Permissions with TWRP as didn't think that would apply. So I unmounted card from pc, still pluged in, and selected Format SD Card icon in TWRP.
It stopped on Verifying partition sizes after it started the Formatting /sdcard sequence and has been there for over 20 minutes. So, much easier with a removable card. What would you suggest I do next. Can't take that long to format with TWRP, or can it--?
I normally use SD Formatter and it did take awhile. But, when using the recovery like AmonRa etc only a couple minutes. Obviously not a full format.
Thanks
Ken
Well, I had to back out of formatting and format with sdformatter. Then sdcard wouldn't mount so I did the clear storage method and got data back on sdcard.
Problem is now after reflashing twrp and cwm the bootloader screen still shows the "clear storage" choice. So, even though I can boot into recovery, I could not see any bu's in twrp to restore. I did in cwm and restored Zydroid 3.3.5.
I will see how it runs, but why is clear storage still an option in bootloader, I thought that disappeared with a custom recovery--maybe not??
And why no bu's showed in twrp to restore, but did in cwm-- The only thing I did different was flash twrp thru fastboot as opposed to thru Goo Mgr originally.
Two final notes then I will retry twrp soon and move on:
I don't pay a lot of attn when backing up or restoring. I did watch this time and saw cwm back up recovery as a default. Twrp has that as an option I never selected--not sure it matters--any thoughts--still trying to figure out why twrp showed no bu's when I selected restore, not even the backup folder. But, the folder showed in File Mgr.
And do you guys with custom recoveries show a Clear Storage option as is available with a stock recovery. I don't remember seeing one. If so, why flash a stock recovery to Clear Storage and get sdcard remounted--
If the Clear Storage shouldn't be there, I still may have recovery issues. Although, all good atm on cwm--
TWRP and CWM has different backups iirc, they can not flash backups made in the other.
thanks, but i may have not explained well
I understand that and it is not the issue
problem was i reflashed twrp after restoring my sdcard
when i went to restore my twrp bu thru twrp the twrp bu folder never showed, just a blank screen after tapping restore
thing is i never tried a restore with twrp, so don't know if it ever worked--
solved one issue thru experimenting
you can't change bu name that shows in file mgr. it didn't have a date and I gave it one. then it doesn't show in recovery when you select restore. I did that to give it a date. but, found out when viewed in recovery after tapping restore the date is there not the HT24HW403671 name.
saw on some guides with cwm that clear storage was mentioned, so guess it was always there and didn't notice as never used it
back on twrp and will see how it goes
one question--if you can't change bu name, how do you differentiate btw diff roms in recovery bu folder--keep only one and put rest on pc?
All Resolved--NP with the Folder Names, didn't know the dated bu's were inside the HT folder--
Hopefully no more sdcard unmounting on its own--
I'll update this incase anyone following or has or will have a similar issue
I haved tried two differnet roms Trickdroid/Axiom (have not gone back to LeeDroid yet). Have run twrp and cwm. Deleted SD Card Speed Boost. Have tried mounting thru phone and twrp.
I still get missing/corrupted sdcard folders from DCIM to Downloads and alerts of folder doesn't exist and need to reformat card. I have reformatted with sdformatter and thru phone. Will lose personally made ringtones.
I have gone back to Axioms v01s kernel from the oc vo6. I had that running at 1890 and 1809 and 1674--no help
Just fastbooted the v01 so will see
Seems like a mounting issue, but stumped--maybe card is shot--
Anyone with similar issues or ideas your comments are welcome--not at phone replacement stage yet--
I do unmount properly
running v01 kernel for a day, no issues--1512mhz
did a good backup, all ok--no lost folders
when I open two windows panes on pc to copy bu to pc from phone and backup sdcard to phone issues start
the right pane which is the phone storage pane starts to lose the Removable Disk H disk icon, which is phone. Pane flashes and goes back and forth btw showing card contents and not showing H disk. Also showed empty H folder as nothing on card. I unmounted and remounted phone to pc and all was there. Unmounted and checked card contents with phone not connected to pc--all ok
Beginning to wonder if it is usb port problem--something is losing connection and/or unmounting remounting on its own. Maybe why some folders got corrupted before--still confused--
get popups on pc occasionally that state devise can perform better on a differenet port and sometimes device icon does not show when phone plugged in. I have changed ports, on my third one that only was used for mouse, will see. I have once or twice reinstalled htc drivers--
Hola banditos, I am new here, and not really that big into android, so forgive me if I do not refer to something correctly. I am currently having multiple problems with my Asus Transformer pad. A few months ago I purchased said product and rooted it. I had a few minor issues but eventually got it working. Flash forward to yesterday night at around 10 PM, and I had wiped the system and removed the Operating system. "No problem" I thought "I can just download the Jellybean firmware from the asus website" ( I had done this before.)
I downloaded the firmware, put it on my SD card and flashed it. The only problem was that I had flashed the Japanese version of the firmware onto it.
At this point, TWRP apparently thought it would be hilarious to stop working. Upon downloading the US version of the software and loading it onto my SD card, TWRP was no longer able to mount the SD card. That my friends is the major problem.
I have checked on my computer, and the SD card is still functioning. I have went into the Japanese OS on the Android and it is still accessible and functioning. I have downloaded multiple versions of TWRP, different recovery kernels and tried multiple solutions through other threads. I have tried reformatting my SD card to EXFAT, Fat32, NTFS and regular FAT. I have tried putting the firmware on the internal SD card and loading it from there. It recognizes that the firmware is there, but fails to install it. ADB also fails to recognize the device (I have everything set up correctly on the PC but it still fails). Fastboot is working fine though.
I have crawled through web page to web page looking for a fix. About 7 hours in total, and I am yet to find one that works.
Help me out here.
My gear:
64 GB sandisk SD card
Asus tf300t running a japanese Jellybean 4.2.1
TWRP 2.6
You're my last hope
There is another way! Inside the us software zip there is another zip inside that zip is a .blob file extract it to the directory where adb and fastboot are on your pc open up command prompt and cd to your fastboot directory: now type: fastboot flash system blob
This will take some time!
Then flash twrp and open it then wipe data system cache dalvik cache and then flash the firmware via twrp reboot!
Sent from my sensational HTC Desire C
I have grabbed the blob file from the US firmware. Upon using the "fastboot flash system blob" command, I get the message < waiting for device > I have waited a half hour, and it is still there. am I doing something wrong?
Edit-
I have since got the fastboot to work after some research. When I went to wipe the data system cache and dalvik cache, TWRP said that it had failed. TWRP still failed to recognize my SD card
Edit Edit-
Again after more searching, I have found a TWRP version that has recognized my SD card. However, One problem still remains before I am finished. I am still unable to flash the stock firmware. I navigate to my External SD card in TWRP, select the firmware zip file. Almost instantly it says that the install failed. Any ideas?
Lord Cyan said:
I have grabbed the blob file from the US firmware. Upon using the "fastboot flash system blob" command, I get the message < waiting for device > I have waited a half hour, and it is still there. am I doing something wrong?
Edit-
I have since got the fastboot to work after some research. When I went to wipe the data system cache and dalvik cache, TWRP said that it had failed. TWRP still failed to recognize my SD card
Edit Edit-
Again after more searching, I have found a TWRP version that has recognized my SD card. However, One problem still remains before I am finished. I am still unable to flash the stock firmware. I navigate to my External SD card in TWRP, select the firmware zip file. Almost instantly it says that the install failed. Any ideas?
Click to expand...
Click to collapse
cant you use fastboot to flash the stock firmware?
So i soft bricked my device while trying to install the latest 4.0.1 image. I tried hard wiping the device and wipe cache partion from Stock Recovery but didn't help, still wouldn't boot. I tried installing the image in Stock Recovery from Apply Update From External SD Card, but i got a few errors first "E:Failed to map file Operation aborted", i took a look at the file and it had about 1.67gb extra in "Userdata" i tried deleting that file and reinstalling from external sd card but then i got "E:footer is wrong" "E:signature verification failed" Operation Aborted.
Now i'm trying to install update from ADB (Surprisingly if i have the tab connected and im in Apply Update from ADB the tab is recognized in ADB
Code:
adb devices
serial # sideload and i have updated the drivers) But if i try to flash the recovery file 4.0.1 (provided from the developers site [cant post links]) "i just get waiting for device"
Anyone know how to get around this issue in ADB or properly install from external sd card without getting errors?
(Alternative read to my problem posted in the Nvidia Forums 98% sure i soft bricked my device [cant post links]
Did you ever find a fix? I'm having a similar problem.
Try to use fastboot restore everything.
I can't get it to connect to fastboot. When it loads the boot loader and I try to select fastboot protocol it fails.
Wow this thing sucks! I'm really appreciating my Samsung with Odin right now! So I finally got it to connect to fastboot (don't ask me how, I don't know) unlocked the bootloader and flashed twrp. Now it won't flash supersu in adb sideload so I put it on an SD card (which now magically mounts and works now) and flashed the zip in recovery but it says at the very end of the process while trying to update the partitions that it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so which one? I have no idea which version bootloader, kernel, or os is or was on this device...
Update: I think I may start a new thread in the Q&A/Help section so that I can try to get a vast concensus. Thanks!
rom fiend said:
Wow this thing sucks! I'm really appreciating my Samsung with Odin right now! So I finally got it to connect to fastboot (don't ask me how, I don't know) unlocked the bootloader and flashed twrp. Now it won't flash supersu in adb sideload so I put it on an SD card (which now magically mounts and works now) and flashed the zip in recovery but it says at the very end of the process while trying to update the partitions that it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so which one? I have no idea which version bootloader, kernel, or os is or was on this device...
Update: I think I may start a new thread in the Q&A/Help section so that I can try to get a vast concensus. Thanks!
Click to expand...
Click to collapse
Yes flash a ROM in recovery.
Try Resurrection Remix. It'll resurrect your device
Just tried flashing bliss 6.2 and it won't get past the nvidia screen. It says it flashes successfully but I still get a bunch of "can't mount such and such partition" errors during the flash sequence. Not sure what to do, I can post pics if you guys want.
If you got/can get TWRP on there now, the advanced wipe menu will allow you to check /data for errors. As for /system, wipe it. If you get errors that e2fsck can't fix in your TWRP log, you'll have to put on your data recovery hat on. If it's that important to you, my advice is to adb pull the right file under /dev/block. You won't get a block device, you'll get an exact image of your data partition. Once it's fully pulled (it'll be 10 GB or more on a 16GB device), make a copy of it first thing, and use data recovery tools (testdisk, or if you really know what you're doing, debugfs). If you don't have anything valuable on /data (remember that any backups you took from recovery go in /data/media by default), just format that and be done with it.
Pray that there are no errors after you format everything, because that usually means your NAND is toast.
If your errors are hardware ones, you're royally screwed. Same thing happened to my Nexus 7 2013 model a year ago. Only way to use it is to flash a modified kernel that will use an attached USB drive exclusively as storage. If the NAND is toast inside the boot partiti,try replacing recovery, otherwise, you have to tether boot it (fastboot boot) every time you want to run it, unless you have the guts to try repartitioning the NAND (unlike on PCs, messing up there is an instabrick).
Since the Shield Tablet can use SD cards, you're better off. No USB drive needed.
Device: HTC Bolt (unlocked)
I installed TWRP recovery mode (an ADB method that doesn't need to root your device) to the phone because I wanted an original image backup of the device (because I basically did a command on my first HTC Bolt that made it locked and it went into SIMLock mode).
So, I used this guide:
(sadly, I am new, I cannot post a link)
https:, //www, stechguide, com, /take-twrp-backup-directly-pc-via-adb
I performed this command:
adb backup -f original --twrp --compress system cache data boot
Then sadly, I did the same thing to my second HTC Bolt and the SIMLock came back.
I booted TWRP, mounted all partitions as read/write. And performed this command:
adb restore original
Rebooted Device: HTC Boots Only to HTC Splash Screen
I am open to many solutions (webpages with tutorial/guides). I would really like to keep my device unrooted even though I already TWRPed it.
I apologize if this is miss filed, I am new to the forum so there are limited areas I can post.
Best Regards,
Jason Zouikri
[Solved] HTC Boots Only to HTC Splash Screen
Well, my goal was only to get it back to being a phone again; I am not sure of the security implications of using a third party image. I am not quite sure what's in this ROM either.
(1) I couldn't get TWRP to recognize my external SD card after I formatted it as FAT32 on Windows 10. So, I booted into TWRP recovery and formatted it there (even though it says its going to use ext3 or ext4, it formatted it as FAT32 - the log says FAT32).
(2) https://forum.xda-developers.com/bolt/development/o-sense-oemhtc-ultra-10-10-life-m9-t3729247 -- XDA post.
(3) https://www.androidfilehost.com/?fid=889964283620763979 -- downloaded from their "afh link" (android file host).
(4) On Windows, copied the zip file to the SD card
(5) Placed the SD card in the phone, booted into TWRP recovery, and chose install and the zip file on the SD card.
(6) Followed installer instructions, rebooted, and it now boots into the phone.