Flash w/out sdcard? - G1 Q&A, Help & Troubleshooting

May have been asked before, but I tried searching and didnt find much luck.
I think my SDCard slot finally gave up, it just will not be read (tried two different 8gb cards that both worked fine on the computer). On Cyan 4.2.9.1.
Anyway, is there a way to flash the phone without the sdcard? I was trying to think how that would be possible, but I think its not right?
Just looking for a quick def. answer so I can know if i need to go phone hunting . Or do something different , which would be much better.
Appreciate it .
Happy holidays btw

You should be able to using ADB, not sure the command lines for that. As well, you might want to try getting a can-o-air and blowing out the SD card slot on your phone.
Lastly, this is the wrong section, should of been posted in Q&A.

pjcforpres said:
You should be able to using ADB, not sure the command lines for that. As well, you might want to try getting a can-o-air and blowing out the SD card slot on your phone.
Lastly, this is the wrong section, should of been posted in Q&A.
Click to expand...
Click to collapse
I didnt really think of adb, yeah that might work. Maybe someone knows them?
Maybe
adb shell recovery flash location/zip ?
Tried the canned air, didnt change. Good thinking though.
And lastly, I did debate which place, but I was thinking I saw a utility here or I am looking for the command lines and thought maybe alittle more technical than a general question? It will fall shortly anyway (hopefully after the commands ) or get moved/deleted.

If someone nandroided, they could just send you their system.img and you could fastboot it onto the phone. Provided you have the engineering/danger SPL.

persiansown said:
If someone nandroided, they could just send you their system.img and you could fastboot it onto the phone. Provided you have the engineering/danger SPL.
Click to expand...
Click to collapse
Thats a pain, and I dont think there are many of those out there...
No adb commands? Ive been searching but it seems scarce
EDIT:
Ok I tried my idea anyway,
adb shell recovery flash update.zip
And it just hangs (no errors though)...probably missing something?

Are you able to warranty your phone for the bad SDCard Reader??
If so, I started this thread and came up with an answer, but it will bring you back to fully stock cupcake
http://forum.xda-developers.com/showthread.php?t=560254

Search for a webpage , how to root/flash/hack g1. It's has everything you need.
You need to go into fastboot
Fastboot update update.zip. somthing like that or do like the website shows 1 at a time.
There might be an adb for it, but I've never used it. Fastboot only option I believe.

bildo said:
Search for a webpage , how to root/flash/hack g1. It's has everything you need.
You need to go into fastboot
Fastboot update update.zip. somthing like that or do like the website shows 1 at a time.
There might be an adb for it, but I've never used it. Fastboot only option I believe.
Click to expand...
Click to collapse
That is the better answer, thanks for continuing. If you just left that first sentence I would have said re-read my problem, I cannot use my sdcard (the normal way rom is flashed).
As for the fastboot, I will look into that. I appreciate it, thanks.

Im getting
No android-info.txt
No android-product.txt
In the package when i try to do this command while in fastboot:
fastboot update update.zip
I found android-info in the update file from htc, but I cannot resign right now. Im also guessing it will still yell about the android-product.txt anyway, so any ideas where to get that file?

If all you're trying to do is flash a .img (system.img, userdata.img, recovery.img) and you have a developer, or hardspl, you can flash using fastboot.
Code:
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
flashing an update.zip is only possible through recovery mode, but can still be accomplished using the /cache partition
Code:
adb push update.zip /cache
and you should be able to do the update from cache.

haykuro said:
flashing an update.zip is only possible through recovery mode, but can still be accomplished using the /cache partition
Code:
adb push update.zip /cache
and you should be able to do the update from cache.
Click to expand...
Click to collapse
Using you're SPL, is it still possible to place an update.zip into /cache with the partition table having been re-written??''
I'm assuming yes, since you jumped in and posted that method, I was just curious

jackslim said:
Using you're SPL, is it still possible to place an update.zip into /cache with the partition table having been re-written??''
I'm assuming yes, since you jumped in and posted that method, I was just curious
Click to expand...
Click to collapse
Well you're cache partition should have 30720K (about 30MB)
the last cyanogen rom was 37 MB =[
my other recommendation for you is to push the updates to your sdcard through your phone. (just re-read your post and noticed the SD card is functional in your phone)
Code:
adb push update.zip /sdcard/update.zip
then just proceed as usual.

@theslam08
Your signature say's your using the "Danger SPL" Judging by that you could reflash your spl from fastboot to the hard spl
Code:
fastboot flash hboot spl.bin
Then use the method described above by Haykuro pushing updates to /cache with adb

Thanks for the responses guys .
As for pushing to sdcard while in phone, thats where the problem remains. The sd reader IN the phone is busted it would seem as it just says no sd card found (cannot mount) with 3 different cards I tried (all working on the computer).
Ok so if I flash back the spl will I have more than 40mb free on the cache partition? Because yeh, the most recent update from CM is ~40mb, so it wont fit currently.
ANd once pushed to /cache, how would I go about doing the actual update? You said "you should be able to do the update from the cache part.), not sure how, just give the location?
console: flash update /cache/update.zip ?
Thank you.

theslam08 said:
Thanks for the responses guys .
As for pushing to sdcard while in phone, thats where the problem remains. The sd reader IN the phone is busted it would seem as it just says no sd card found (cannot mount) with 3 different cards I tried (all working on the computer).
Ok so if I flash back the spl will I have more than 40mb free on the cache partition? Because yeh, the most recent update from CM is ~40mb, so it wont fit currently.
ANd once pushed to /cache, how would I go about doing the actual update? You said "you should be able to do the update from the cache part.), not sure how, just give the location?
console: flash update /cache/update.zip ?
Thank you.
Click to expand...
Click to collapse
i forgot the exact command to force a boot-recovery and have it flash through cache (the traditional method)
but if your on cyanogen's recovery you can do
Code:
adb shell mount -t yaffs2 /dev/block/mtdblock4 /sdcard
this should mount cache into /sdcard, allowing you to flash.

haykuro said:
i forgot the exact command to force a boot-recovery and have it flash through cache (the traditional method)
but if your on cyanogen's recovery you can do
Code:
adb shell mount -t yaffs2 /dev/block/mtdblock4 /sdcard
this should mount cache into /sdcard, allowing you to flash.
Click to expand...
Click to collapse
Excellent, that seemed to be the trick (after going back to HSPL because yeah, I didnt have enough room with haykuro's). Though some bugs with that.
I got it to copy once after making that partition mount, and I was able to see the update file. I updated, and everything went well (even though I wondered how in the middle of the update it says formatting cache, yet it still worked).
Now, I went to put on a theme file and it says out of room. I hit 'update from sdcard' in recovery and it says E: No zip files found or something like that, just no files. So if it gets 'wiped' how is there no space? Is there a manual format I should do?
And I dont think this has happened to anyone yet, so thanks for going through this , im sure others down the road will find it helpful.

Not to get off-topic or picky about anything, but having the phone without an SD card being able to be read seems kind of pointless.
After all, you won't be able to run A2SD, or move the cache. The phone's going to run as if it was "stock."

akapoor said:
Not to get off-topic or picky about anything, but having the phone without an SD card being able to be read seems kind of pointless.
After all, you won't be able to run A2SD, or move the cache. The phone's going to run as if it was "stock."
Click to expand...
Click to collapse
Not being blunt but, thats the point. I have 'no' other choice right now, I cannot get a new phone for a while (and warranty is over, its a yr and 3 months since pur)
I obviously know I cannot use A2SD, so I need to get it to run 'stock', and thats proving to be a trick (stock but not). I almost have it, but cache doesnt seem to wipe on its own, which is the new problem. Once that is cleared, then I should be all set .

theslam08 said:
Not being blunt but, thats the point. I have 'no' other choice right now, I cannot get a new phone for a while (and warranty is over, its a yr and 3 months since pur)
I obviously know I cannot use A2SD, so I need to get it to run 'stock', and thats proving to be a trick (stock but not). I almost have it, but cache doesnt seem to wipe on its own, which is the new problem. Once that is cleared, then I should be all set .
Click to expand...
Click to collapse
Ah, okay - now it makes sense. I didn't understand the purpose at first.

Related

[Q] Install ROM without SD Card

Ok so the SD card slot on my phone is toast. Is it possible to install a rom thru the USB cable without using the SD card? =/
Hmm... Ok I have two ideas that i'll quickly check out. One of which will require you to wipe your data/factory reset in recovery, the other if I did get it to work wouldn't require any wiping unless you wanted to.
I'll try 'em both out and tell you if I have any luck doing so
Alright, so here we go..
Results
First idea without having to wipe: no go
Second idea with wiping: WORKS
After doing some digging around the AmonRA github to look for the commands it actually performs while in recovery I figured out exactly how to do what I wanted.
(namely THIS PAGE for those of you who are interested in seeing the exact page I found them on)​
How to Flash a ROM Without an SD Card
Prerequisites:
Flash an Amon_RA recovery if you're using Clockwork - I recommend Darch's unofficial (refer to my signature if you need it)
Access to a computer that had AndroidSDK tools on it - you'll be using ADB
Put whichever ROM.zip you want to flash in your android-sdk\tools folder - I would rename it to something simple. (My example which I'll be using for this tut is: C:\AndroidSDK\toosl\kyoukoROM.zip)
Directions:
Reboot into the Amon_RA recovery
Wipe data/factory reset, cache, and dalvik via the recovery menu
Open up cmd/terminal on your computer
Navigate to your android-sdk\tools directory
Enter the following in cmd/terminal:
Code:
adb shell
mount data
*wait a second or two* You may or may not get the "/ #" line returned.
Despite what happens press "Ctrl+C" to break the command and get back to the standard AndroidSDK\tools> directory
Enter the following in cmd/terminal:
(replace "kyoukoROM.zip" with the name you're using)
Code:
adb push ./kyoukoROM.zip /data/
*this will take anywhere from 30sec to a min depending on the rom.zip size*
Then we do this in cmd:
Code:
adb shell
recovery --update_package=DATA:mau5.zip
Wait for it to finish flashing/updating
Reboot
ENJOY
If someone thinks I should post this in the development section as a [GUIDE] let me know and I'll post it there too
Yup I think so marking as a fav this is good knowledge thanks for the post
Root-Hack-Mod-Always™
Post it! This would be a HUGE help to people
Sent from my HERO200 using XDA App
Great work Kyouko! If not to the dev forum, atleast post it to the wiki.
BTW, you should post it to Android forums, as well... if I am not wrong, this will work with any phone.
andythegreenguy said:
Great work Kyouko! If not to the dev forum, atleast post it to the wiki.
BTW, you should post it to Android forums, as well... if I am not wrong, this will work with any phone.
Click to expand...
Click to collapse
Good idea, hopefully it'll help a lot more people there. I'll post it there and change up a couple things (the darch recovery part)
And idk how to edit the wiki
Amazing response! I will have to give this a try thank you!!! I still have a month left before my upgrade and I wanted to be able to change my ROM. Thanks again!
FYI Rom Manager will not flash a clockwork recovery without an SD card, gives an error... looking into other ways to flash a recovery...

1.31.651.2 ruu?

Does anyone know when the new ruu for the HTC One comes out? I went to unroot my phone, locked the bootloader, and went to run the ruu, only to realize I did the system update a few days before. So now I'm stuck in a bootloop and I can't mount my sd card ( I think it's corrupted ) So I'm pretty much out of a phone till then, correct?
Thank you in advance guys.
If you can unlock again, and somehow get adb to work, you can s-off using revone. Then you can flash any RUU. Otherwise, I dunno
Sent from my HTCONE using xda premium
propjockey said:
If you can unlock again, and somehow get adb to work, you can s-off using revone. Then you can flash any RUU. Otherwise, I dunno
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
I re-unlocked the phone again but I have no clue how to do the rest.
If you can get files to your sd, you can run revone or moonshine to get s-off. Look in original development for the corresponding threads and instructions. Once you have that, you can RUU old firmware or unsigned.
Sent from my HTCONE using xda premium
I can't mount my internal storage. Even in TWRP recovery it shows nothing on the sd card. I think some how the internal sd card got corrupted, so I can't mount it.
Chloroform said:
I can't mount my internal storage. Even in TWRP recovery it shows nothing on the sd card. I think some how the internal sd card got corrupted, so I can't mount it.
Click to expand...
Click to collapse
I'm having a similar problem and need some help too!!
tx_jaycee said:
I'm having a similar problem and need some help too!!
Click to expand...
Click to collapse
I think the only thing that will fix our problem is a new version of the ruu. I knowledge on adb is very limited, I'm sure someone that knows what their doing can fix it 1,2,3, but that person isn't me. :crying:
ADB should not be your tool of choice. Fastboot would be your friend here, since it's a lot more direct in its method. If your internal card isn't completely hosed, you should be able to restore using the fastboot flash commands to reflash your /system and /boot and /recovery, at which point you should be fine. There are several threads on how to do this.
Rirere said:
ADB should not be your tool of choice. Fastboot would be your friend here, since it's a lot more direct in its method. If your internal card isn't completely hosed, you should be able to restore using the fastboot flash commands to reflash your /system and /boot and /recovery, at which point you should be fine. There are several threads on how to do this.
Click to expand...
Click to collapse
Can you point me in the right direction?
I tried the all in one kit, tells me device not found. I know it's found by my computer, it's in the device manager, plus I hear the noise that confirms a device is found. I can reboot my phone thru the all in one kit. I think it's best to wait for the newest ruu in my case.
Chloroform said:
Can you point me in the right direction?
Click to expand...
Click to collapse
Download the image of your choosing from this thread: http://forum.xda-developers.com/showthread.php?t=2368907.
Download TWRP 2.5 from this thread: http://forum.xda-developers.com/showthread.php?t=2236620.
Put your phone into fastboot mode (power + volume up + volume down). Plug the phone into your computer.
Install fastboot/ADB. You may need to search the web for the platform tools, or there are some toolkits that can help.
Open a command prompt and run "fastboot flash recovery <path-to-recovery.img>".
Go to Advanced -> ADB sideload, then run "adb install <path-to-downloaded-image.zip>".
If that doesn't work, open the zip and run:
fastboot flash system <path-to-system.img>
fastboot flash recovery <path-to-recovery.img>
Bottom line is if you're not willing to learn a bit about fastboot and ADB, then you shouldn't be using a toolkit because you won't be able to fix your device if something goes wrong.
So I pretty much tried everything with no luck BUT I flashed the boot.img and now I'm getting some where. Now it's showing my internal storage but the rom I had installed I guess erased. I've been searching around people saying flash system.img but how can I flash a system.img? All the files I've been finding are .zip and there any .img roms that I can flash?
Chloroform said:
I can't mount my internal storage. Even in TWRP recovery it shows nothing on the sd card. I think some how the internal sd card got corrupted, so I can't mount it.
Click to expand...
Click to collapse
I've had this problem. To correct it, I put everything I need to flash in /sdcard/0. TWRP sometimes only sees stuff within a 0 folder placed inside root.
If you haven't tried already, make a 0 folder on the sdcard, then copy it and see what TWRP shows.
Thank you to @Indirect for fixing my problem.
Chloroform said:
So I pretty much tried everything with no luck BUT I flashed the boot.img and now I'm getting some where. Now it's showing my internal storage but the rom I had installed I guess erased. I've been searching around people saying flash system.img but how can I flash a system.img? All the files I've been finding are .zip and there any .img roms that I can flash?
Click to expand...
Click to collapse
In the future, try extracting your downloaded .zip files.
OTA packages and recovery-flashable ROMs are provided as .zip files. Each archive contains the necessary .img files and a script that tells the recovery where to put them. You can extract these .img files and flash them with fastboot if you don't have recovery access.
Fastboot factory images generally are .img files compressed as .tar files. You'd better have a tool like 7zip onboard so you can deal with the many archive formats you'll find on the net.
Closed per OP request

Bootloop after CM install. Won't restore backup, mount /data, flash stock

Hi developers. I am sorry for posting this. I spent the last week trying to solve it by myself with no hope. This is my second time installing something on a phone, but it is my only phone, so I beg anyone for a help...
-What I did:
Some days ago I downgraded to this ROM C5503_10.1.1.A.1.310_GLOBAL-LTE.ftf to use DoomLord rooting script. I did it with flashtool for linux and I applied his .bat step by step in the terminal since windows would not detect my phone.
It worked. I had root for some days, but I was still annoyed by sony default android. So I decided to install Cyanogenmod.
I unlocked the device with sony official system and wen't straight to this instructions, before the first reboot
wiki.cyanogenmod.org/w/Install_CM_for_yuga
I booted succesfully in CWM, followed everything as it says there. But that's where weird things happened:
-The problems:
-The backup
I tried, it wouldn't mount /sdcard. Since I don't understand much about this, I thought it was normal. The next choice was sdcard1, I backed up there. Or so I thought...
-The factory reset
I factory reset, again, not mounting sdcard. Here is the message that shows when I try this now:
can't mount /data!
Error mounting /sdcard.android_secure
Skipping format...
Data wipe complete.
Since it said it is complete, I went on installing the zip file from my sdcard1. Both CM 10.2.1 (dogo, the right one for my phone) and the appropriate GAPPS.
Now it loops on the CM loop animation and I have to remove the battery...
-The restore problem
It still boots on the recovery mode. So I tried recovering my backup from sdcard1. But the image name is 1970.01.01.00.03.16. And it says "md5 mismatch"
I tried flashing again the stock rom with flashtool. The proccess goes on but nothing happens. I still have CWM and the boot loop.
I read elsewhere someone with a similar problem who solved using sony "emma" software. I installed it, it won't even recocnize my phone.
It recocnizes that there is a phone, but don't know which one.
But that has alway been the case with windows. I haven't been able to do anything in windows other then accessing the sdcard (when the phone worked).
Is there something I can do? I imagine that somehow, for some reason, the /data and /sdcard partitions got corrupted. I imagine I would need to repartition this and install again, but I have no idea how this happens on phones...
I can mount /system /cache and /storage/sdcard1. just /data I can´t. Says "error mounting /data"
This is my only phone and a vey recent $400 thing. I was very stupid to do that withouth a replacement and really need this phone. I greatly appreciate any help...
I found this post forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/ searching the internet. Is it possible that this would solve my problem? or would it finish bricking the phone?
Here's what you'll need:
Working recovery, basic knowledge of adb & the shell
Parted (download here)
stock PB31IMG.zip
Note also that I had run unrevoked forever (so my phone was S-OFF) ... I'm not sure if that's required or not.
So, grab parted from the link above. Now you need to extract the individual binaries from the .zip (the 6 files in the sdparted folder within the zip), ideally to your android-sdk\tools directory. Now push all 6 files (adb push [file] /sbin/). Next, we need to make them useable, so go into the shell (adb shell). Change to your /sbin/ directory, and run: chmod 0755 <file> on each of the 6 files.
Now, we need to fix the partitions. This is assuming that the partitions are there, just the wrong format (which is what happened to me .. I accidentally made them FAT32 instead of ext). So, run the following: parted /dev/block/mmcblk0 mkfs ext2. It will ask if you want to continue, hit yes. When it asks for the partition number, enter 1. Next, when it asks for the format, enter ext2. Let it do its thing. Now, once it's done, run parted again. This time, enter partition 2 (everything else is the same).
Click to expand...
Click to collapse

Error mounting data and cache

Hello Everyone
I have run into an odd problem. My tf701 ran out of power while I was watching netflix on it. After that it got stuck on boot. When I tried to fiddle using CWM I found out that I cannot mount data or cache. Further more I get to see 5 lines of "E: can't mount /recovery/*" where * are folders within /recovery/ . I tried to format system using CWM or fastboot, they both say they succeed but when I reboot I still get my bootanimation. At this I am out of ideas as to how I can fix it. Furthermore thanks to being unlocked I lost my warranty .
Any suggestions as to how I can fix it?
devbro said:
Hello Everyone
I have run into an odd problem. My tf701 ran out of power while I was watching netflix on it. After that it got stuck on boot. When I tried to fiddle using CWM I found out that I cannot mount data or cache. Further more I get to see 5 lines of "E: can't mount /recovery/*" where * are folders within /recovery/ . I tried to format system using CWM or fastboot, they both say they succeed but when I reboot I still get my bootanimation. At this I am out of ideas as to how I can fix it. Furthermore thanks to being unlocked I lost my warranty .
Any suggestions as to how I can fix it?
Click to expand...
Click to collapse
Maybe I saw something like this I dont know. Did you try mounting system first and see if that fixes it? I have no idea.
EDIT: from CWM I mean. I had a situtation where some things would not mount. data being one of them.. Not sure what else. Then I just mounted /system and everything was ok. Could it be that for some reason system is not getting mounted and you not formatting it besides an empty directory.
YayYouFixedIt said:
Maybe I saw something like this I dont know. Did you try mounting system first and see if that fixes it? I have no idea.
EDIT: from CWM I mean.
Click to expand...
Click to collapse
Yes I tried no luck. When I try to format /data using fastboot it simply hangs both the device and the terminal too.
devbro said:
Yes I tried no luck. When I try to format /data using fastboot it simply hangs both the device and the terminal too.
Click to expand...
Click to collapse
some corruption seems to have occurred.
perform a hard reset in the 'stock' recovery (this will format /data).
then boot in and re-setup. any userdata you had will be gone (including media/content stored locally, etc.).
in case of /system corruption (after performing the above; you still cannot boot in), you can format that partition separately and re-flash it from the CWM file for the latest posted stock update.
you can find file(s) on droidbasement, as needed.
I belive I have the same probleme, how i could i do it right?
devbro said:
Yes I tried no luck. When I try to format /data using fastboot it simply hangs both the device and the terminal too.
Click to expand...
Click to collapse
How did you try to format data in fastboot??
That's done in recovery afaik.
nero0345 said:
I belive I have the same probleme, how i could i do it right?
Click to expand...
Click to collapse
What problem do you have? /data not mounting? Format it in recovery but you will loose everything stored on your internal SD.
I finally took my tablet in for a check with asus. They said that I ahve corrupted my boot and since I replace the recovery there is no way to fix it. the only way to fix it is to replace the motherboard at this point. It will cost 190$ to replace!!!!
Just as an update to the future readers. I ended up replacing my logic board inside using one that I got from ebay. My tablet now works just as new. As per advice of the Asus tech, DO NOT FLASH a new recovery. If anything goes wrong the original asus recovery is the only way to fix things.
devbro said:
Just as an update to the future readers. I ended up replacing my logic board inside using one that I got from ebay. My tablet now works just as new. As per advice of the Asus tech, DO NOT FLASH a new recovery. If anything goes wrong the original asus recovery is the only way to fix things.
Click to expand...
Click to collapse
I beg to differ....
The stock recovery can only flash firmware signed by Asus and perform some crude wipe operations.
With a custom recovery you have way more tools at hand to fix problems:
You can wipe or format partitions selectively
You can take nandroids and restore them
You can check the integrity of file systems on partitions
You can fix permissions
You can flash SuperSU, custom roms and more
Some have a build in file manager allowing you to move data off the tablet even if it doesn't boot anymore
Some have a build in terminal you can run commands from.
The list goes on...
But sure - you have to do all of the above including flashing the custom recovery correctly or you can seriously damage your device like you did.
I am really sorry that you lost your mainboard and had to buy a new one, but don't kid yourself: It was not the custom recovery damaging your tablet. It was you...
berndblb said:
I beg to differ....
The stock recovery can only flash firmware signed by Asus and perform some crude wipe operations.
With a custom recovery you have way more tools at hand to fix problems:
You can wipe or format partitions selectively
You can take nandroids and restore them
You can check the integrity of file systems on partitions
You can fix permissions
You can flash SuperSU, custom roms and more
Some have a build in file manager allowing you to move data off the tablet even if it doesn't boot anymore
Some have a build in terminal you can run commands from.
The list goes on...
But sure - you have to do all of the above including flashing the custom recovery correctly or you can seriously damage your device like you did.
I am really sorry that you lost your mainboard and had to buy a new one, but don't kid yourself: It was not the custom recovery damaging your tablet. It was you...
Click to expand...
Click to collapse
When I talked to the tech at their center, there is apparently some special actions that only their recovery can do. These actions are those that allow changing boot table and other low level functions of the tablet which has nothing to do with the built-in memory or system files.
If I did not replace the recovery, then the repair by asus would have only cost 40$.

I might need some assistance. (EVA-L19)

After unlocking the bootloader, installing TWRP recovery and rooting my phone with SuperSU (v2.82), I was preparing to install a custom ROM (more specifically the Resurrection Remix 7.1.2.) all in all, things ended up going out of hand and I accidentally deleted my internal storage, losing every single bit of my existing ROM, not to mention the RR ROM file as well. Now when I try to wipe, I can't, it usually says "Failed to mount '/data' (Device or resource busy) and "Unable to mount storage".
I tried using ADB sideload but to no success, only the same message. What I can understand is that the previous data is gone, I tried changing the format of data, system and cache to FAT & exFAT but it still did not resolve my issue.
I'm out of options here, I don't want to have to give up this phone because of my stupidity.
I also tried flashing the LineageOS 14.1 ROM to see if anything was different, here is what it said:
Installing zip file '/sideload.package.zip'
Target: HUAWEI/EVA-L09/HWEVA:7.0/HUAWEIEVA-L09/C432B361:user/release-keys
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
detected filesystem exfat for /dev/block/bootdevice/by-name/userdata
mount: failed to mount /dev/block/bootdevice/by-name/userdata at /data: Device or resource busy
unmount of /data failed; no such volume
Patching system image unconditionally...
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
Script succeeded: result was [1.000000]
Although it said succeeded it clearly did not work and I am sitting without a ROM. I'm not smart when it comes to these things please help a guy out.
(Is there a way to going back to completely stock EMUI 5.0?)
Cheers.
EMUI 5.01 requires encryption, which you obviously removed.
Search for DC Unlocker, it can probably fix it for 25 Euros
zgfg said:
EMUI 5.01 requires encryption, which you obviously removed.
Search for DC Unlocker, it can probably fix it for 25 Euros
Click to expand...
Click to collapse
I know this is awkward to ask and all, but how exactly do I go about this, I'm pretty lost and I have minimal experience with this stuff..
I never had to use it but here is their portal (with download info, prices, instructions, etc)
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
If you search on XDA or search on Google for eg XDA Huawei DC Unlocker you will find threads with first hands experience (I've seen them several tines but didn't save to Favorites)
zgfg said:
I never had to use it but here is their portal (with download info, prices, instructions, etc)
If you search on XDA or search on Google for eg XDA Huawei DC Unlocker you will find threads with first hands experience (I've seen them several tines but didn't save to Favorites)
Click to expand...
Click to collapse
I'm terribly sorry for being THIS stupid. As I'm looking into this even more, I'm conflicted about the credit amount I need, been scrolling through the list and I can't really find my problem involving firmware I suppose.
People usually buy for 15 Euros. It may help you, Chrome will automatically translate from German
https://www.android-hilfe.de/forum/...-wiederherstellung-mit-dc-phoenix.818669.html
I'm not educated about DC Unlocker but that is NOT neccesary here. You can easily repair the /data partition by flashing the stock recovery via fastboot, formatting data with that stock recovery and then flashing TWRP again. After that TWRP should be able to read the data partition again.
You can easily go back to stock completely and even restore your bootloader by doing a "rollback" to Android 6. (dload method). After that you can normally upgrade from there though EMUI to the latest version of stock.
christopherpfister said:
I'm not educated about DC Unlocker but that is NOT neccesary here. You can easily repair the /data partition by flashing the stock recovery via fastboot, formatting data with that stock recovery and then flashing TWRP again. After that TWRP should be able to read the data partition again.
You can easily go back to stock completely and even restore your bootloader by doing a "rollback" to Android 6. (dload method). After that you can normally upgrade from there though EMUI to the latest version of stock.
Click to expand...
Click to collapse
I've tried using eRecovery to format the data but to no success, I can't even use the touch screen for some reason, (I know about the volume keys, but when it comes to selecting the Wi-Fi, there is no success whatsoever). If you do know a fix for this, could you possibly walk me through this?
Hexagonal said:
I've tried using eRecovery to format the data but to no success, I can't even use the touch screen for some reason, (I know about the volume keys, but when it comes to selecting the Wi-Fi, there is no success whatsoever). If you do know a fix for this, could you possibly walk me through this?
Click to expand...
Click to collapse
UPDATE: I flashed the stock recovery image and it showed me the wipe cache partition and factory data and system reset, I tried both, only the cache one succeeded, the other one failed. I saw a post that directed you to flash boot.img, recovery.img, recovery2.img and then system.img, I did that, but I couldn't boot into my phone - the good thing is however! That I can use my touchscreen in the recovery now.
Obviously the second time booting into EMUI recovery it prompts me to 'Download latest version and recovery', I try to connect to my Wi-Fi, seems okay but then it suddenly fails. More specifically it says 'Getting package info failed'. Save me please :crying:
So this "erecovery" never worked in any way for me (the one which offers you to download the latest version).
Instead you need the normal recovery you already used. Formatting failed for me the first time too, try it again and then it will try to format "low-level" which worked for me.
Go directly into fastboot from that, flash TWRP and go directly into TWRP.
After that should be able to use /data in TWRP. As soon as you are able to start TWRP without any error messages (like "Device busy" or something) go to Wipe and then format data.
Important: check which partition type you have! For EMUI you need "f2fs" and for lineage you need "ext4". You can see and change that in TWRP under Wipe -> "change or repair filesystem".
If you have any more questions, just ask.
christopherpfister said:
So this "erecovery" never worked in any way for me (the one which offers you to download the latest version).
Instead you need the normal recovery you already used. Formatting failed for me the first time too, try it again and then it will try to format "low-level" which worked for me.
Go directly into fastboot from that, flash TWRP and go directly into TWRP.
After that should be able to use /data in TWRP. As soon as you are able to start TWRP without any error messages (like "Device busy" or something) go to Wipe and then format data.
Important: check which partition type you have! For EMUI you need "f2fs" and for lineage you need "ext4". You can see and change that in TWRP under Wipe -> "change or repair filesystem".
If you have any more questions, just ask.
Click to expand...
Click to collapse
So what you're saying is, as soon as I get my data sorted and my partition set to the right one I should be able to install the custom ROM. I could use data and even formatted it, tried installing Lineage but I must've had the storage on the wrong type, now I'm back with the same issue, I'll try to fix it and post my results here. Thank you!
Hexagonal said:
So what you're saying is, as soon as I get my data sorted and my partition set to the right one I should be able to install the custom ROM. I could use data and even formatted it, tried installing Lineage but I must've had the storage on the wrong type, now I'm back with the same issue, I'll try to fix it and post my results here. Thank you!
Click to expand...
Click to collapse
Update: It did NOT work, tried flashing LineageOS through ADB sideload, it was going fine before the bar completely filled up around 50% of the way done, it said 'detected filesystem ext4 for /dev/block/bootdevice/by-name/system' and in the next line it said 'script succeeded: result was [1.000000]'
Help me, I'm begging you, at the moment I don't have an access to a microSD that has the capacity to hold the stock files to do the dload method, therefore this is my only hope.
Hexagonal said:
Update: It did NOT work, tried flashing LineageOS through ADB sideload, it was going fine before the bar completely filled up around 50% of the way done, it said 'detected filesystem ext4 for /dev/block/bootdevice/by-name/system' and in the next line it said 'script succeeded: result was [1.000000]'
Help me, I'm begging you, at the moment I don't have an access to a microSD that has the capacity to hold the stock files to do the dload method, therefore this is my only hope.
Click to expand...
Click to collapse
Whats the error? Why doesn't it work? What happens when you try to boot?
christopherpfister said:
Whats the error? Why doesn't it work? What happens when you try to boot?
Click to expand...
Click to collapse
That's what I'm trying to figure out, when I try to boot in it's just stuck on a boot loop. Unfortunate..
Remember that you have to what *a while* for the first boot. Only if you see no change after 5-8 minutes or so something is definitely wrong.
Have you checked in TWRP if your /data partition is ext4?
christopherpfister said:
Whats the error? Why doesn't it work? What happens when you try to boot?
Click to expand...
Click to collapse
christopherpfister said:
Remember that you have to what *a while* for the first boot. Only if you see no change after 5-8 minutes or so something is definitely wrong.
Have you checked in TWRP if your /data partition is ext4?
Click to expand...
Click to collapse
I know, but it was flashing the Huawei logo and the unlocked bootloader warning continuously. It was set on EXT4 but as I was saying, it said script succeeded at 50%.
Hexagonal said:
'detected filesystem ext4 for /dev/block/bootdevice/by-name/system' and in the next line it said 'script succeeded: result was [1.000000]'
Click to expand...
Click to collapse
That just said that /system partition is ext4. That is default even for stock I believe. You need to check for /data.
christopherpfister said:
That just said that /system partition is ext4. That is default even for stock I believe. You need to check for /data.
Click to expand...
Click to collapse
I deliberately set the data partition to EXT4 before installing
Hexagonal said:
I deliberately set the data partition to EXT4 before installing
Click to expand...
Click to collapse
Can you check in TWRP if it actually says /data is ext4?
Which lineage are you trying to install? Don't you need a vendor.zip for some of them?
/data is indeed on EXT4, and I was installing the one that was on the room section.

Categories

Resources