Related
last night i flashed an update of clockwork mod through rom manager. i then went to do a back-up of my current rom. the phone re-booted to the fastboot mode and now says no boot or recovery img. when i scroll to recovery and click it, the phone reboots right back into the bootloader. i am trying to flash a new recovery through adb but i cant get anything to connect. when i do "adb devices" in the command prompt i get the daemon started and list of devices but there are no devices listed. "fastboot devices" does nothing either. i have the android sdk loaded onto c:\ and the drivers seem to be installed correctly. when i rooted the phone i used a different pc that i dont have access to now. i also used pdanet for the drivers so i have never had the google drivers set up correctly. i type fastboot flash recovery recovery.img and it says "cannot load recovery.img" i have downloaded the recovery-clockwork3.0.0.5-crespo.img to the "tools" folder and renamed it "recovery.img"
i have tried to explain everything i have done so far but i am sure there are some steps i have missed. i read some on odin and downloaded it but i am even more lost trying to figure that out. i really need some help here and i would appreciate anything i can get
when you're in bootloader, you're supposed to use "fastboot"
you cant flash a recovery using adb.
go into bootloader mode
fastboot devices
... if your device doesn't show up, then your drivers are not properly set up.. uninstall them and look for the sticky and reinstall your drivers using those set of instructions; assure your SDK is updated to support 2.3.X
when you get your device to appear in fastboot devices.
download clockwork recovery 3.0.2.5 (3.0.2.4 is buggy) or 3.0.0.5; 3.0.2.5 is found in dev forums; rename it to recovery.img
put it in /sdk/tools/
fastboot flash recovery recovery.img
i guess i need help getting the device connected through fastboot. i have tried 5 times now to install the drivers verbatim to what the sticky says (using W0lv3r1n3's Great Windows Rooting Guide). adb command works and pulls up the adb help text. fastboot is still unrecognized by the command prompt. adb devices nor fastboot devices works. i have no idea what else to do. most of the stickies just graze over this part and have no trouble shooting guides.
tohg2 said:
i guess i need help getting the device connected through fastboot. i have tried 5 times now to install the drivers verbatim to what the sticky says (using W0lv3r1n3's Great Windows Rooting Guide). adb command works and pulls up the adb help text. fastboot is still unrecognized by the command prompt. adb devices nor fastboot devices works. i have no idea what else to do. most of the stickies just graze over this part and have no trouble shooting guides.
Click to expand...
Click to collapse
if your device is unable to GET into bootloader mode... that wont get you anywhere.
when you plug your phone into the computer with the USB.. does that USB sound pop up? if it doesnt.. then its bricked.
ok i have fastboot devices seeing the device. but adb devices still wont see it. when i do fastboot flash recovery recovery.img it says cannot load recovery.img. i put the clockwork file in the tools folder renamed at recovery.img. do i leave it as a zip file though?
when i plug the usb in i dont hear a sound. the phone will only boot into "fastboot mode".
when i do fast boot devices i see "38328e03afbf00ec fastboot"
tohg2 said:
ok i have fastboot devices seeing the device. but adb devices still wont see it. when i do fastboot flash recovery recovery.img it says cannot load recovery.img. i put the clockwork file in the tools folder renamed at recovery.img. do i leave it as a zip file though?
Click to expand...
Click to collapse
bootloader mode is for fastboot. you wont be using ADB to recover your device.
you unzip the file. it should be like: clockwork-recovery-version..blah blah blah.img
rename it to "recovery.img" assure that your "fastboot" appears as "fastboot.exe" and not just "fastboot." if it is "fastboot" you need to go into folder options and show extensions otherwise you'll be trying to flash "recovery.img.img" and SDK wont recognize it
tohg2 said:
ok i have fastboot devices seeing the device. but adb devices still wont see it. when i do fastboot flash recovery recovery.img it says cannot load recovery.img. i put the clockwork file in the tools folder renamed at recovery.img. do i leave it as a zip file though?
Click to expand...
Click to collapse
Make sure you are typing the full file path, for example on my setup its "fastboot flash recovery c:\android\tools\recovery.img"
Sent from my Nexus S using XDA App
file extensions are being shown and it is named recovery.img. still saying cannot load "recovery.img" i have tried several recovery downloads from different sources. as for file size of the img its 3,988kb sound right? i tried fastboot oem lock and unlock and everything worked fine. is there another recovery img i can try. maybe a stock recovery or somehting?
ok so i tried "fastboot flash recovery c:\program files (x86)\android\android-sdk\tools\recovery.img" exactly and still nothing i have the path modified in the system so i was under the assumption that i didnt have to write out the whole path in the command prompt.
tohg2 said:
ok so i tried "fastboot flash recovery c:\program files (x86)\android\android-sdk\tools\recovery.img" exactly and still nothing i have the path modified in the system so i was under the assumption that i didnt have to write out the whole path in the command prompt.
Click to expand...
Click to collapse
cd C:\program files (x86)\android-sdk\tools\
fastboot flash recovery recovery.img
is what you want to do.
tried that path and still got nothing. i re-booted my pc thinking that would help and now i cant find my device with fastboot devices. adb isnt recognized either now. i just cant catch a break. although i suppose its my fault. i really appreciate you going back and forth with me like this. with all the trouble i am having does trying odin make any sense? i searched a bit but there dosent seem to be alot of info on that either
tohg2 said:
tried that path and still got nothing. i re-booted my pc thinking that would help and now i cant find my device with fastboot devices. adb isnt recognized either now. i just cant catch a break. although i suppose its my fault. i really appreciate you going back and forth with me like this. with all the trouble i am having does trying odin make any sense? i searched a bit but there dosent seem to be alot of info on that either
Click to expand...
Click to collapse
Odin is last resort. If fastboot devices shows your phone you will be able to flash recovery. Reinstall phone drivers and get fastboot to work. Then get back to trying to flash recovery. I really think it is some small mistake. Did you exctract the zip of recovery and copy the .img file?
The error you were getting means the appropriate file was not found in the file path you specified, so its not a phone error.
Sent from my Nexus S using XDA App
got it. the first line in my command promt kept saying c:\users\dana>. i couldn't delete it so i ignored it and kept typing in the path after that but i guess it was always looking in users/dana and that wasn't where the img file was. i put the img file alone in the users/dana folder and it worked. i guess i am a bit slow to understanding the command prompt. thanks again for everyone's help and patience
tohg2 said:
got it. the first line in my command promt kept saying c:\users\dana>. i couldn't delete it so i ignored it and kept typing in the path after that but i guess it was always looking in users/dana and that wasn't where the img file was. i put the img file alone in the users/dana folder and it worked. i guess i am a bit slow to understanding the command prompt. thanks again for everyone's help and patience
Click to expand...
Click to collapse
Cool! Glad you got it, good job!
Sent from my Nexus S using XDA App
Please help, I'm having the exact the same problem
I know, I shouldn't have play around with my phone since I don't know much about rooting the device.
My phone booted into Andriod logo with an unlocked, I have successful downloaded
clockwork recovery 3.0.2.5 and rename it to recover.img
I ran following command
fastboot flash recovery recovery.img and it was successful..
I tired to reboot my phone after that as normal but I'm still getting the same screen which only showing the Android Logo with an unlocked lock.
I'm not sure what I am suppose to do after need to get my phone to work again, any help would be appreciated.
Thank you,
Please can someone help me, im stuck in the bootloader cant use recovery or anything. Dont have adb , lost it i guess. My phone is stuck. Is it bricked, if so can someone at least tell me
whitetiger2429 said:
Please can someone help me, im stuck in the bootloader cant use recovery or anything. Dont have adb , lost it i guess. My phone is stuck. Is it bricked, if so can someone at least tell me
Click to expand...
Click to collapse
Grab the stock update (Full ~90mb) or full stock ROM from the dev forum for your specific device. Extract it and use fastboot to flash the .img files
fastboot flash boot boot.img
fastboot flash recovery recovery.img
ok a lil confused. Im currently stuck in the bootloader(at the top its says fastboot mode- no boot or recovery img) Im unable to do anything with phone trying usin adb it doest give ne a serial number It just say devices attached and it shows nothing. so how do i get the files i need on the phone. You said fastboot not sure how to start that. Do i just download the zip and extract it and hit shift-right click in the folder to bring up command. If so how do start the command line.
the only stock rom im finding that the links work for is only 77mb will that work
You need to use fastboot, not adb.
Grab the appropriate full rom here (i9020, i9023) for your phone: http://forum.xda-developers.com/showthread.php?t=1056062
Extract that.
Take boot.img and recovery.img and put them into tools\ folder of the SDK (where fastboot is located) unless you've added it to your path.
fastboot devices should show your device (serial) much like adb devices
Flash boot:
fastboot flash boot boot.img
Alternatively, you could flash CWM (using fastboot, just grab the .img for CWM) - flash the entire update package and then reboot - it will install the stock recovery.
krohnjw said:
Grab the stock update (Full ~90mb) or full stock ROM from the dev forum for your specific device. Extract it and use fastboot to flash the .img files
fastboot flash boot boot.img
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Ok i did that but when i tried flashing the recovery img it said error: cannot load ' recovery.img.
the link for my version is broken or something
whitetiger2429 said:
Ok i did that but when i tried flashing the recovery img it said error: cannot load ' recovery.img.
Click to expand...
Click to collapse
The full recovery isn't in the package. You could flash cwm manually via fastboot and then install the full OTA package through cwm. A subsequent reboot will then install the stock recovery.
Sent from my Nexus S using XDA Premium App
ok the rom i had downloaded didnt have a revovery img in it, still trying to find a rom with both boot and recovery. If i cant how do i a flash cwm manually, where do i get the files from.
whitetiger2429 said:
ok the rom i had downloaded didnt have a revovery img in it, still trying to find a rom with both boot and recovery. If i cant how do i a flash cwm manually, where do i get the files from.
Click to expand...
Click to collapse
okay
- download this file: http://hotfile.com/dl/119279955/e2325da/Tool.rar.html
- extract it in anywhere (could be in desktop)
- open the file named "Start Here"
- type: fastboot flash recovery recoverycwm.img
so i download the file and extract it. Do i hit shift - right click to bring up the command line or what. im really confused on this. I have never had this many problems with a phone. I guess i need step by step steps
whitetiger2429 said:
so i download the file and extract it. Do i hit shift - right click to bring up the command line or what. im really confused on this. I have never had this many problems with a phone. I guess i need step by step steps
Click to expand...
Click to collapse
i can't see how i could make it easier.
- extract the file, and make DOUBLE CLICK in the file named "Start Here.exe" to open it
- plug your phone in bootloader screen
- type fastboot flash recovery recoverycwm.img
- hit ENTER
theres no start here file it only shows tool rar
whitetiger2429 said:
theres no start here file it only shows tool rar
Click to expand...
Click to collapse
extract it? ^^
i did using and theres no exe file only a rar thing i used the stock extract program to do it did i do something wrong
"start here.bat"
can't you see it either?!
there is no start here.bat
dude, it's a .rar file. it's compressed. Inside it has several files.
donwload winrar (if you are running windows) http://www.rarlab.com/rar/wrar401.exe
install it and extract the content of the tool.rar file!
ok i install win rar extracted but still no start here.bat. I sthere a certain way of doing this i know nothing about rar files
ok i found that file
nexus 9020A did rooting, but when i tried to boot up it froze and not booting up look like System.IMG missing what is the solution for that
Thanks in Advance
Lost what ever info you can so that the people you are asking for help from can better help you.
Sent from my Nexus S using XDA App
when i turn the phone on it shows me ( google) and under of it there is a open Lock and as soon as it comes phone freezes . i tried to fastboot System.Img file in it but every time i do it fails.i want to know what should i do from this place? Sorry i spent 10 hours last night to get it fixed and i was bit frustrated .
thanks
can u get into recovery by holding up volme and power button?
yes i can go into bootloader and recovery. i tried to recover it in factory mode didnt work.
any helppppppppppppppppppppp?
Put your phone into fastboot.
Download ClockWorkMod Recovery: http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-crespo.img
Flash clockwork mod recovery in fastboot with this command: fastboot flash recovery C:\where\ever\you\put\the\file.img
Then from fastboot select recovery.
Wipe data/factory reset
Install zip from sdcard: http://download.cyanogenmod.com/get/update-cm-7.1.0.1-NS-signed.zip
Do you have a custom recovery?
If yes, then download a Rom to your computer and either a) mount your to computer and transfer the Rom to your phone or b) push it to your phone with adb.
After that is done wipe everything (except sd card) and flash the Rom you just transferred to your sd card. Reboot and enjoy.
If you do not have a custom recovery then download one (search) and place it into the same folder on your computer as fastboot. Then plug your phone into the computer and boot to the bootloader. Run this command ( fastboot flash recovery insertname.Img ). After this do the steps I wrote above.
If you have any questions about the above steps then search you will find the answer. If you unlocked your bootloader than your computer obviously sees your phone and adb works well. If you can get your phone into the bootloader then I don't see any reason how your problem cannot be fixed. This leads me to believe your not quite putting forth the effort to search.
Check the stickies in this section and have fun.
Dueces
Sent from my Kindle Fire using xda premium
weehooherod2 said:
Put your phone into fastboot.
Download ClockWorkMod Recovery: http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-crespo.img
Flash clockwork mod recovery in fastboot with this command: fastboot flash recovery C:\where\ever\you\put\the\file.img
Then from fastboot select recovery.
Wipe data/factory reset
Install zip from sdcard: http://download.cyanogenmod.com/get/update-cm-7.1.0.1-NS-signed.zip
Click to expand...
Click to collapse
Beat me to it lol.
Sent from my Kindle Fire using xda premium
How about instead of making a thread with no one helps me in capital letters and bumping it over and over again. You actually put info in your thread. Like what you did. Examples. Unlocked via fastboot with sdk flashed so and so recovery and so on
Or you could have just searched the forum/read another thread about how to fix a phone stuck at google logo because of user error.
Frankly you are lucky anybody even bothered to help you at all.
On a mac here. I think I got a bit over my head here with the 2.20 root. I did all of the bootloader unlocking successfully, installed TWRP, and then downloaded CM10, and flashed the boot.img.
Now when trying to boot the phone I get stock on the screen with "This Build is for development only."
I can get into recovery, but don't really know what to do from there. I'm trying to mount, but can't get the computer to recognize the device. Tried a factory reset and it failed. I'm not quite bricked, but sort of stuck and don't know what to do. I'd love to get CM10 working, but at least I want to be able to use my phone.
I'm pretty new to Android so sorry for newbishness.
Thanks anyone for your help.
Just to add, I'm getting the message "no OS installed" when trying to reboot in recovery.
ul49 said:
On a mac here. I think I got a bit over my head here with the 2.20 root. I did all of the bootloader unlocking successfully, installed TWRP, and then downloaded CM10, and flashed the boot.img.
Now when trying to boot the phone I get stock on the screen with "This Build is for development only."
I can get into recovery, but don't really know what to do from there. I'm trying to mount, but can't get the computer to recognize the device. Tried a factory reset and it failed. I'm not quite bricked, but sort of stuck and don't know what to do. I'd love to get CM10 working, but at least I want to be able to use my phone.
I'm pretty new to Android so sorry for newbishness.
Thanks anyone for your help.
Click to expand...
Click to collapse
Did you flash the boot.img first, then the ROM?
Can you wipe System?
Sorry, what's the difference betwwen boot.img and the rom itself? I only flashed boot.img. I did wipe the system.
ul49 said:
Sorry, what's the difference betwwen boot.img and the rom itself? I only flashed boot.img. I did wipe the system.
Click to expand...
Click to collapse
The boot.img has the kernel in it. If you didn't flash the CM10.zip you have no operating system.
Wipe System, and Factory Reset
Flash boot.img
Flash the CM10.zip, flash google apps, and you should be good after that
Now flash the rom zip from recovery (twrp)
Sent from a slithery smooth phone!
So to flash the zip file for the ROM and gapps, I just enter fastboot flash boot 'rom.zip' or 'gapps.zip'?
Also, what do I do after I've flashed them?
Thanks so much for your help
ul49 said:
So to flash the zip file for the ROM and gapps, I just enter fastboot flash boot 'rom.zip' or 'gapps.zip'?
Also, what do I do after I've flashed them?
Thanks so much for your help
Click to expand...
Click to collapse
no,you flash the boot.img in fastboot, and then you flash the rom.zip and gapps.zip from recovery (twrp)
ul49 said:
So to flash the zip file for the ROM and gapps, I just enter fastboot flash boot 'rom.zip' or 'gapps.zip'?
Also, what do I do after I've flashed them?
Thanks so much for your help
Click to expand...
Click to collapse
No, do a clean wipe.
boot your phone into fastboot
download the fastboot files http://www.mediafire.com/?4dx982z93w8z7wk and extract them to your desktop
on your computer, open up cmd and type
cd desktop
cd foldername (the folder that has fastboot.exe)
fastboot flash boot boot.img
reboot into recovery
flash CM10, flash gapps, reboot
I see. The problem is that I seem to be unable to mount my phone and sd card through recovery.
Trying to push the zips using adb using './adb push cm10.zip/sdcard' but when I enter this command in terminal it seems to just reload adb, and not push the file.
ul49 said:
Trying to push the zips using adb using './adb push cm10.zip/sdcard' but when I enter this command in terminal it seems to just reload adb, and not push the file.
Click to expand...
Click to collapse
I think you are typing the command wrong
./adb push file /destination
or ./adb push cm10.zip /mnt/sdcard
./adb push cm10.zip /sdcard
whatever the mount point is for the sdcard
Tried that too. It just reloads the opening adb dialogue.
ul49 said:
Tried that too. It just reloads the opening adb dialogue.
Click to expand...
Click to collapse
does ./adb devices return your phone as connected?
Well, now it doesn't. Instead of reloading the adb dialogue now, when I try the push command it says device not found. Just came out of nowhere. How do I make it recognize the phone again?
Thanks for bearing with me here. I think I'm really close.
ul49 said:
Well, now it doesn't. Instead of reloading the adb dialogue now, when I try the push command it says device not found. Just came out of nowhere. How do I make it recognize the phone again?
Thanks for bearing with me here. I think I'm really close.
Click to expand...
Click to collapse
I'm not familiar with OS X and android, are there any specific drivers you may need to install?
Are you in your bootloader or recovery?
All necessary drivers were installed. The device was being recognized before, but for some reason isn't now. I'm stuck on the "This build is for development purposes only" screen now since I can't get into recovery or bootloader using adb now since the device isn't recognized...
Ok, I'm connected again somehow. Now just trying to figure out this pushing issue. Entered this command './adb push /android/cm10.zip /sdcard and it looked like it was working then said "failed to copy to /sdcard"
ul49 said:
Ok, I'm connected again somehow. Now just trying to figure out this pushing issue. Entered this command './adb push /android/cm10.zip /sdcard and it looked like it was working then said "failed to copy to /sdcard"
Click to expand...
Click to collapse
because it is probably at /mnt/sdcard
Successfully pushed the files. Of course, I've hit another problem. Trying to install the ROM through TWRP and it's failing. Same with Gapps. I'm seeing "unable to mount /sdcard" and unable to mount storage. I've already cleared cache, wiped system, factory reset/
First time post and it's been a hell of a day. I need to figure out how to either sideload the factory ROM, load a 3rd party ROM, or actually factory reset my phone to stock.
I unlocked my bootloader and installed TWRP and SuperSU earlier in the day. I then wanted to try to load Cyanogen11, but there were issues with the load, it constantly failed. I made a backup before I did this, but when I attempted to load the backup, nothing happened, it would just continually boot to recovery.
I attempted a few other things, clearing caches, doing wipes, powering the phone off for 5~ minutes, etc. etc.
Nothing is working, I can't load any ROM now and phone is either stuck at a bootcycle or the HTC Splash screen (Aside from being able to load bootloader/CWP)
jdolbeer said:
First time post and it's been a hell of a day. I need to figure out how to either sideload the factory ROM, load a 3rd party ROM, or actually factory reset my phone to stock.
I unlocked my bootloader and installed TWRP and SuperSU earlier in the day. I then wanted to try to load Cyanogen11, but there were issues with the load, it constantly failed. I made a backup before I did this, but when I attempted to load the backup, nothing happened, it would just continually boot to recovery.
I attempted a few other things, clearing caches, doing wipes, powering the phone off for 5~ minutes, etc. etc.
Nothing is working, I can't load any ROM now and phone is either stuck at a bootcycle or the HTC Splash screen (Aside from being able to load bootloader/CWP)
Click to expand...
Click to collapse
Are you still having issues? If so, PM me and I'll help you out.....
Got everything sorted with the great help of Nelvin. I had previously gone to the twrp support IRC and after answering a few questions, they just stopped talking... Glad there are people out there still willing to help! He spent a good hour or so with me making sure everything was working.
Hey you two!
Did you solve your problem via PM, then maybe send me the log of it please.
I dont know exactly if we have the same problem, but i'll try to explain mine:
I wanted to put a ROM on my mini, because it is branded.
I unlocked the bootloader on the htc one mini and then put the twrp recovery on it. It seems to work.
Next i wanted to put super su on it, but I'm already stuck in a bootcircle, so i cant put any files onto the phone. I tried to move files with Qick ADB Pusher, but always when I try to send the file from PC(win7) to one mini it says "Opeartion Failed! Exit Code 1". I tried this when i was in Bootloader. When I am in Recovery ADB doesnt even recognize the phone via USB.
If there is more explanation needed, please feel free to ask.
Thank you for your help in advance!
Greetins,
just2lose.
just2lose said:
Hey you two!
Did you solve your problem via PM, then maybe send me the log of it please.
I dont know exactly if we have the same problem, but i'll try to explain mine:
I wanted to put a ROM on my mini, because it is branded.
I unlocked the bootloader on the htc one mini and then put the twrp recovery on it. It seems to work.
Next i wanted to put super su on it, but I'm already stuck in a bootcircle, so i cant put any files onto the phone. I tried to move files with Qick ADB Pusher, but always when I try to send the file from PC(win7) to one mini it says "Opeartion Failed! Exit Code 1". I tried this when i was in Bootloader. When I am in Recovery ADB doesnt even recognize the phone via USB.
If there is more explanation needed, please feel free to ask.
Thank you for your help in advance!
Greetins,
just2lose.
Click to expand...
Click to collapse
Hi, can you let me know: Which ROM you want to flash, if you have attempted to s-off, and that you can boot to recovery?
Also, i'd advise against using utilities like the "pusher", please download this http://d-h.st/qmi and create a directory called c:\adb\ - move your ROM and SuperSU zip files here and extract the adb_windows.zip file to the directory.....
I did not attempt s-off, just normal htc dev bootloader.
First i wanted to flash Magio R4, but then i was thinking about Stock Rom Sense 5.5, which tr1gg3r84 uploaded.
i created folder and moved rom there. i also extracted the adb_windows zip there. what to do next? (i just wanna ask, because im a little scared of totaly breaking the phone now)
Thanks for now!
just2lose said:
I did not attempt s-off, just normal htc dev bootloader.
First i wanted to flash Magio R4, but then i was thinking about Stock Rom Sense 5.5, which tr1gg3r84 uploaded.
i created folder and moved rom there. i also extracted the adb_windows zip there. what to do next? (i just wanna ask, because im a little scared of totaly breaking the phone now)
Thanks for now!
Click to expand...
Click to collapse
Boot to recovery, then
adb push therom.zip /sdcard/
adb push UPDATE-SuperSU.zip /sdcard/
Remember to extract the boot.img from the ROM zip file, and after flashing the ROM and SuperSU, boot to bootloader and FASTBOOT menu then:
fastboot flash boot boot.img
you mean to push with the quick ADB Pusher? but in this programm (on PC) it doesnt find the phone whilie it is is recovery boot.
just2lose said:
you mean to push with the quick ADB Pusher? but in this programm (on PC) it doesnt find the phone whilie it is is recovery boot.
Click to expand...
Click to collapse
No, use the adb binary from the download link I posted......
If your phone isn't found, check the windows device manager and verify that you have ADB Android device listed..... if not, download adb drivers for windows and install - then plug your phone back in.....
You are using TWRP 2.6.0.0 recovery image from here right? http://forum.xda-developers.com/showthread.php?t=2418938
the adb.exe just pops up the cmd console, showing a lot of commands for half a second and then its gone again.
the android device is listed on device manager.
no, i did not use this one(twrp). i used some explanation how to do it from another forum and another file.
should i use this one now? how exactly to do that? theres no explanation :/
Open a command prompt in Windows and cd to c:\adb
Then when your phone is in recovery, type the adb commands I posted earlier.....
Sent from my HTC One mini using XDA Premium 4 mobile app
terdingb all
cmd says that the command is wrong or misstyped
(im in c:/adb typing: adb push rom.zip /sdcard/)
Is your ROM zip file called rom.zip? Can you post a screenshot?
Sent from my HTC One mini using XDA Premium 4 mobile app
ok got it.
now the rom and the supersu.zip are on the phone.
i cleared cache and dalvik and flashed both files(Stock Sense 5.5 4.3 Rooted Odex/Deodex;UPDATE-SuperSU-v1.86; both zip files) and , after that i went into fastboot and tried (fastboot folder) "fastboot flash boot boot.img" but cmd only says "waiting for device"
just2lose said:
ok got it.
now the rom and the supersu.zip are on the phone.
i cleared cache and dalvik and flashed both files(Stock Sense 5.5 4.3 Rooted Odex/Deodex;UPDATE-SuperSU-v1.86; both zip files) and , after that i went into fastboot and tried (fastboot folder) "fastboot flash boot boot.img" but cmd only says "waiting for device"
Click to expand...
Click to collapse
Check device manager on your pc, most likely the adb driver device isn't listed - if not, reboot your pc and try again.... This has happened to me several times......
ok now it worked. writing boot and so on .. finished. total time: 2.717.
i shut it down and started the phone again.
now it almost made the starting sound. after 5 boot cycles it played the whole starting sound and also showed the second screen with the "o1ne" and "beatsaudio" on the bottom.
but thats it. boot cycling in a different way now .
seems like it just doesnt want to work.
i'm so sorry that I am bothering you for so long now..
another idea?
thanks again!
edit: im gonna go through everything again with magio rom r5...
ok got it now. thanks a lot dude!
i deleted the rom files now from the phone but still there is 9gb used on the phone. this is way to much, isnt it?
is there a safe method to clean the whole phone .. something like c:format ?
thanks ³
No problem dood.....
Download an app called diskusage from the store - start it and choose storage card.... Post a screenshot please!
Sent via a weather balloon towed by a flock of seagulls. That's how this messaging stuff works, right?
after the phone went out of battery, it was in a boot cycle again after loading and rebooting.
flashed super su.zip again, but it didnt help. stupid me didnt do a backup yet. so do i have to install the rom again and do all the configs from scretch?
What's your hboot status? Locked/unlocked, s-on/s-off etc
Also, did you do, or install anything before your phone powered off?
Sent from my HTC One mini using XDA Premium 4 mobile app