[Completed] [G.M. GT-S5570] Fail to set up ROM - XDA Assist

Hey good evening dude. So the story is that im failing in installing ROM.
Im here having some troubles. My first problem is :
1. The ROM I downloaded from http://forum.xda-developers.com/showthread.php?t=2622069 is kinda damage/ error. I dunno it's a real error or what.
But it shows error message like :
E:Error in /tmp/sideload/package.zip
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Note :
Before I did that, I have done the ' wipe cahce partition ' and also the ' wipe data/ factory reset '.
2. Now my phone is stuck on the blackscreen with white text " Samsung Galaxy Mini GT-S5570 ". I got no idea about what going on here, it's my first time ROM-ing. Thx btw.
3. Now if I enter the recovery mode, it shows error msg : E:failed to mount /system (Invalid argument)
Click to expand...
Click to collapse
I hope you can help me in easy way, coz im totally newbie here.

TheMD5 said:
Hey good evening dude. So the story is that im failing in installing ROM.
Im here having some troubles. My first problem is :
1. The ROM I downloaded from http://forum.xda-developers.com/showthread.php?t=2622069 is kinda damage/ error. I dunno it's a real error or what.
But it shows error message like :
E:Error in /tmp/sideload/package.zip
Note :
Before I did that, I have done the ' wipe cahce partition ' and also the ' wipe data/ factory reset '.
2. Now my phone is stuck on the blackscreen with white text " Samsung Galaxy Mini GT-S5570 ". I got no idea about what going on here, it's my first time ROM-ing. Thx btw.
3. Now if I enter the recovery mode, it shows error msg : E:failed to mount /system (Invalid argument)
I hope you can help me in easy way, coz im totally newbie here.
Click to expand...
Click to collapse
As long as you can not post in the ROM thread, you should post your question in the Legacy & Low Activity Devices > Samsung Galaxy Mini > Galaxy Mini Q&A, Help & Troubleshooting forum.
Hopefully you will get proper help there :fingers-crossed:
Could be differnt things, such as corrupt download, wrong ROM for your device, wrong recovery version, etc.
As I don't have your device and no experience with the ROM, you might get some helpful ideas in the forum I linked above.
EDIT:
As my friend @KJ has recognized, you've already posted your issue in Q&A of your device specific forum. So there's nothing we can do for you here at Assist.
We're not here for support or troubleshooting, just help navigating the site.... And you already figured out where to post.
You'll have to be patient and wait for replies.
Good luck!

Related

Stuck in a bootloop

[Deleted]
johnfocker said:
Hello everybody!
I'm posting today cause I got stuck in a bootloop when trying to factory reset from a freshly flashed Asus stock rom.
I was previously tinkering with cynaogenmod installs when I found myself facing those kind of errors:
Code:
E: Can't mount / cache/recovery/command
E: Can't mount / cache/recovery/log
E: Can't open / cache/recovery/log
E: Can't mount / cache/recovery/last_log
E: Can't open / cache/recovery/last_log
Since I was unable to flash anything from that point via recovery, I flashed the latest asus stock rom via fastboot and the tablet booted again.
Then I flashed CWM recovery to be able to flash CM11 again but I got the "Can't mount" errors again so I booted the tablet on the stock rom and tried a "Factory reset" from the Settings menu...
Now I'm stuck on this nice screen and everytime I try to coldboot the tablet I'm unable to access fastboot anymore... It boots directly to that screen and never gets past it!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I feel like I'm screwed this time... please help me ^^'
Click to expand...
Click to collapse
You should NEVER use the "Wipe Data" option from the bootloader or factory reset from Settings with a custom recovery installed! Any kind of wipe or format can and should be done from recovery.
But don't worry - you'll be fine.
The factory reset command starts the recovery and asks it to wipe the data partition. And you keep interrupting it. I've seen your scenario a number of times. Connect your tablet to a power source and let it do it's thing. Go to bed. Sleep over it. The next morning it'll most likely be finished.
And before you flash anything else, check your bootloader and recovery versions. Most likely one or both are incompatible with CM 11 or each other.
I've done the exact same thing, was in a hurry and wasn't thinking... I never usually do a factory reset from settings, I don't know what I was at. I hope your right and it will come on eventually. I can't boot to Recovery I can't boot to fastboot, nothing works... Its a nice brick at the moment. Did you ever get this sorted?
Sent from my HTC One using Tapatalk

twrp - can't install this package on top of incompatible data

i have followed all the steps using NRT to unlock boot-loader and root the phone.
Installed TWRT manager and flashed the recovery.
Now i am trying to flash CM12 for the first time and stuck with error message "can't install this package on top of incompatible data" during flashing .
downloaded the following flash zip from CM website: cm-12.1-20150901-SNAPSHOT-YOG4PAO237-hammerhead.zip (281.77 MB)
Can any one help me what needs to be done to proceed further.
i didnt wipe the data before. Now its working and closing the thread
I wiped everything on my phone via TWRP. Still getting this error!
This topic is old but in case someone else gets here I got a solution - Change /data partition filesystem to ext4 or other supported by ROM
mesaj said:
This topic is old but in case someone else gets here I got a solution - Change /data partition filesystem to ext4 or other supported by ROM
Click to expand...
Click to collapse
How did you do that?
dsarcinelli said:
How did you do that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-4/help/guide-detailed-f2fs-manual-format-guide-t3264185
This guide might help, you do it in TWRP by going to Format > Advanced > select partition > Change filesystem > Ext4
Wiping data worked for me
2sumanth said:
i didnt wipe the data before. Now its working and closing the thread
Click to expand...
Click to collapse
In twrp, I had to fumble around to find advance wipe to clear data but worked like charm after that.
Thank you!
xiaomi note 4g dior
Let me tell my story,
My friend gave me an old xiaomi note 4g which was stuck at the MI icon on boot,
Luckily the phone did not lock boot-loader
So I use xiaomi flash rom to flash global room , it worked after i tried sometimes.
Then I booted to the phone, and other problem came, the phone was linked with an Mi Account , and my friend forgot everything about it
not email, no phone number
I did a search and they said the only way to bypass the MiAccount is using a Resurrection ROM or balallala
so I ended up with using
1. fastboot to install twrp
2. open twrp --> open adb sideload mode.
3. Open window command line and install Resurrection ROM though adb sideload
While installing rom though adb slideload , i got the same issue with topic
SO i cleared data and tried again,
IT WORKED , NO MORE ****ING MiAccount
THANK a lot
:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi
Playing with my wife's Nexus 5, bootloader unlocked, rooted, and latest TWRP installed but when trying to flash from android 6.0.1 to Lineage, I'm getting an error 7 image shown I hope.....
Is this just because I haven't wiped the data first ? (I'm fairly sure but...)
I dont dare try 'cause if it's not that she'll kill me, so would like to be sure before I wipe all her data..
Thanks
Update, it was that I just wiped all except the SD and flashed, all is just great

[Completed] Asus eepad transformer Marshmellow

Hey,
So this is my first foray into this sort of thing. I have some computer background but I haven't really gotten into this sort of stuff.
I have an Asus Eepad Transformer T101. I was requested to load Android 6.0 on it.
I followed this thread:
http://forum.xda-developers.com/eee-pad-transformer/development/rom-t3318496
I had to learn some things my way. User Debugging was on but I couldn't flash recovery. I ended up finally flashing recovery (I forget what step I had to do to use Clockwork Mod Recovery).
Once I was into CWM I had E:\Cannot Mount \sdcard\.
I then found out I had to use a micro SDcard, fine.
I couldn't load anything, and no solutions were working for getting SDcards to work.
I found a thread through google that said to use SD Formatter, to no avail.
Then I found this:
http://www.transformerforums.com/fo...x-bootloops-soft-bricks-all-ics-firmware.html
I have the files and. It was a batch file that loaded ADB then I could flash recovery. I attempted to flash recovery and I got to rogue XM recovery 1.5.0 (CWM - based recovery v5.0.2.8)
I used Nandroid Backup (Note, still could not mount SDcards)to do a backup of everything to the internal storage. I then did a wipe of all user data.
I have a folder called Marshmellow with Katkiss-6.0_025.zip, open_gapps-arm-6.0-pico-20160219.zip and BETA-SuperSU-v2.52.zip.
I attempted to install the KatKiss one, and it failed saying:
"Installing Update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/marshmellow/katkiss-6.0_025.zip
(Status 7)
Installation aborted."
So here's where I'm pretty sure I screwed up.
I loaded the Gapps and SuperSU.
Tried marshmellow again, and no luck.
Now the device boots to the eepad transformer screen, lasts a few seconds (usually no more than 10) and then reboots.
I've tried
http://forum.xda-developers.com/showthread.php?t=1688012
and
http://justanotherdave.ca/?p=351
The latter simply doesn't work. And I don't think I can get into ABX mode for the former.
Are there any resources on how to "unbrick" the device that may still work. Right now it just keeps rebooting at the nvidia eepad screen. I can get into recovery still.
Hello and thank you for using XDA Assist,
Please ask in our Android Q&A section:
Android Q&A, Help & Troubleshooting
Kind regards and good luck
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Trafalgar Square
XDA Assist

Help needed for Bootloop, Recovery mode stuck, Flashing sahara fail error in LYF Flame 1 LS 4503

Hi
New member here, so the problem is
1. Phone is stuck on - Powered by Android screen and automatically gets shut down or sometimes need to remove the battery to turn it off.
2 By Pressing volume down + power button = Phone enters in recovery mode which looks like the photo I am attaching here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In the above picture you can see the Errors I am having in recovery mode.
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Some say it's emmc chip failure but I read a forum here ( that's for another phone); in that post, someone posted exactly the same errors and he managed to fix the issues. I will post the link to that forum if I found it.
FOUND IT by Skanob
https://forum.xda-developers.com/t/guide-possible-fix-for-the-infamous-emmc-problem.1314629/
---------------------------------------------------------------------------------------------------
POSTS WITH SIMILAR ISSUES AND SOME MANAGED TO FIXED THIS ( LENOVO A6, HTC EVO 3D, Nexus 5 )
BY WillJitsu
https://forum.xda-developers.com/t/cwm-recovery-e-cant-mount-cache-recovery-command.1644790/
BY cadbomb
https://forum.xda-developers.com/t/howto-guide-repairing-corrupted-data-partition.2577447/
BY basavel
https://forum.xda-developers.com/t/...artition-after-flashing-5-1-lollipop.3052563/
-----------------------------------------------------------------------------------------------
HOW IT HAPPENED
The phone was on charging and I pulled out the charging cable and turned it on and after powered by Android screen this recovery screen appeared out of nowhere. It was on charging overnight.
------------------------------------------------------------------------------------------------
BY FAR WHAT I HAVE PERFORMED
1. I did wipe the cache partition first. - no use
2 Then I downloaded the firmware (2 firmware) and Qualcomm USB loader 9008 drivers and qpst and qpil, after that, I copied the firmware zip files in phone's sd card and tried the " support from SD card" option in " recovery mode ", didn't work, stopped automatically, it was so quick that I couldn't read the errors.
3 Now I tried to wipe data/ factory reset - nothing happened, the process started and stopped automatically.
4 I tried to flash rom on it, ERROR - download fail sahara fail, sahara server fail. Every single time, I changed the versions of flash tool USB drivers, old versions, latest versions, my laptop is flooded with unnecessary versions, it drive looks pretty messed up right now. Zip files and extracted files everywhere.
5 at this point I tried adb and fastboot, adb devices command shows my device name successfully but after that no command works, sometimes it showed failed or sometimes - waiting for device.
Sometimes it keeps saying - *failed to write data 'protocol fault (no status)' *
---------------------------------------------------------------------------------
FOLLOWED SOME OF THE STEPS FROM THIS - BY Teddy Lo
https://forum.xda-developers.com/t/...-sahara-fail-error-help.3823986/post-77229641
WANTED TO TRY THIS BUT ADB IS NOT TAKING ANY COMMANDS - by zhudachang
https://forum.xda-developers.com/t/lost-cache-partition-fixed.2949752/#post58720690
WANTED TO TRY THIS AS WELL BUT I DON'T KNOW HOW TO INSTALL TWRP IN THIS DEVICE WHICH IS ON RECOVERY MODE AND BOOT LOOP MODE AND NOT ACCEPTING THE ADB COMMANDS. BY Ciprum
https://forum.xda-developers.com/t/lyf-ls-4503-soft-brick-how-to-solve-it.3358002/post-67185573
------------------------------------------------------------------------------------------
EXTRA- I don't know if the bootloader is unlocked or locked or USB debugging is on/off.
I WAS HOPING FOR GENUINE HELP FROM ANYONE OUT THERE, THANKS A TON.

unmount 4.4.2

Hello!
How to unmount an old android 4.4.2 data partition?
Update: phone model if that makes any difference is Sony Xperia E1 dual
Not sure where to put this question, so I guess a general??
I have no knowledge of linux, android. But I got a programming background on windows systems and web.
I want to unmount an old android 4.4.2 data partition to run file system check because after deleting some files in data directory I am unable to write anything.
Could anyone please help me to get an idea how to do this? I searched the threads but they are more about flashing, TWRP and so on. Would not a simple file system check be enough in this case? As I noticed possibly it might be some sort of inode error? So checkdisk or something should fix it, shouldn't it?
I tried clearing the cache, it helped, but after few hours could not write anything again.
Now even the cache cleaning does not help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's always a good idea to set filepointer to begin of filesystem if you mount / unmount a partition: doing so you'll never run into error "Device or resource busy"
xXx yYy said:
It's always a good idea to set filepointer to begin of filesystem if you mount / unmount a partition: doing so you'll never run into error "Device or resource busy"
Click to expand...
Click to collapse
thanks for the tip!
However, I am a noob in linux/android, and the mount was done by android or KINGO rooter. So should I something like restart in recovery mode? Update:
Code:
adb reboot recovery
-> just rebooted to the regular interface
Update: phone is Sony Xperia E1 dual
I thought fixing a disk would be something like very basic task, like one liner or one parameter I did not add...
The mounting is just a way how I think I might solve the problem. That might be absolutely wrong way, not sure, now trying to move in the darkness by intuition only ...
Main problem: can not write anything with free space avaliable. Appeared since I deleted some files from /data using adb and rm command.
I also tried all the devices, but none of them was checked with two types of error:

Categories

Resources