In the process of trying to flash a new firmware to a GIO I somehow managed not to be able to acess the recovery menu anymore. Right now the Phone is rooted, booting fine into stock ROM, download mode is working but no recovery menu. While trying to boot with power and home button it just shows the Samsong logo for ages.
I tried to flash a new recovery several times due to the fact that the stock recovery is only able to apply update.zip and not able to select any custom filename. So I installed su and a new recovery this way. After realizing that there is no recovery anymore I did it using ODIN and download mode. I tried several recovery images from cwm to stock, but everytime the same.
What did I miss?
How to do a dalvik/cache reset outide revovery menu and not doing a full hard reset?
Would a hard reset help?
TiA,
longInt
Guess their are commands to do it with ADB, phone can still go on so thats fine
Download adb
Connect phone to pc
Open command prompt , cmd.bat
Type
Adb
Su
Reboot recovery
Try if it works...
You can also flash recovery with ODIN, cwm v5 can be flashed with odin
Sent from my GT-S5660 using xda premium
I did already
Flashed cwm-5.0.2.7-ext4+rfs-odin.tar.md5 using ODIN without problems, but as I said, no recovery menu available/accessible. BTW: Do I've todo anything after ODIN triggered the reboot? I just remove the phone and try to access recovery menu...
I do not have adb available at the moment, Sorry. Will try tommorow, but I guess this will not show something different!?
Thx!
Terminal emulator?
Code:
su
Reboot recovery
Sent from my HTC Sensation
OK; will try the Terminal emulation soon. But also when trying "Reboot to recovery" from inside ROM Manager it just hangs showing the SAMSUNG Logo. Did I flash the right recovery in terms of the ext4 thing?
TiA
voetbalremco said:
Adb
Su
Reboot recovery
Click to expand...
Click to collapse
This results in a black screen and the phone not booting anymore (just showing the Samsung logo). I'm pretty sure the stock rom is booting again after flashing cwm again (had this before). Doing this now...
Any other ideas, tipps?
TiA
OK, guys, time for new proposals. Whichever way I try to get into recovery it fails. Reflashing recovery brings the phone back, but how to go into recovery!? I even tried to boot recovery using my GS3 Toolkit with the same negative result just to prove there is no way to reach recovery.
Isn't there a need to flash cache and dalvik or something else after flashing recovery!? How?
TiA
Try flashing a full stock rom with odin, so everything is gone, kernel, su etc...
If still not, live with it or bring it to a service center
Sent from my GT-S5660 using xda premium
OK, thx. If someone is having additional hints/ideas please let me know . Phone is still working but still no recovery...
exact same problem
longint2 said:
OK, thx. If someone is having additional hints/ideas please let me know . Phone is still working but still no recovery...
Click to expand...
Click to collapse
I have the exact same problem as you. Same phone as you, phone rooted fine, tried installing CWM now can't get to recovery with the same symptoms as you. Holding Power+Home results in a hanging Samsung logo and no longer being able to boot at all. Removing the battery doesn't help. Reflashing allows me to boot normally but still not recovery mode (download mode accessible all the time). Rebooting from ROM manager usually results in "RAMDUMP mode arm9" instead of recovery (wtf).
Tried different CWM versions recommended for Gio, some older some newer, some with different filesystems.
Tried different methods for installing recoveries (from SD card in the original recovery mode the first time, and from ODIN)
Tried different methods of reaching recovery mode (key combination on boot, reboot from terminal, reboot from ROM manager).
Tried doing "firmware update" with (lol) Kies
Seriously no idea how to solve it, it's exactly the same as the problems in this thread. Advice from friends and these forums has so far not helped, but hopefully someone will discover an answer soon?
Things I don't think are related:
I have hardly any space left on the phone
My battery life has now been reduced to 2 hours average (woohoo!)
Have you tried installing stock rom via Odin? It installs stock recovery itself, and then you would be able to see what happens when you are trying to acces recovery
Very simple, it happened to me sometime ago. The problem was that my pc was blocking Odin to flash correctly, so I figured out the solution. The solution is to try flashing it from someone else's computer. Give it a try and tell me.
---------- Post added at 08:23 AM ---------- Previous post was at 08:17 AM ----------
Follow step by step:
Make sure you do it from a PC on which you haven't already installed Samsung USB drivers or KIES.
1. Install Samsung usb drivers.
2. Open Odin and boot phone into downloading mode.
3. Browse Gio.ops and xxxxxxxx.tar file and start flashing.
Sent from my GT-S5660 using Tapatalk 2
nope…
pakistanish said:
Very simple, it happened to me sometime ago. The problem was that my pc was blocking Odin to flash correctly, so I figured out the solution. The solution is to try flashing it from someone else's computer. Give it a try and tell me.
Click to expand...
Click to collapse
I doubt this is the problem because the first time I tried flashing CWM was not with Odin (I'm not a Windows user) but from the stock recovery as shown in the video tutorial on this forum. I think I'll try wojtek267's suggestions and reflash the stock rom when I get my USB cable back.
Tried a lot more things, none of them worked
Sorry for double-posting, but this is long.
Update:
I got a USB cable. I tried a lot of stuff that also doesn't work. That's what's covered in this post:
This doesn't work. Naturally the first part doesn't work because it says boot into recovery and I can't do that. Ignoring that and continuing from step 5 does just as little. At the bottom of this post I've written what Odin does.
This also doesn't work, it's basically the same thing.
Tried reinstalling stock ROM as suggested. No difference in results. List of ROMs I've tried at bottom of post.
Tried using Odin from a different PC, as suggested. More on this at bottom of post.
Tried flashing using flash_image in adb. More about that at bottom of the thread.
Tried to get fastboot to work. I get an infinite < waiting for device >. More on that at bottom of the post.
Tried to factory reset the phone using both the menu option in settings, and the dial code, both result in the phone turning off and then starting up with a blank black screen that stays there forever.
Tried taking the battery out a thousand times, seriously why is this suggested so often?
List of Recovery ROMs I've tried:
signed_cwm-5.0.2.7-flashablezip-ext4only.zip
cwm-5.0.2.7-ext4only-odin.tar.md5
cwm-5.0.2.7-ext4+rfs-odin.tar.md5
stockrecovery-DXKT4-odin.tar.md5
All coming from this thread.
Also one or two others from blog about clockworkmod etc.
The point is it has no effect because as far as I can tell it isn't even flashed anyway.
Flashing from fresh PC failed
What I mean by this is:
I took a different PC
did a fresh install of windows on it
installed the Samsung drivers using the Kies CD
put the phone in download mode (VolDown+Home+Power)
start Odin, select OPS and tar.md5 file
connect phone
run Odin
nothing special happens…
What Odin does:
copy image to phone → success
disconnect from COM port and wait for reboot
start countdown timer
at this point phone reboots normally (not recovery or anything) and nothing special happens, the Odin timer eventually time's out and the operation is finished
Update: added actual output from odin as an attachment.
I'm not sure but I don't think the above is what Odin is typically supposed to do.
The odin I'm using is 4.42 for Gio and comes from the threads linked to in the first 2 bullet points linked above.
How flash_image fails
I have tried using both adb and terminal emulator on phone. Root access is given to the emulator via superuser app. This is what I do:
Code:
su
cd system
flash_image recovery recovery.img
This is what I get:
Code:
error scanning partitions: No such file or directory
recovery.img is located in /system/recovery.img
flash_image is located in /system/bin/flash_image with proper chmod setting of 755.
It makes no difference if I mount the system as read/writeable or not.
The flash_image I'm using comes from CyanogenMod wiki, here.
My best guess here is that the reason flash_image finds no recovery partition is that there isn't one. I certainly don't see one. And this would also explain why the phone does nothing (black screen or samsung logo) when you try to boot to recovery.
Please dear God somebody tell me that one of you has seen this before and knows a solution for this?
According to this thread the partition where recovery.img resides is /dev/block/bml9, but how do I get my CWM recovery.img on that partition? Do I cat? dd? What? Is there any partition (e.g. that one, or /system or anything) that I should format to something strange before this will work?
Issues with fastboot
2 problems with this. First one is, how exactly do you get into "fastboot" mode on the phone? I don't even know if it can. I have uncovered the following startup key-combos:
recovery mode (Home+Power) does not work, so now just a blank screen
download mode (VolDown+Home+Power)
ramdump arm9 mode (VolUp+Home+Power)
emergency download mode (VolDown+VolUp+Home+Power)
LK Little Kernel Mode (VolUp+VolDown+Power)
blank screen (VolUp+Power)
blank screen (VolDown+Power)
regular boot (Power) doesn't work after attempting hard reset, only results in samsung logo and inability to boot
None of these seem to be fastboot mode, so I guess it's more complicated than that.
Other problem is I'm using Linux and I've read I'll need to configure Udev to detect the phone ID used when in fastboot mode.
I've read that some people who couldn't flash with flash_image in adb were able to flash using fastboot so I'm hoping for that.
Summary
As you guys can see I've really tried a lot of things. Everything I can think of, and everything I could find on XDA and the rest of the web. I have had no success. Like OP's topic title says, I still have a working phone. When Hard Reset fails and the phone becomes unbootable I can make it bootable again by using Odin to fail at flashing a recovery.
So the phone actually works fine. The problem is I can't get to recovery mode and therefore can not flash CyanogenMod (all CyanogenMod threads say to flash ClockworkMod Recovery before CyanogenMod).
Please can somebody help me with this, I don't know what else to try.
Edit: hey pakistanish, thanks for the suggestions, if I don't install the USB drivers from the Kies CD then where am I supposed to get them from?
Bump?
Nobody able to help with this?
Am I in the wrong sub-forum or something?
One more option you could try: the dd command. Provided you're rooted, copy the recovery.img file you want to flash over to your SD card.
then from a shell: dd if=/sdcard/recovery.img of=/dev/block/bml9 bs=4096
Also, did you try using ddms or logcat while your phone was stuck at the Samsung logo? There might have been clues as to what the issue was.
Good luck,
Darkshado
very nice try, still no cigarre
Darkshado said:
One more option you could try: the dd command. Provided you're rooted, copy the recovery.img file you want to flash over to your SD card.
then from a shell: dd if=/sdcard/recovery.img of=/dev/block/bml9 bs=4096
Also, did you try using ddms or logcat while your phone was stuck at the Samsung logo? There might have been clues as to what the issue was.
Click to expand...
Click to collapse
Hi thanks for the helpful advice! I tried that now. Backed up the current bml9 to sdcard with dd and then dd'd my recovery.img over it; it seemed successful. I restarted the phone to recovery mode and it just hangs at the Samsung logo like normal. This thread confirms that /dev/block/bml9 is indeed the recovery partition, however replacing it seems to have no effect.
I have never heard of ddms or logcat, what do they do and do you have download links?
I still have the same issue, thx for any advices.
Today my N7100 suddenly rebooted without any warning and got stuck at initial Samsung boot logo (even sound gets into loop). I managed to enter recovery and tried to wipe cache partition. But every time I try to wipe anything or delete via twrp file manager - phone reboots
Should I try re-partitioning via Odin? What pit file do I use?
lorendroll said:
Today my N7100 suddenly rebooted without any warning and got stuck at initial Samsung boot logo (even sound gets into loop). I managed to enter recovery and tried to wipe cache partition. But every time I try to wipe anything or delete via twrp file manager - phone reboots
Should I try re-partitioning via Odin? What pit file do I use?
Click to expand...
Click to collapse
you can try to use Odin, but probably you have faulty eMMC, many similiar cases around the forums about rebooting and stuck on Samsung logo.
Probably PC won't recognise your phone and there will be nothing else to do, but to give it to service
Miracles happens! Re-partitioned and fully erased nand via Odin and managed to upload the rom! Have tried 3 time before it succeed (crashed few time on system and cache image writing). Everything seems fine so far. Won't upgrade the rom from the stock 4.1.2 for a while to keep phone working. I have the insane emmc chip by the way. Hope it won't fail again.
Hello,
tried to upgrade my 1.4 watch to 1.5 via update.zip. While pushing the update.zip he stopped copying.
From this time the watch always stuck at Google bootanimation.
So I tried to push the update.zip again, success, but not boot up.
Then I unlocked the bootloader, pushed twrp, pushed a whole system.img, success, but not boot up.
In TWRP is saw that he cant mount storage (0 MB) and /data.
So what can I do? Remeber a rapair option of filesystem in TWRP of my Samsung. But cannot find.
So is there a way to rebuild storage and /data using fastboot or ADB?
I have no TWRP Backup. But if somebody can give me... may restoring would go or fail because he cannot mount?
Whole sh*t because cant wait for OTA
Ok. No help. So I had to help myself :-/
Luckily found images of all partitions for persons who installed the preview of Wear 2.0 and want go back to 1.5
Flashed all of them using fastboot and voilà I'm back in business
ArnomaF said:
Hello,
tried to upgrade my 1.4 watch to 1.5 via update.zip. While pushing the update.zip he stopped copying.
From this time the watch always stuck at Google bootanimation.
So I tried to push the update.zip again, success, but not boot up.
Then I unlocked the bootloader, pushed twrp, pushed a whole system.img, success, but not boot up.
In TWRP is saw that he cant mount storage (0 MB) and /data.
So what can I do? Remeber a rapair option of filesystem in TWRP of my Samsung. But cannot find.
So is there a way to rebuild storage and /data using fastboot or ADB?
I have no TWRP Backup. But if somebody can give me... may restoring would go or fail because he cannot mount?
Whole sh*t because cant wait for OTA
Ok. No help. So I had to help myself :-/
Luckily found images of all partitions for persons who installed the preview of Wear 2.0 and want go back to 1.5
Flashed all of them using fastboot and voilà I'm back in business
Click to expand...
Click to collapse
Hi, could you be so kind to share those partitions to me please?? My watch just turned into a brick...: ( Many thanks!
Stuck in twrp recovery
Here's my case
I have a huawei watch
i unlocked the bootloader successfully
I then flashed twrp recovery
then tried to flash a custom rom but failed.
I am stuck at twrp recovery and fastboot mode.
I cant boot into system
I tried to sideload adb from twrp but it said unable to mount storage and unable to mount data.
When i flash the stock recovery, it keeps rebooting itself.
PLease tell me if there is any hope for me.
Have you tried to format the partitions? or to repair it via "Wipe" > "File System Options" > "Data" > "->" > "Repair"? Or chance the filesystem? mine is f2fs (this only works for data and not for storage...
Hi,
A few days ago my GT-N7100 started to behave weirdly. Phone was stuck in a boot loop. I tried to open recovery but it wasn't booting into recovery mode.
I flash TWRP recovery using Odin and found that the internal storage size was showing 0 MB. So I formatted the Internal storage and then repaired it using TWRP.
Then I tried to install a custom rom in it. After the installation was successful, i wiped cache and factory reset the phone but phone was still stuck in boot loop.
I turned on my phone in recovery and found out that it /data size was 0MB. So I installed a pit file using Odin to resize it. It was successful. Then I installed a Stock rom 4.4.2. Now the phone turns on and shuts down after a few moments.
I think there is not boot loader which can boot the OS (Just my understanding).
Please help.
Thanks,
shujaathussain said:
Hi,
A few days ago my GT-N7100 started to behave weirdly. Phone was stuck in a boot loop. I tried to open recovery but it wasn't booting into recovery mode.
I flash TWRP recovery using Odin and found that the internal storage size was showing 0 MB. So I formatted the Internal storage and then repaired it using TWRP.
Then I tried to install a custom rom in it. After the installation was successful, i wiped cache and factory reset the phone but phone was still stuck in boot loop.
I turned on my phone in recovery and found out that it /data size was 0MB. So I installed a pit file using Odin to resize it. It was successful. Then I installed a Stock rom 4.4.2. Now the phone turns on and shuts down after a few moments.
I think there is not boot loader which can boot the OS (Just my understanding).
Please help.
Thanks,
Click to expand...
Click to collapse
in recovery need to mount data to show if not will show 0mb
since u already Flashed official rom can turn on phone but after few moment will shutdown by it self ?
try change the battery if helped !
good luck !
Hello,
my Samsung Galaxy S4 mini with bliss ROM stated to turn off spontaneously and sometimes it didn't start again (the Samsung logo appeared and then the phone went dead, it was impossible to enter recovery mode, download mode shut down itself immediately). After several tries, it booted normally. This happened again - and I found out it was a bad power button, which I replaced. Now it is possible to enter both recovery mode and download mode with no problems. However the main OS doesn't boot up. So I tried to do a full wipe in recovery mode and CWM recovery rebooted the phone, when it was trying to format /data partition. So I tried to flash stock firmware with ODIN. It also didn't boot up, but at least the stock recovery gave me a hint what is wrong. When I perform full wipe, I get error: "E:format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc.1/by-name/userdata"
I tried to flash the phone again, this time with a PIT file and let ODIN to reformat the partitions. However, no change. How can I fix it?
Try twrp