two days ago, i rooted my phone using simple root, nand unclocked and flashed clockwordmod and everything. i was using fresh rom, and i wanted to use the vanilla lockscreen. but in order to do that, i needed to flash amons ra. i tried doing that, and somehow i got rid of my clockword recovery mod (and amons ra didnt work) so whenever i went into recovery mode, it just stayed at the screen with the phone and triange and red exclamation mark. i tried running the recovery windows .bat file, but it didnt work. and i tried running the ruu .exe file to unroot my phone, but everytime it said it couldnt find my device, even though it was connected via a usb chord. i tried it in charge only mode, disk drive mode, and htc sync mode and none of them worked. i tried using rom manager, but everytime i tried doing something it said error attempting to run privilidged scrips or something. i tried downloading the superuser .apk file and installing it onto my phone, but that didnt work either. the terminal emulator didnt work when i tried to flash something, it just said it couldnt find the file on my sd card, even though i put it on there. help?
Okay, number one: Did you try holding volume UP + power at the red exclamation screen? I think that's how you enter AR recovery.
Number two: You can flash Fresh tweaks without using AR. You just have to reboot into ClockworkMod and flash the .zip files manually.
Are you able to boot ANY ROM right now? If so, is it rooted? If it is, try to reinstall ROM Manager.
Sounds like you went a little off the deep end when you couldn't get into AR.
any suggestions?
Yeah, answer my questions or provide more info so you can get better direction.
you can reflash either recovery with the simple root program or you can follow the first part of toasts root method part 2 to restore recovery.
SilverZero said:
Okay, number one: Did you try holding volume UP + power at the red exclamation screen? I think that's how you enter AR recovery.
Number two: You can flash Fresh tweaks without using AR. You just have to reboot into ClockworkMod and flash the .zip files manually.
Are you able to boot ANY ROM right now? If so, is it rooted? If it is, try to reinstall ROM Manager.
Sounds like you went a little off the deep end when you couldn't get into AR.
Click to expand...
Click to collapse
ill try your first suggestion. and i cant boot any rom right now, because rom manager isnt working. and im pretty sure my phone is rooted, because i still have dev tools and CIQ settings and all those rooted apps.
update: your first suggestion worked, except once i entered AR recovery, the only options i had were: reboot system now, apply sdcard:update.zip, wipe data/factory reset, and wipe cache partition. at the bottom, it said "E: can't open /cache/recovery/command,
t3project said:
you can reflash either recovery with the simple root program or you can follow the first part of toasts root method part 2 to restore recovery.
Click to expand...
Click to collapse
i tried reflashing with simple root but it didnt work. can you give me a link for toasts method?
i had a similar problem, i used the OTA simple root, get that and plug ur phone back in with debugging on , one of the drop down menus will let you flash a recovery so flash clockworkmod
okay so somehow i managed to unroot it by wiping my data/cache..but now whenever i try using simpleroot or OTA simpleroot it doesnt work, because it says device is not found. i have it plugged in via usb, usb debugging is on, and ive tried it in charge mode and disk drive mode. anyone know what the problem is?
I'm sure there is a way to fix this, but I would suggest using the full root method by toastcfh.
okay i'll just reroot using that method, thanks. also, whenever im on my computer and im using command prompt, none of the adb commands ever work. do i need to download something for it to work?
Yes, you need the ADB framework. Read the guide (or the one by TheBiles, which is basically a rewrite). The ADB framework is a part of the Android SDK. You have to run ADB commands from the ADB directory (which is actually the "tools" folder inside of the SDK directory, wherever you extract that). Just cd to the tools folder, then run your commands from there.
Related
Can someone please help...
i rooted my evo and then reinstalled a backup, now i cannot start the evo, it just keeps rebooting. i have tried to restore nand backup, installing the new pc36img.zip file and reformatting the sd card. when i start with the pc36img.zip file on the root of the sd card, i get no image or wrong image. it also has the newest ota. any help would be greatly appreciated.
Thank you,
D_
Corrupted pc136 file?
Sent from my PC36100 using XDA App
you have to use OTA simple root, you can't use the regular simpleroot and most likely you nand wasn't unlocked that's why you have the bootloop.
youngdhillon said:
you have to use OTA simple root, you can't use the regular simpleroot and most likely you nand wasn't unlocked that's why you have the bootloop.
Click to expand...
Click to collapse
Also, after you do the newest ota simple root. Be sure to wipe all before you flash a new Rom.
vbyt said:
Corrupted pc136 file?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I have tried multiple PC136img.zip files.
Thank you
I used the ota simple root... when it was done, i tried to restore a backup of all my apps and data using my backup, that's when the loop started. I can boot into boot loader, nand, restore, etc... but nothing seems to get me out.
Thank you
What HBOOT version do you have? When you statr phone with volume down and power, white screen you come to at the top should be the version.
The HBoot is 0.79.0000
erase all the new files from your sd csrd....like pc36 and the flast image and image1-3...then start over using simpleroot 1.47
Thanks but I cannot boot the phone at all. I was able to format the card to fat32, boot the phone to recovery, start the ota simple root, on pc run Windows-recovery, start a adb shell and push the pc36img from simple root to it... but when I reboot from there, I get the "no image or wrong image". Then it will say loading... pc36img.zip for about 30 seconds, then says checking pc36img.zip for another 30 and go to the menu with "fastboot, recovery, clear storage etc..."
I can select "recovery" and see any Rom or zip file and load it; but it will still boot to a loop.
Thanks again.
Have you tried toasts part 2 in its entirity? You dont have the engineering hboot. Look for whiteslacks starting over it will tell you to do toasts part 2 first then run the whiteslack method you are going to have to get engineering hboot to do much of anything.
Sent from my PC36100 using XDA App
I will try it out and let you know. Thank you very much.
i tried the toast 2, but can't seem to get past the mtd-eng.img part.'
here's what i get. First i Hold down the vol button and press power. once the phone starts, i scroll down to recovery and press power. in recovery it says "ClockworkMod Recovery v2.5.0.1" at the top and bottom of the screen. Now i open a command prompt on my computer and type in, "recovery-windows" the phone then goes into the android system recovery, and at the bottom says "Build : not set". From here i can open shell on the computer by typing "adb shell", but when i type in the first line "cat /sdcard/flash_image > /data/flash_image" it returns "cat: can't open '/sdcard/flash_image': No such file or directory" but i can ls while in a shell and see the file in the data directory and i can cd to any directory. the flash_image file is in the data director, and i can change the permissions with 755, but cannot get past that part.
OK... I don't really know how, but i was able to finally get it to see the PC36img.zip files. i pushed the flash_image to the /data directory, wiped everything and rebooted with the new PC36IMG file on the root. it asked if i wanted to update, and the rest is history...
Thank you for all your help.
I never used simple root and i dont recommend by other suggestionfor many issue during the process. Always i use this way and work perfectly easy and useful step by step , then last step flash custom rom
http://forum.ppcgeeks.com/showthread.php?t=123714
132.651.1/6 Top Instructions
147.651.1 Bottom Intructions
I had rooted my phone and updated the radio to 1.47.651.1 when I tried to update a custom rom I accidently re-ran PC36IMG.zip and it rebooted quick NOW the radio says 1:39:00:04:26
and in the options below I now have
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HBOOT USB
I tried putting the phone on FASTBOOT then connected it to the USB and began a stock rom not rooted and it boots my phone into an HTC Black screen Boot mode and begins to update until it comes to the signatures and it gives me an error.
I run windows 7
I went and tried this, connected sd card to Computer with adapter and transferred stock rom rooted and renamed it to sdcard.zip
booted Evo to bootloader and chose recovery.
I as usual got the black background with EVO Icon and red triangle with exclamation mark.
There I click on hold Volume Up and Power until I get the following error:
E:Can't open /cache/recovery/command
Then I click volume up and the following title and menu appear:
Android system recovery <2e>
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
When I choose the sdcard:update option the following message is displayed
----Install from Sdcard ------
Finding Update package
Opening update package
verifying update package
E:signature verification failed
instalation aborted
After, I downloaded tha froyo 2.2 file and placed it on the sd and rename it to update.zip
and when I ran Update.zip from bootloader it ran half way but then stopped saying the following error
failed to verify whole-file signature
So now I load any PC36IMG and I get NO QUESTION to update just puts me onto the bootloader screen….
Not bricked, just stuck. Download stock ruu, plug phone into computer and install. Or put pc136.img on rot of sd, boot into fast boot, it should install automatically. If none of the above, go to a sprint store, tell them it won't boot and you don't know why, and they will flash or replace.
Sent from my PC36100 using Tapatalk
What I would do from here if I were you is put that sd card back in the computer and erase everything on it.
while your at it shut down the phone. Hold down the volume down button and press power. When that comes up post what version of Hboot you have please.
And I'll be better able to help out.
WOw
did you try to reinstall another ROM?
if you still see the RECOVERY menu item, go there and then go where it says update from zip on sdcard. then using up/down buttons highlight the .zip file of the ROM then push the power button to make it run.
this hoping you got a ROM on your sdcard. if not just get one at the forum and download.
i got clockworkmod but im sure the other recovery tools have similar options.
@ adelaney Stock Ruu begins to update and gives me an error when signatures are being installed. I tried three Stock ROMS
RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253
RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed
RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459
@ rjmjr69
Hboot information is:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-0.79.0000
MICROP-041F
TOUCH PANEL-ATMWLC03_16ac
RADIO-1.39.00.04.26
@mogul420
Recovery gives me an error
E:Can't open /cache/recovery/command
Then I click volume up and the following title and menu appear:
Android system recovery <2e>
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
When I choose the sdcard:update option the following message is displayed
----Install from Sdcard ------
Finding Update package
Opening update package
verifying update package
E:signature verification failed
instalation aborted
Ok here's the deal. If you have nan unlock, fully rooted then you should have a nandroid back. If you do then boot into recovery and no a nandroid restore. This should boot you to one of your pervious backup/ system state.
Please note.
If you are fully rooted u should always do a nandroid backup before you flash any update, that way u can do a restore in the even something goes wrong.
http://WWW.rootznculture.com
Thank you for the information but it was a step I did not do... The tutorial that I went with did not speak about that when I rooted my phone...
EDIT: I even tried mixing files that I have downloaded with various PC36IM.zip and nothing triggers the update question.
Would they be able to notice if its rooted?
adelaney said:
Not bricked, just stuck. Download stock ruu, plug phone into computer and install. Or put pc136.img on rot of sd, boot into fast boot, it should install automatically. If none of the above, go to a sprint store, tell them it won't boot and you don't know why, and they will flash or replace.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Most likely NOT bricked if it boots!
Sounds like you re-applied root but glitched somewhere?
Try root again - may still work?
http://forum.xda-developers.com/showthread.php?t=706411
Another helpful post
http://forum.ppcgeeks.com/showthread.php?t=123714
What version is your hboot - press power and volume down WITHOUT pc36img.zip, update, etc on your sd - i.e. rename it or remove it, i.e. with adb or sd card slot on pc.... See if you can still access recovery?
I've been hammering on these things for a bit and if I can get into the boot screen, it's pretty much good to go...
Hboot-0.79.0000
Also the error that began all of this was running the wrong PC36IMG to begin with... I had 1.4 radio and I think that the one I used had the 1.3 radio so the only thing that helped me boot up again was that 1,2,3 step flashing so I thought that I had to take the second step and that placed in on booter, I have not been able to boot again ever since.... That was yesterday been trying for about 9 hours lol
lwarranty said:
sounds like you re-applied root but glitched somewhere?
Try root again - may still work?
http://forum.xda-developers.com/showthread.php?t=706411
another helpful post
http://forum.ppcgeeks.com/showthread.php?t=123714
what version is your hboot - press power and volume down without pc36img.zip, update, etc on your sd - i.e. Rename it or remove it, i.e. With adb or sd card slot on pc.... See if you can still access recovery?
I've been hammering on these things for a bit and if i can get into the boot screen, it's pretty much good to go...
Click to expand...
Click to collapse
Yes your just not rooted anymore. Run whatever process worked for you the first time
Try whitslack's method.
EDIT: Nevermind, no can do.
What happens is that my phone DOES read the PC36IMG.zip but it does not give me update option as it used to before. Any suggestions?
rjmjr69 said:
Yes your just not rooted anymore. Run whatever process worked for you the first time
Click to expand...
Click to collapse
xx1479 said:
Try whitslack's method.
Click to expand...
Click to collapse
latinsbest said:
What happens is that my phone DOES read the PC36IMG.zip but it does not give me update option as it used to before. Any suggestions?
Click to expand...
Click to collapse
Like he said
Make sure you delete all the files off your sdcard first
Do you have a link? I made a quick search and could not find a direct link...
xx1479 said:
Try whitslack's method.
Click to expand...
Click to collapse
I have several times even formatted (fat32) various times too
rjmjr69 said:
Like he said
Make sure you delete all the files off your sdcard first
Click to expand...
Click to collapse
latinsbest said:
I have several times even formatted (fat32) various times too
Click to expand...
Click to collapse
Reroot your phone using toast method! That is all! If you are on 1.47 then use simple root!
Seems you have un-rooted the boot me thinks but also read something about mixing radio's causing grief, someone more in the know could answer that... If you can get to hboot usb and try the RUU from your PC? Sometimes taking the battery out and restarting, if communication fails, try it again, rebooting the pc, hell I have no procedure, I just hammer till it makes sense, however 9 hours - holy crap, I'd be foaming at the face!
Ok will do right away and post update
novanosis85 said:
Reroot your phone using toast method! That is all! If you are on 1.47 then use simple root!
Click to expand...
Click to collapse
I have done that via PC and the only thing that works with that are the stock roms since they come in EXE they manage to reboot my phone and everything but when the update gets to the signature part it says it fails in the signatures and aborts... any other custom roms that have EXE?
lwarranty said:
Seems you have un-rooted the boot me thinks but also read something about mixing radio's causing grief, someone more in the know could answer that... If you can get to hboot usb and try the RUU from your PC? Sometimes taking the battery out and restarting, if communication fails, try it again, rebooting the pc, hell I have no procedure, I just hammer till it makes sense, however 9 hours - holy crap, I'd be foaming at the face!
Click to expand...
Click to collapse
Hi guys, I've had my Desire rooted for around 2 months and have used loads of
ROMs/Mods etc. It's fair to say I know the procedure. At the moment though I'm
puzzled and worried because I have lost my previous ROM and can't get a new one
on!
I was flashing a new version of Pinky Desire over the previous one (without wiping)
and it never got to the reboot screen. So I took out the battery and put it back in
to reboot it. It got to the custom boot screen and no further so I then booted into
recovery and wiped data and cache and re-flashed the ROM, but the result was
the same...
So I tried this a couple more times until suddenly the recovery-windows.bat file
would no longer put me into a recovery menu. I've tried everything I can think of
(using my original Goldcard etc) but nothing is fixing it- it's like I've lost root access.
How can I make my phone useable again? PLEASE HELP!!!
EDIT: In case it makes a difference I did delete what I thought were some old .zips from my SD shortly before this.
Install an official RUU, then re-root it? I guess some of the pro's got some better answers though
Download the ClockworkMod recovery, rename it in update.zip, put it in the sd, enter recovery, when you get the red triangle press vol up+power, select to flash update.zip.
Yep, flash an ruu, then re-root, only this time use unrEVOked and for future when flashing roms use the newer recoveries like clockworkmod or amonra.
The old recoverywindows.bat file leaves you at risk of the usb brick. You may well already have that now if you pulled the battery mid flash.
Thanks all. Haven't had a chance to do this yet but will. I did manage to flash an update.zip but it won't detect the sd. will try with clockwork mod.
DomFel said:
Download the ClockworkMod recovery, rename it in update.zip, put it in the sd, enter recovery, when you get the red triangle press vol up+power, select to flash update.zip.
Click to expand...
Click to collapse
Tried this but all I'm getting is cannot find directory. It retries about 12 times then
reboots. Just won't work.
When trying to flash an RUU it comes up with 'Error 170: USB connection error'.
This is weird because the device's bootloader recognises that there's a usb
connection. Any ideas?
EDIT: Seems like the phone in it's current state simply can't mount an sd card.
Gotta try some alternative methods for getting the RUU to run...
Doogleman said:
When trying to flash an RUU it comes up with 'Error 170: USB connection error'.
This is weird because the device's bootloader recognises that there's a usb
connection. Any ideas?
EDIT: Seems like the phone in it's current state simply can't mount an sd card.
Gotta try some alternative methods for getting the RUU to run...
Click to expand...
Click to collapse
Check out the USB brick thread.
prove said:
Check out the USB brick thread.
Click to expand...
Click to collapse
I will. That's so sh*t though
Thanks guys
Had almost same problem.
I even couldn't flash update.zip
the problem was in SD. it was working OK in windows, but phone couldn't mount it. soved problem with reformating using SDFormater, when formated with clockworkmod.
mendozinas said:
Had almost same problem.
I even couldn't flash update.zip
the problem was in SD. it was working OK in windows, but phone couldn't mount it. soved problem with reformating using SDFormater, when formated with clockworkmod.
Click to expand...
Click to collapse
I've two SDs and neither is working though so...
two things
the windows unlockerthing.bat was only supposed to be run one time, after that you could access the menu pressing vol up and power...
Why would you pull the batt on a Flash??
Pulled the battery because the device said flash completed but didn't do anything for over 5 mins. Won't make that mistake again. I've actually bricked the USB so this thread is a little pointless now
Oh and I did fix the SD issue
Hey everyone. I know there are already a few threads with boot loop animations, and am having difficulties finding the same situation as what I'm going through. Here is what the phone used to have before it randomly started looping:
Rooted - with Stock rom, using ClockwordMod Recovery 5.5.0.2
Used Go Launcher Theme ( if that even matters )
No additional roms installed or anything, the phone is 3 months old.
Ok here is where I'm stuck. I understand I should reflash somethings like recovery image or something, but I'm stuck with one big problem. My computer and phone don't recognize using the USB mount.
The message I get is called "Unable to open lunfile ( no such file or directory)
Here's what screens I can get to:
1. Hold vol up/down while holding power ( the little android with its belly open, and the options Start - Restart Bootloader - Recovery mode - Power Off )
2. Hold vol down - ODIN mode, with the START option only
I can access WMD recovery and factory reset, Try to install my old backup, nothing works at all in that area, no matter what I do.
Can someone advise me a step by step way of getting my computer to recognize my phone, so that I am able to do fastboot, or reflash, or anything to get my phone working again. I can't access my internal memory at all.
It's even possible that I've read too much, and my frustration is getting in the way, if so I apologize! Some guidance would be greatly appreciated!
Thanks in advance of course! I need my phone for business!
Cheers,
Install the drivers on a computer then use fastboot oem unlock. Or just factory reset it from within recovery.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-4
Try my siggy.
I'm not sure about the exact error:
But the link there will get you the correct drivers.
Also, as stated...try to factory reset.
You'll lose your apps/data that way though =/
Hopefully you can get the driver installed and get your computer to recognize.
If so, follow this to back up your apps:
http://forum.xda-developers.com/showthread.php?t=1420351
Have exactly the same setup as you (rooted/stock/CWM) and had the animation bootloop - animation would just loop until a battery pull.
Only thing that solved it was a factory reset from recovery. Been working fine for the 4 weeks since. No need for any reflashing etc. Titanium recoveries have all worked fine as well. Didn't try my Nandroid backup as I thought that may still have the 'fault' built in.
I had a boot loop for every from I tried to flash...wat fixed it was before flashing u need to wipe system data and wipe the cache in the recovery...ie a clean install...then every rom I tried worked...so I think ur missing that crucial step coz it worked for me
Sent from my Galaxy Nexus using Tapatalk
Hey guys, as stated above I've done numerous factory resets, it still seems to boot. I will for sure try to get the drivers installed so my phone is recongised by the computer, but would need step-by-step assistance when doing fastboot, or whatever the next step is.
Looking for more help though! Keep em coming!
?
Any other ideas?
Thanks!
Ok guys, so here's where I'm at now. I've used Jubakuba's sticky link, located here:
http://forum.xda-developers.com/showthread.php?t=1529058
Everything is able to be recognized up to the point where it says "Put the su.zip on your phone."
Since I cannot access my phone contents, since I keep getting this "Unable to open lunfile ( no such file or directory), it does not allow me to add anything to my phone.
I re-installed CWD as stated in the list of things to do, and all that went well. But I have the same issue, I tried factory resetting all that. erase cache, and still stuck with the same issue.
What's my next step now peeps? Looking for a quick answer as I have time to do it tonight!
Edit***
Just tried this trick: but it says it does not recognize the device?? what is going on! Please help someone! Thanks!
Panic Section! (Something is Wrong)
Q: My phone won't boot!
A: The easiest option is to get into recovery and restore a nandroid using the above guide (pull battery to put phone in an off-state if needed).
However, more advanced options are available if you don't have a nandroid available (You're naughty).
Do you have another rom .zip available on your SD card? If so, simply use the above guide for installing a rom to get you booting again.
If not, you can download one on your PC. Boot into fastboot (the green Android with open chest menu).
Move the .zip to the C:\android-sdk-windows\platform-tools folder.
Open ADB.
Change the NAMEOFZIP.zip below to the correct file name...and perform the action.
Surely your computer recognizes your phone. Otherwise how were you able to unlock the bootloader and flash the recovery?
And I've never seen that error message before. It doesn't even make any sense to me. Where are you seeing it? On your phone or on your computer? And in what context? What are you trying to do when it shows up?
If your phone isn't booting I'm not sure that you can copy any files to it yet. (Maybe you can use adb in clockworkmod? I'm not sure) What I do know you can do is flash the stock ROM and start over.
Download the image from Google here:
http://code.google.com/android/nexus/images.html
Here's a instructions for the GSM version:
http://forum.xda-developers.com/showthread.php?t=1366806
For the Verizon version, I can't find the thread at the moment but you just replace the filenames and also there's 2 radios to flash so:
fastboot flash radio *filename*
fastboot reboot-bootloader
fastboot flash radio-cmda *filename*
"Unable to open lunfile ( no such file or directory) appears on the phone, in CWD mode, when trying to attempt "mount Usb" to be able to access my internal storage .
I am attempting your thoughts right now.
I will post with results
Ok I tried to do this step. This is the outcome I received on the computer after even typing the first step:
'fastboot-windows' is not recognized as aninternal or external command, operable program or batch file.
A thing to stress, I'm not sure how to do step 1: 1) Take a Nandroid Backup if you have CWM installed.
EDIT***
GREAT NEWS!
used this setup!
http://android.modaco.com/topic/348161-01-feb-r4-superboot-rooting-the-gsm-lte-galaxy-nexus/
and it worked!
Thank you everyone! Going to play with my phone and make sure it all works!
Macinshak said:
Ok here is where I'm stuck. I understand I should reflash somethings like recovery image or something, but I'm stuck with one big problem. My computer and phone don't recognize using the USB mount.
The message I get is called "Unable to open lunfile ( no such file or directory)
Click to expand...
Click to collapse
the problem is when that happen?? when ur phone is booted and u plug the usb cable to ur pc? or when u are under recovery and want mount the usb mass storage? the second one doesn't work
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.