First off, I'm a little out of my depth here.
I had originally wanted to root my A8, but stopped short because it isn't officially supported by TWRP. I wanted to roll things back but botched the Odin process. I flashed the AP file but didn't include any of the others. As a result, I can't get into the bootloader. I'm not sure what my options are at this point, or if I have any.
I've already wiped the cache partition and done a data/factory reset.
Output on my Recovery screen is as follows:
Code:
Failed to load locales from the resource files, Failed to compare
#Reboot Recovery Cause is [UNKOWN]#
#Reason is []#
E:Failed to load bitmap installing_text for locale en-US (error -1)
Supported API: 3
# MANUAL MODE v1.0.0#
No command specified.
I'm hoping there's a procedure for completing loading in the other files, or getting back into the bootloader.
Do I have any hope or did I truly brick this thing?
Ok, I got it back by using vol up/down and plugging in the USB. Wasn't able to do it from the recovery, but the physical method worked. Odin worked, I'm back in business.
Related
Hello,
Like many other users on this forum, I am having trouble with my i9000M sdcard after doing some ROM flashing.
Although there is some extensive threads collecting the different situations people are experiencing, I was hoping I could get some help for a specific circumstance relating to the sdcard issue.
I'll start by..
- Detailing the firmwares I have flashed, and what happened
- What is working / not working now, and how I got to get to the current situation
- And finally, I'll detail what I'm trying to do and where I'm getting stuck.
I would really appreciate some help with this, and thank anyone who takes the time to read it. I am trying to be very thorough to give you as much information as possible.
-----------------------------------------------------------------------------
1. Started with stock firmware. I am not sure what it was.. I believe the phone is equivalent to the Bell i9000M, but I am on the SaskTel carrier.
2. Flashed firmware I9000XXJP2: This worked, and I was using Froyo 2.2 fine.
3. Tried to root Froyo 2.2 firmware: This FAILED and the trouble began. I was using the update.zip method, and the source claimed it was compatible with 2.2. I had to hard reboot the phone, but it would stall on the white text intro screen (not the animated one).
4. Went into Download mode. Tried to flash firmware I9000UGJH2 (apparently the most current bell firmware), using Odin v1.1. This FAILED, and I had to hard reboot, which resulted in the PHONE - ! - PC error. I am aware the i9000M can still be recovered from this state.
NOTE: I could do nothing at this point: all firmware flashes failed, UNTIL I CHANGED TO ODIN V 1.3!
Using Odin v.1.3:
5. Flashed a series of firmwares.. (I9000UGJG8, I9000XXJM1, I9000XWJG5), ALL resulted in the phone either being in a shutdown-boot loop to the white Glaxaxy text screen, or the battery charging screen.
I could enter Download mode to reflash, but NOT recovery mode.
6. The ONLY semi working firmware is I9000XXJP2, Samsung Froyo 2.2. This is what the phone is now.
- I CAN enter Download mode, Recovery mode, and the phone stalls on the white Galaxy boot screen, but goes no further, and does not restart.
- I CAN run abd commands
Here is the output I get from each of the options in the Recovery mode:
Code:
I9000XXJP2
Odin 1.3
512.pit
Flashes fine
Goes into recovery mode
Displays error:
(No such file or directory)
E:copy_dbdata_media: Can't mount SDCARD
your storage not prepared yet. please use UI me nu for format and reboot actions.
copy default media content failed.
Try to format sdcard:
Formatting SDCARD:...
ensure_root_path_unmounted**
ensure_root_path_unmounted (/mnt/internal_sd)
ensure_root_path_unmounted ret 0
ensure_root_path_unmounted It's not mounted
update media, please wait
E:Can't mount /dev/block/mmcb1k0p1
(No such file or directory)
E:copy_dbdata_media: Can't mount SDCARD
your storage not prepared yet. please use UI me nu for format and reboot actions.
Try to wipe cache partition:
-- Wiping cache...
Formatting CACHE:...
ensure_root_path_unmounted**
ensure_root_path_unmounted (/cache)
ensure_root_path_unmounted ret 0
unmount (/cache) attempt 1 (Unknown error: 0)Cache wipe complete.
Try to apply sdcard:update.zip
Same errors as 1) can't mount sdcard therefor installation fails.
Reboot system:
- Will accept adb download reboot
note: I can reach download mode using the button combination
- recovery mode: can access with button combination or 'adb reboot recovery'
- power off: battery charging indicator shows
note: it does not loop the battery indicator
- power on: stalls at Galaxy S GT-19000 white lettering screen.
note: i recieve an indication on windows desktop that a device has been connected which is capable of USB high speed point
ADB COMMANDS WORKS: device is detected
Things I have tried:
I tried booting into a Ubuntu Live cd to see if I could format the sdcard, as suggested in this thread: (sorry, forum won't allow me to hyperlink, thread id=759910)
The disk utility picked up the Samsung drives (One was labeled something like Samsung_Galaxy, and the other Samsung_Galaxy sdcard, but I'm not 100%) but could not format them. There was also no info being listed about the size.
Things I would like to try / have hunches on:
Before all this happened, I made a Nandroid backup of the orriginal firmware, and copied it from the i9000's sdcard to my computer. I made the backup using Rom Manager's Clockworkmod.
Is there a way to use Odin to flash Clockworkmod, so I can restore this backup?
-everything out there says to use Rom Manager, which I can't access because the phone is pseudo dead.
Will the backup even still be on my sdcard?
Wait, my sdcard isn't mounted.. can we try mounting it with abd? (I tried, but am not sure of the command / path of how to do this..
Can abd be used to restore my backup stored on my computer? Is this dependent on the sdcard being mounted?
I fully appreaciate those you take the time to read through this as it is rather lengthy. I just want to ensure I have tried every means to revive the device, and hopefully some more skilled users can help with the mounting and adb syntax.
All comments and ideas are welcome and appreciated! Thank-you
Sorry to be the bearer of bad news. But time and time again this error has proven to be a hardware error. Mine did the same thing and samsung/bell had to replace the mainboard in my phone. Good luck, but unfortunately, anything you do further is a waste of time short of sending it back for repair.
Hi,
I have a problem with my Moto G 2014 XT1068 which is described in topic: forums.androidcentral.com/moto-g-2013/391289-something-seriously-wrong-my-moto-g.html#post3668518
I can't do these steps, because dialog window shows up all the time, and i cant go further.
I have disabled usb debugging option and can't disable ART runtime.
First of all "Factory" in bootloader doesn't work. Wipe and factory reset via stock recovery has no effect; old android remains, the same using TWRP:
"E:Unable to open 'cache/recovery/.version' but ends successfully
and PHilz.
I've tried to flash many roms using many recoveries( TWRP - few versions up to 2.8.5 because 2.8.6 has display flickering bug, few Philz, and few others that also flicker) and fastboot and msfastboot(both on linux).
When i flash via fastboot or mfastboot using xml.zip roms everything looks ok, there are no errors, but flashing has no effect - I have still old ROM with old issue.
When i flash via different recoveries always some errors appears. For example flashing latest CM 12.1 nightly
via TWRP i get:
"E:Error executing updater binary in zip '/sideload/package.zip'
or via stock recovery (ADB sideload) get:
"(...)
Verifying update package...
E:Failed to verify whole-file signature
E:signature verification failed
Installation aborted."
Partition erase in fastboot despite "OKAY" message in CLI has no effect. As i understand this should remove all files from partitions.
This problem showed up when i discharged battery to 0% and turned on the phone.
Have you any ideas what should i try more?
Thanks in advance.
Hi,
I've tried other things to back my phone to life, like turn on usb debugging or even delete files, all via adb shell in recovery, but it is impossible. In TWRP or PhilzTouch I remount partitions with rw privileges, it look like I'm able modifying files via vi and cat to check results but when remount one more time old files still exist, so it is like there is some buffer? (maybe some security lock?), when try rm -rf files it shows up that i can't delete because it read only... (but mount says rw). After remount partitions with rw privileges wipe /data in twrp ended successfully but has no effect.
Do you know why everything looks ok, but it is not? Of course android boots up but is useless and after few minutes phone turns off.
i have the exact same problem with xt1064 that shuts off after bootanimation, all flashing and wiping look ok, but stuck in same result.
i read in some threads it's due to corrupt partitions and there's no solution yet to this problem, i hope this is not true, please share if you make any progress, i will do the same. best of luck.
Sounds like you both have a failed eMMC. If that is the case, and I'm certain it is, there is nothing that can be done to "save" or "restore" your devices.
Sent from my XT1031
hi, maybe any1 has already found a solution?
dihcar said:
i have the exact same problem with xt1064 that shuts off after bootanimation, all flashing and wiping look ok, but stuck in same result.
i read in some threads it's due to corrupt partitions and there's no solution yet to this problem, i hope this is not true, please share if you make any progress, i will do the same. best of luck.
Click to expand...
Click to collapse
I have exactly the same issue with my XT1063. Reading a lot for a solution, traying all without success.
Hopping someone can help us!
Dear forum,
I'm struggling to get CM 11 (or any other stable CM MOD) installed on my Galaxy S.
Trying to go back to factory settings, my rooted phone got bricked.
After struggling with the USB drivers via zadig I finally managed ODIN (very flaky tool !) to recognise the deive. I managed to repartition the phone using the PIT file s1_odin_20100512.pit (from google code)
I then started following the guidelines for installing CM on the device and flashed the phone (using Heimdal) with semafore 2.7.4. When going in recovery mode, it gave errors related to the mount points (missing .fstab). Any action from the recovery mode (data wipe, format, etc.) was resulting in errors related to the mount points...
Digging around pointed me to the Replicant recovery image as this would resolve the problem. Which it did. It now states CWM-based recovery v6.0.4.6 and operates without errors when mounting unmounting etc.
Now, when in recovery mode and pushing (adb) any MOD (CM, replicant, etc.) I always get an error stating:
E:Error in storage sdcard0 update.zip
(status 0)
Installation aborted.
I've been spending hours on combinations, rebooting reconnecting, re-wiping, toggling signature verif, sideloading vs pushing, etc. etc. and searching the Internet for answers.
So far I have not found a root cause or way to avoid the error and continue with the ROM installation.
Any idea what is causing the error message in the ROM zip files with Status 0 ?
After a fresh reboot in recovery and going to Advanced-show log, I can see:
Code:
I:Skipping execution of extendedcommand, file not found...
I:Cannot load volume misc
I:Can't partition non mmcblk device: devices platform s3c-sdhci.0 mmc_host mmc0
All hints are welcome.
Thanks
Help revive my device.
After updating the tablet from the playmarket of the Youtube application, the tablet freezes, after a reboot, it hangs on the Asus logo and a spinning circle. I couldn’t enter the droidboot from the buttons and, following the instructions from the 4pda forum, after downloading the service firmware, unpacked it to drive C into the folder, then went to the firmware folder by pressing shift + the right mouse button opened the command window and launched the
droidboot with the fastboot boot droidboot.img
fastboot continue
commands booted into the droidboot and in the folder with the firmware clicked on the update_image file, the firmware process started which took a very long time about 7 hours, at the end the tablet rebooted but only until the first screen saver. I waited a long time, but it did not boot. I turned it off. After that, by pressing a combination of buttons, I was able to enter the droidboot, the serial number of the tablet was missing, through a dead robot I was able to enter the recovery.
Then, according to another instruction from 4pda, through a temporary twrp, I tried to install the Ul-KO13-WW-3.2.23.182-user firmware, the installation process started, but it did not install, but the serial number returned and the tablet again hung on the Asus logo and a spinning circle.
I checked the
fastboot oem start_partitioning
fastboot flash /tmp/patrition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
commands after each command was OK. So the flash memory of the tablet is working.
After I checked the root, the rights remained. USB debugging in the developer menu was turned on even when the tablet was working. Then I decided to try installing the service firmware 201 again, as I wrote above, and again unsuccessfully, the serial number flashed again. . And again, through a temporary twrp, I began to install 182 firmware.
And the serial number failed, it was not restored, but the recovery now showed that it costs 182 firmware. After that, when checking, I found out that no root su. I got a complete crash. I tried again to install 201 firmware and now it costs WW 3.2.23.201 in recovery.
On the advice of a person from the 4pda forum, I tried to restore images of 201 firmware boot.img fastboot.img recovery.img via twrp v2.8.7.0 from the 4pda forum, but again unsuccessfully. I showed the person who helped me install the firmware images 201 that twrp gave me an installation error, it read:
Updating partition details ...
E: Unable to mount '/ factory'
E: Unable to mount '/ config'
E: Unable to mount '/ data'.
The person who helped me said that there was no markup table, or rather, the system section was written, but could not find the other sections, since he wrote this script for Android 5. And on KitKat version 4.4, he did not test this script. Now I'm desperate, I really need a tablet in working condition. Because I am very poor, and I do not have money to buy another tablet, I have been sick for 5 years. I live on disability benefits, they pay me $ 50 a month and I can’t buy another one. I beg everyone to help with tips and instructions on how to restore tablet firmware. I need a worker. I need your help.
Even when connecting to a laptop on a Windows 7 tablet in twrp 2.8.7.0 mode, the tablet is detected as K013, but it does not see the internal drive and only shows a microSD card, I suggest that this is because the firmware is installed incorrectly and there are no firmware sections? ? If Who knows, you can install any custom firmware that fits on my tablet.
If someone can write me instructions for restoring the firmware. If anyone has encountered a similar problem, give information and instructions for restoring partitions with links from where to download what and step-by-step instructions for restoring.
Sorry text wrote through translator. I hope the problem is described clearly and someone can help me with the firmware.
I thank everyone in advance who will respond and help restore the firmware.
P.S. I decided to try to flash through Intel Flash Tool Lite, I launched service 201 firmware, reached the 57% band and issued FAILED. I turned off the tablet, I decided to try running TWRP, running the script, and now there are only two errors:
E: Unabled to mount / and
E: Unabled to mount / config, and the amount of internal memory Internal Storage (3916MB) !!! And before that, it was zero and in the device k013 on the laptop it shows the storage along with the memory card. Here's an interesting process
Hey guys,
Here's the situation. I was in the process of completing the setup of my 768GB Note 8 (SM-N950N) with Dr.Ketan P12 custom ROM, and RZ Kernal (for DriveDroid support). Out of nowhere, my Note 8 camera just stopped working, and the Dr.Ketan ROM Tools and Tweaks Pro apps could no longer be opened. I began back-tracking my steps; tried reverting magisk back to v20.1, tried dirty flashing the ROM again, all to no avail. In the process of troubleshooting, figured it could be something I toggled under developer settings. Noticed that my OEM Unlock toggle was turned on, even though I recall seeing it turned off earlier during the configuration process (as explained by @dr.ketan here, scroll to Note for OEM Issue). Thinking it's ineffective, I turned it off and was prompted to reboot my device, just to get stuck at the boot screen
I came across the following forum post describing how to recover from the boot loop, without needing to delete any data, by flashing the latest available official firmware AP***.tar (removed the .md5 extension) file using Odin3:
https://forum.xda-developers.com/sprint-galaxy-s6/help/custom-binary-blocked-frp-lock-how-t3581010
The problem is, during the flashing of the Dr.Ketan P12 custom ROM, I chose to flash the SM-N950F OMC for SM-N950N, in order to use a Korean-Free CSC (more details on why explained here). So, even though I've attempted all of the following:
- flashed the current latest available official firmware AP***.tar file for SM-N950N,
- simultaneously flashed the current latest BL/CP/HOME_CSC***.tar.md5 and AP***.tar firmware files via Odin,
- flashed the latest TWRP***.tar custom recovery (failed probably due to OEM unlock being disabled),
- wiped cache via the stock recovery,
- tried booting via the "Lacking storage booting" option in the stock recover,
- tried booting to safe mode,
- tried using Smart Switch for PC, it (nor its Emergency Software Recovery) never detected my Note while stuck at the Samsung boot logo, nor did it detect it in Recovery mode,
- etc.it still won't boot-up, and I think it's due to the CSC (UK Unbranded - BTU) not being available in the official firmware.
When I boot into recovery mode, I get the following message:
Code:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
Support SINGL-SKU
File-Based OTA
Supported API: 3
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
# MANUAL MODE v1.0.0#
can't open directory '/system/omc/SUP/etc/sysconfig' . (No such file or directory)
can't open directory '/system/omc/SUP/etc/cid/sysconfig' . (No such file or directory)
can't open directory '/system/omc/SUP/etc/permissions' . (No such file or directory)
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : '/proc/device-tree/firmware/android/compatible' : No such file or directory
Would any of you folks have suggestions on how I could recover from this mess without needing to delete any data? Perhaps if there was a way I could add the UK Unbranded CSC to the official SM-N950N firmware and flash it via Odin, maybe that'll allow it boot? Please kindly advise, thanks in advance.
Bump
please i have the same proplem what to do
i dont know the meaning of bumb
please help
ah_1st said:
please i have the same proplem what to do
i dont know the meaning of bumb
please help
Click to expand...
Click to collapse
No luck on my end, lost months worth of data on my internal storage. Had to perform a factory reset on my Note 8 via Odin, reflash TWRP via Odin, then reflash my Custom ROM and tweaks. Lesson learned for real though