HELP!!! My SGS i9000 is stuck in bootloop. - Galaxy S I9000 Q&A, Help & Troubleshooting

Help. MY SGS i9000 is stuck at bootloop. I had CM7 installed before, i was flashing back to stock rom and i got stuck in bootloop. i get "Android system recovery <3e>
E:failed to mount /dbdata
E:delete_data_files : cant mount /dbdata

How did you try to flash the stock rom? From recovery or with Odin?
Edit.
The stock rom/kernel cant read the filesystem that CM7 used, so it must be converted back (I think)
One way to do this would be to flash a stock rom with odin, using a .pit file and ticking the "Re-Partition" box

I flashed it using odin. Will try your tip

Tried your tip. Didnt work.

Edit (again) So sorry, i forgot to mention you need the android 2.2.1 firmware because for diffrent bootloaders in gingerbread.
You can find froyo firmware here: http://www.samfirmware.com/
Direct link to firmwares (choose one of the 2.2.1) http://www.sammobile.com/forum/showthread.php?t=17
http://forum.xda-developers.com/showthread.php?t=1139050
Your odin should look something like this
{
"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"
}
With pda, phone and csc file + pit
This should work =/ strange if it doesn't

Thanks a lot bro. You are a savior. Phone works.

Tusharkamath said:
Thanks a lot bro. You are a savior. Phone works.
Click to expand...
Click to collapse
Dear sir, I have the same (almost) problem. I followed your instructions but problem is still there. My phone works fine but when I turn it off and then start it up, it keeps boot looping and after some time (last time took 10 minutes but sometime takes hours) and then turns on just fine. On boot menu (3e) or CWM, I can never access internal sdcard, says is not prepared.
E:cant mount /dev/block/mmcblk0p1
(no such file or directory)
E:copy_dbdata_media:cant mount SDCARD

Related

[Q] Android System Recovery <3e> problem

GT i1900M
I was trying to update to CyanogenMod 10.2.
The phone was purchased in Canada and flashed and installed Froyo 2.2 soon after purchase some years ago. Which was fine until now.
I was following the instructions in How Manually Update Your Samsung Galaxy S GT-I9000 to Android 4.3 Jelly Bean
I transferred the CyanogenMod and Google Apps packages to a directory on my phones SD card called 'Download'.
I also installed from the PlayStore [BOOT] recovery tools - Flasher
I switched off the phone and booted into recovery mode. As there wasn't an option to perform a backup of the current OS, I didn't.
I then successfully did a 'wipe/data factory reset' and a 'wipe cache partition' after which I did a 'apply sdcard:update.zip and got the following message.
Installation aborted
--Insall from sdcard...
E:failed to open /mnt/internal_sd/update.zip (no such file or directory)
E:signature verification failed
Installation aborted.
I'm still in the Android system recovery <3e> window with two options available, namely reboot system now or Format interal sd-card.
If I reboot the system now will I be able to install the CyanogenMod some other way?
richardnz said:
If I reboot the system now will I be able to install the CyanogenMod some other way?
Click to expand...
Click to collapse
for i9000M, you need to
i9000M Upgrade or Downgrade GB 2.3.3 UGKG3 ROM + 512 PIT finally with UGKG3 Root & CWM http://www.4shared.com/file/eGrh9tKQ/s1_odin_20100512.html Ideal base for upgrading to ICS and JB
flash above following
{
"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"
}
[Tutorial] How to Unbrick, Flash, Downgrade, Root, Update i9000 from Froyo to Kit Kat
the Gingerbread flashing guide, after that you can flash other versions step by step following the above guide.
Check this out! Links to useful Guides and " Banned " Documentaries ​
it's not work. many apps are not install. can I upgrade my handset?? How I do??

How to downgrade from 5.0.1

I got a used phone i537UCUCOC7 android 5.0.1. What do i do to downgrade and can i when security patch?
cell2011 said:
I got a used phone i537UCUCOC7 android 5.0.1. What do i do to downgrade and can i when security patch?
Click to expand...
Click to collapse
To downgrade to KitKat, download the following file to your PC and extract with 7zip or WinRar: https://www.androidfilehost.com/?fid=23991606952608110
Boot your phone into download mode. This is done by powering the phone off, then holding down vol- and power at the same time. Connect the phone to PC with USB. You have to flash all four files with Odin as shown in the following image:
{
"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"
}
Please be aware that this process will erase any settings, data, and media saved to your phone's internal storage and restore it to its original factory condition, now on KitKat. This process also takes a long time (at least 5 or 10 minutes) and will cause your phone to reboot on its own, and to boot into stock recovery at least once. It is important you leave your phone alone while it is doing so, and definitely do not disconnect it until it boots into the KitKat setup wizard screen.
To apply the security patch, you will now have to flash two files in stock recovery (vol+ and power). First download and extract this file: https://www.androidfilehost.com/?fid=96042739161891196 it should be named 2400258.cfg. You need to rename it update.zip (yes, this involves changing the file type) and save update.zip to your external SD card (it will not work if it's on internal storage).
Finally, you need to download this file to your external storage and flash in stock recovery: https://www.androidfilehost.com/user/?w=settings-dev-files&flid=37222 Please note this file has already been renamed update.zip. They must both be named update.zip for them to work; since this can be potentially confusing I'd advise you to either save them to different folders, or delete the first one after you're done with it.
Follow these steps and you'll be back on KitKat, with that all important security patch. Good luck :good:

Bricked Huawei P10 - Any help? (VTR-L29)

So in my unending wisdom whilst drunk I used an app off the store to reset my phone to factory (I know, what was I thinking?) and have been left with the phone stuck in bootloop.
I can get into EMUI but my only options are Reboot, Shutdown and Download latest version and recovery - I can select that and select my WIFI, but when trying to restore/download anything it fails.
Out of some of the guides I have (tried) to follow I've found the Update.zip I think I need, extracted and then I need to move the update.app to the SD card? However I can't do this as the Update.app file is over 4GB
I am a complete noob with this (obviously) but any help would be hugely appreciated.
Thanks
Try this guide https://forum.xda-developers.com/p10-plus/how-to/p10-plus-to-stock-erecovery-dns-ff-t3730077
Hey, I'm probably doing something wrong and missing something obvious, but I can't seem to get it to work. Am I missing something.
I set my DNS to 81.177.139.39
I had to use the Windows 10 hot-spot feature to do this as my router will not allow DNS change.
Then opened up Firmware finder, searched for the firmware for my model and copied it
Pasted it in to the Firmware for install bar, clicked set then Register for update.
Wnet into erocovery on my phone, selected the hot-spot I had changed the DNS for and clicked update.
It started saying "getting package info from server" did that for about 5 minutes then went straight to "getting package info failed"
Thanks again for any help and sorry for being a noob
{
"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 think you have to set the DNS to the router.
You can still try many debrick methods that are describet here in forums.
Do you really know that you are in bootloop? After factory reset the device could bootup about 5 minutes.
DallasCZ said:
I think you have to set the DNS to the router.
You can still try many debrick methods that are describet here in forums.
Do you really know that you are in bootloop? After factory reset the device could bootup about 5 minutes.
Click to expand...
Click to collapse
Yeah maybe the router is the problem. Well the phone tries to boot up, then shuts off and boots again but the second time boots directly into EMUI

[Solved] Help with TWRP and VENDOR

Hello, I am a owner of a ZUK Z2 Pro from Brazil, apologies for my english.
I tried to update the mooke rom to pie, but it wasn't working via central mooke, so I downloaded and tried to flash on TWRP, but I was possesed by a demon and instead of not deleting the internal storage, I delete all files. The problem now is that the mobile isn't reconigze in the computer and the device manager shows this:
{
"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"
}
The USBView show this:
Maybe it's something related to the vendor folder that can't be mount on TRWP. I tried adb push, but don't display my device and I don't have acess to allow the usb debugging. I tried USB OTG, but the pendrive is unrecognized. I don't know what to do anymore, but I don't think the mobile is bricked. May day may day!
In twrp you have to click mount otg to make it visible in the file system (if you already did this you can try different adapters/usb sticks). If you deleted the vendor partition I think you should be able to fix it by going back to stock or finding a vendor image/backup. If the only problem is that you ran the vendor to factory script and now twrp dies not find it you can just update twrp. Updating twrp could also help with the unrecognized usb issue.
craftandbuild said:
In twrp you have to click mount otg to make it visible in the file system (if you already did this you can try different adapters/usb sticks). If you deleted the vendor partition I think you should be able to fix it by going back to stock or finding a vendor image/backup. If the only problem is that you ran the vendor to factory script and now twrp dies not find it you can just update twrp. Updating twrp could also help with the unrecognized usb issue.
Click to expand...
Click to collapse
I can't mount otg because twrp don't let me selected the option, I had install all drivers I found of zuk, lenovo and qualcomm and still unrecognizable on the computer, therefore I can flash stock or the vendor image/backup, the version of my twrp is the 3.3.0.0, the most updated. You know if there is a way to force the computer to recognize the device?
Solved doind this.

Question Can't install Xiaomi EU ROM - Stuck without a ROM

I've followed the process outlined here. After installing the ZIP, it rebooted, but went back to recovery. When I said reboot system, it said No OS installed.
So, I tried to start over by formatting data and then copying the zip again via ADB Push. Then the trouble starts. After adb push, which takes about 5 minutes, it says
Code:
failed to copy 'xiaomi.eu_multi_HMNote10Pro_V12.5.3.0.RKFMIXM_v12-11.zip' to '/sdcard/xiaomi.eu.zip': write failed: No space left on device
After that, the data partition seems corrupted. Whenever I go to Install, it shows 0 bytes. Upon Googling I found a solution by formatting to ext2 and back to ext4. Then, it shows again as 100000MB. However, adb push every time fails with same problem.
For some weird reason, I can push to /data. But still running into same problem after installing ROM and rebooting, it goes back into recovery.
I also tried to sideload, but then I run into this issue:
Code:
D:\Tools\ROMs>adb sideload xiaomi.eu_multi_HMNote10Pro_V12.5.3.0.RKFMIXM_v12-11.zip
loading: 'xiaomi.eu_multi_HMNote10Pro_V12.5.3.0.RKFMIXM_v12-11.zip'
* cannot read 'xiaomi.eu_multi_HMNote10Pro_V12.5.3.0.RKFMIXM_v12-11.zip' *
So, I'm stuck with a device without any ROM. Any suggestions please?
Did you ask in the MIUI EU forums as well? Since there would be more ppl familiar with these issues than here.
I'm also interested in this since I prefer EU roms. Also you need a specific TWRP version which I believe is still in alpha stage for the 10 Pro since its still a new device. There should be a TWRP thread somewhere here where you can also ask.
I just got my 10 pro and need to wait a few more days to unlock BL, then I will be flashing an EU rom, hence my interest. Hope you find a solution.
Use TWRP from here:
https://forum.xda-developers.com/t/4248449/
fastboot reboot bootloader
fastboot boot TWRP_file_name.img
Format Data, type yes.
{
"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"
}
Reboot to recovery.
The internal storage should be visible.
Connect phone to PC and put ROM into phone.
Flash ROM, format data, yes
Reboot to system.
If above not work, make your phone under fastboot mode, Mi-Flash, and flash your stock fastboot MIUI. Don't lock your bootloader.

Categories

Resources