Related
Problem solved. Thanks to everyone that responded. I really do appreciate it!!!!
What exactly did you flash? The Mainver error only relates to the kernel IIRC.
The only thing I tried to flash was the custom recovery after I accidentally ran the ota update with the custom recovery still on my phone. When I should've flashed back to the stock recovery before accepting the update. And now I can't get into custom recovery. When I try to reflash armon ra it won't take. I've lost root access even though I have superuser still on my phone.
shane8262000 said:
The only thing I tried to flash was the custom recovery after I accidentally ran the ota update with the custom recovery still on my phone. When I should've flashed back to the stock recovery before accepting the update. And now I can't get into custom recovery. When I try to reflash armon ra it won't take. I've lost root access even though I have superuser still on my phone.
Click to expand...
Click to collapse
how are you trying to reflash Amon Ra ? , what recovery do you boot into ? As long as your still unlocked you should be able to flash Amon Ra through Hboot it has nothing to do with root access at that point. Even odder that the OTA flashed through the custom recovery, thought it would error out and not take if it wasn't the stock recovery. Unless you ran Con's Stock rooted, but then you wouldn't have an issue with superuser or root access.
Should be able to flash stock recovery through fastboot relock and RUU then if you really are stuck. Otherwise , no reason you shouldn't be able to reflash Amon Ra and reroot through recovery.
Download THIS
I take it the phone can't boot up at all? Have your tried fastboot flashing the stock kernel?
mjh68 said:
how are you trying to reflash Amon Ra ? , what recovery do you boot into ? As long as your still unlocked you should be able to flash Amon Ra through Hboot it has nothing to do with root access at that point. Even odder that the OTA flashed through the custom recovery, thought it would error out and not take if it wasn't the stock recovery. Unless you ran Con's Stock rooted, but then you wouldn't have an issue with superuser or root access.
Should be able to flash stock recovery through fastboot relock and RUU then if you really are stuck. Otherwise , no reason you shouldn't be able to reflash Amon Ra and reroot through recovery.
Click to expand...
Click to collapse
I'm trying to flash it in hboot as ph98img. And when I go to recovery it seems to go to the stock recovery with the little phone and a green circle but shortly after it turns into the red triangle and phone symbol.
Try flashing the recovery in fastboot. Download the latest version of AmonRa here and extract the recovery-ra-vigor-3.13-gnm.img. Take that file and place it in the same file directory you place the tools to unlock your bootloader (needs to be in the same directory as fastboot.exe).
Put your phone into bootloader and connect to PC and flash the recovery-ra-vigor-3.13-gnm.img in fastboot using the command:
fastboot flash recovery recovery-ra-vigor-3.13-gnm.img
Marcismo55 said:
Download THIS
I take it the phone can't boot up at all? Have your tried fastboot flashing the stock kernel?
Click to expand...
Click to collapse
It will boot and everything runs fine, I just can't get into custom recovery or install custom recovery. And my apps that need superuser permissions won't be allowed even though I still have superuser installed on the phone.
shane8262000 said:
It will boot and everything runs fine, I just can't get into custom recovery or install custom recovery. And my apps that need superuser permissions won't be allowed even though I still have superuser installed on the phone.
Click to expand...
Click to collapse
So you cannot flash the recovery through fastboot?
Marcismo55 said:
So you cannot flash the recovery through fastboot?
Click to expand...
Click to collapse
Nope. It just won't take. I can try it again and tell you exactly what it says as an error if that will help.
Marcismo55 said:
Try flashing the recovery in fastboot. Download the latest version of AmonRa here and extract the recovery-ra-vigor-3.13-gnm.img. Take that file and place it in the same file directory you place the tools to unlock your bootloader (needs to be in the same directory as fastboot.exe).
Put your phone into bootloader and connect to PC and flash the recovery-ra-vigor-3.13-gnm.img in fastboot using the command:
fastboot flash recovery recovery-ra-vigor-3.13-gnm.img
Click to expand...
Click to collapse
I'll try that and get back with you.
shane8262000 said:
I'll try that and get back with you.
Click to expand...
Click to collapse
Marcismo55 said:
Try flashing the recovery in fastboot. Download the latest version of AmonRa here and extract the recovery-ra-vigor-3.13-gnm.img. Take that file and place it in the same file directory you place the tools to unlock your bootloader (needs to be in the same directory as fastboot.exe).
Put your phone into bootloader and connect to PC and flash the recovery-ra-vigor-3.13-gnm.img in fastboot using the command:
fastboot flash recovery recovery-ra-vigor-3.13-gnm.img
Click to expand...
Click to collapse
Hey, when I download that file from your link, it is in .txt format. Am I missing something here?
Marcismo55 said:
Try flashing the recovery in fastboot. Download the latest version of AmonRa here and extract the recovery-ra-vigor-3.13-gnm.img. Take that file and place it in the same file directory you place the tools to unlock your bootloader (needs to be in the same directory as fastboot.exe).
Put your phone into bootloader and connect to PC and flash the recovery-ra-vigor-3.13-gnm.img in fastboot using the command:
fastboot flash recovery recovery-ra-vigor-3.13-gnm.img
Click to expand...
Click to collapse
Problem solved. Thank you very much!!!!
mjh68 said:
how are you trying to reflash Amon Ra ? , what recovery do you boot into ? As long as your still unlocked you should be able to flash Amon Ra through Hboot it has nothing to do with root access at that point. Even odder that the OTA flashed through the custom recovery, thought it would error out and not take if it wasn't the stock recovery. Unless you ran Con's Stock rooted, but then you wouldn't have an issue with superuser or root access.
Should be able to flash stock recovery through fastboot relock and RUU then if you really are stuck. Otherwise , no reason you shouldn't be able to reflash Amon Ra and reroot through recovery.
Click to expand...
Click to collapse
Thank you for the help!
Nice! Glad to help
So stupid me managed to delete my recovery while in fastboot and now I can't get it back, to make matters worse my phone is in a bootloop because I installed a new ROM today that my phone appears to be rejecting. I can still get into fastboot but I can't seem to successfully install a new recovery, I'm S-OFF 1.49 if that matters.
Jep4444 said:
So stupid me managed to delete my recovery while in fastboot and now I can't get it back, to make matters worse my phone is in a bootloop because I installed a new ROM today that my phone appears to be rejecting. I can still get into fastboot but I can't seem to successfully install a new recovery, I'm S-OFF 1.49 if that matters.
Click to expand...
Click to collapse
fastboot flash recovery recovery.img
where recovery.img is inside the zip file of the recovery tool u used
or you can put your recovery tools's pg86img.zip (if you are cdma) on ur sd card and let hboot flsah it for you.
chad.goodman said:
fastboot flash recovery recovery.img
where recovery.img is inside the zip file of the recovery tool u used
or you can put your recovery tools's pg86img.zip (if you are cdma) on ur sd card and let hboot flsah it for you.
Click to expand...
Click to collapse
What do you mean by recovery tool, should i use the recovery.img from my last backup?
My phone's GSM, I'm guessing pf86img won't fix that?
That did the trick, thank you
ok so i reverted back to stock to fix an issue i was having, it worked fine
but then i tried to flash a new version of speed rom to test it out, but then i forgot i need 4EXT to flash my rom
i wiped everything, and since my rom couldn't be flashed im stuck without a rom
ok, simple right? i just flash 4EXT and restore
but i didnt have an unlocked bootloader (even though i have S-OFF an unlocked bootloader is necessary) so i unlocked it, but i didnt have a rom when i unlocked it so i couldnt reboot
so know i cant flash a new recovery because it wont stick,
so i cant use any recovery, and i cant boot up either :/
is there a way to get out of this without going back to the RUU?
Did u try flashing cwm and seeing if that would stick... Just until u can get back running?
Sent from my HTC_Amaze_4G using xda premium
What are you using to flash the recovery? If you're trying to do it via fastboot commands it won't stick, trust me, I tried, use hasoon's tool, that seems to stick, oddly enough I switched out one of the image files with 4EXT but it still doesn't stick, anyways use the tool and flash cwm, restore then you can install 4EXT via recovery updater once you've got yourself a booted rom.
EclipzeRemix said:
ok so i reverted back to stock to fix an issue i was having, it worked fine
but then i tried to flash a new version of speed rom to test it out, but then i forgot i need 4EXT to flash my rom
i wiped everything, and since my rom couldn't be flashed im stuck without a rom
ok, simple right? i just flash 4EXT and restore
but i didnt have an unlocked bootloader (even though i have S-OFF an unlocked bootloader is necessary) so i unlocked it, but i didnt have a rom when i unlocked it so i couldnt reboot
so know i cant flash a new recovery because it wont stick,
so i cant use any recovery, and i cant boot up either :/
is there a way to get out of this without going back to the RUU?
Click to expand...
Click to collapse
Question: Why don't you want to go back to the RUU?
The only thing I can think of is trying to extract your nandroid backups and then flash the stuff from the backups through fastboot. Don't ask me how to convert the data.ext4.tar and system.ext4.tar into an img file, I do not know how to do that, sorry :/
But if you do figure out how to convert them, flash them as follows:
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
If you're lucky, you may be able to boot up, and then after that, reflash the recovery.
Alternatively, you could try
fastboot erase recovery
then
fastboot flash recovery recovery.img
and see if that sticks
(DO NOT TRY THIS IF YOU DON'T HAVE AN ENG BOOTLOADER, AS IT MAY NOT ALLOW YOU TO FLASH THE RECOVERY)
That's all I can think of right now. I'll try to come up with more ideas later.
i tried all of the above
i dont want to reflash the stock RUU -_-, i have to many files to transfer
U may not have a choice.
Either way... U should know that your phone isn't bricked dude... It turns on.
Sent from my HTC_Amaze_4G using xda premium
i know its not hard bricked, but i really dont want to relock my freaking bootloader again and reflash the ENG bootloader -_-
i still cant believe there isnt a easy method to flash a rom through fastboot -_-
Keylogger_0 said:
Question: Why don't you want to go back to the RUU?
The only thing I can think of is trying to extract your nandroid backups and then flash the stuff from the backups through fastboot. Don't ask me how to convert the data.ext4.tar and system.ext4.tar into an img file, I do not know how to do that, sorry :/
But if you do figure out how to convert them, flash them as follows:
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
If you're lucky, you may be able to boot up, and then after that, reflash the recovery.
Alternatively, you could try
fastboot erase recovery
then
fastboot flash recovery recovery.img
and see if that sticks
(DO NOT TRY THIS IF YOU DON'T HAVE AN ENG BOOTLOADER, AS IT MAY NOT ALLOW YOU TO FLASH THE RECOVERY)
That's all I can think of right now. I'll try to come up with more ideas later.
Click to expand...
Click to collapse
thanks man this actaully helped alot! and for your future use changing it to .img is simple, just rename the extention
my phone cant use fastboot commands at all!, none of them stick -_-
my phone still wont boot
EclipzeRemix said:
my phone cant use fastboot commands at all!, none of them stick -_-
my phone still wont boot
Click to expand...
Click to collapse
unless you get failed pu or your phone wont turn on at all, youre not bricked. flash the ruu and be done with it...
EclipzeRemix said:
i know its not hard bricked, but i really dont want to relock my freaking bootloader again and reflash the ENG bootloader -_-
i still cant believe there isnt a easy method to flash a rom through fastboot -_-
Click to expand...
Click to collapse
If you have the ruu you should be able to replace the recovery.img(or at least remove the one in it) and remove the hboot image, that way you won't have to reflash eng hboot.. I can find the link to the original leak that I flashed, but they simply took out the recovery and hboot image from the zip- it saves some steps.
As much time as you've probably spent doing everything else you probably could have done it 3 times already! LOL. I love you man. Haha.
haha -_- thats true
ok so now im really stuck because i have no way of getting the RUU in my sd card -_-
EclipzeRemix said:
ok so now im really stuck because i have no way of getting the RUU in my sd card -_-
Click to expand...
Click to collapse
You don't have a card reader, or some old phone that can connect by usb? You only need it on the external - I have a feeling that is why it goes on the external, the phone may not boot into anything, but you can alter the external without it.
And I think there is a fastboot push command or something like that, isn't there?
no ;( the only phone near me is my bro's One S
wow im so pissed
EclipzeRemix said:
no ;( the only phone near me is my bro's One S
wow im so pissed
Click to expand...
Click to collapse
Turn it on, put in your microsd, copy the file to it with usb cable or adbwireless, make sure it is on root of microsd, put back in your phone..
HTC one + sdcard = profit?!
Silentbtdeadly said:
Turn it on, put in your microsd, copy the file to it with usb cable or adbwireless, make sure it is on root of microsd, put back in your phone..
HTC one + sdcard = profit?!
Click to expand...
Click to collapse
the one s doesnt have an sd card slot lol
EclipzeRemix said:
the one s doesnt have an sd card slot lol
Click to expand...
Click to collapse
OH YEA. I forgot that was part of why I decided those phones suck. If they had removable battery and sdcard.. oh well. you're screwed.
So right now you don't have eng hboot flashed right? Because that is the ONLY reason that you can't flash recovery or other things with fastboot commands - if you don't, flash that, then you can flash recovery that will stick, then you can reboot into recovery, adb push the file you need, or restore a nandroid.. Just sayin.
no i have always had ENG hboot, and im unlocked,i dunno why it doesnt stick
Open cmd. Put ruu file in same directory where the cmd is running.
Fastboot oem rebootRUU
Fastboot flash zip (ruu filename here).zip
Wait until it completes. You may have to do it twice. After that's done, you'll have a stock rom.
Boot into it and then load up the eng hboot to the sdcard, rename it to PH85img.zip or whatever is correct, then reboot into bootloader, let it flash.
After all that is done, you should have an eng hboot. The next step would be to flash a custom recovery. I'll let you do the rest.
Sent from my HTC_Amaze_4G using XDA
Helloo xda developer forums!
I have a problem with my GSM HTC evo 3d when flashing new roms :crying:
I unlocked it the htc way, installed 4ext touch recovery and
rooted my stock rom using the superuser app.
But whenever i try to flash boot.img from a custom rom,
nothing changes. i tried rebooting several times but i
still have the same rom!!!
Whenever i type fastboot flash boot boot.img this happens:
sending 'boot' (4852 KB)...
OKAY [ 0.931s]
writing 'boot'...
OKAY [ 4.506s]
finished. total time: 5.439s
I am a true noob at android stuff so if i made any stupid mistakes please help me or direct me to the right thread so i wont make stupid mistake anymore
Thank you for your help in advance!!
More info would be helpfully, firstly what is your hboot? Are you s-on or s-off? What Rom did you flash? You are have issues with bootloops after you flash a rom?
(My evil evo is snake bitten by venom sense 4.1 rom and also infected with THE kernel,don't ask me for help, as I couldn't care less if you phone explodes)
Jaklo said:
Helloo xda developer forums!
I have a problem with my GSM HTC evo 3d when flashing new roms :crying:
I unlocked it the htc way, installed 4ext touch recovery and
rooted my stock rom using the superuser app.
But whenever i try to flash boot.img from a custom rom,
nothing changes. i tried rebooting several times but i
still have the same rom!!!
Whenever i type fastboot flash boot boot.img this happens:
sending 'boot' (4852 KB)...
OKAY [ 0.931s]
writing 'boot'...
OKAY [ 4.506s]
finished. total time: 5.439s
I am a true noob at android stuff so if i made any stupid mistakes please help me or direct me to the right thread so i wont make stupid mistake anymore
Thank you for your help in advance!!
Click to expand...
Click to collapse
re-read the steps on flashing a ROM...youll find out you need more than just the boot.img file to do it... only time you should have to flash the boot.img is when a new rom is installed but wont boot up...if your phone still boots then youre not installing the ROM properly
You need to supply the information that flashallthetime requested, but you should also be aware that flashing boot.img from fastboot does not flash the ROM and doesn't even flash all the files associated with the kernel. The attached screenshot of the warning that comes up in 4EXT when selecting the "flash boot.img" option expains it better than I can.
If you are S-ON, the proper way to flash a ROM is to "fastboot boot recovery.img" then flash the entire ROM .zip file from recovery, or use 4EXT with the S-ON (SmartFlash) option enabled. You can tell that SmartFlash is working by watching to see if your phone boots twice after your exit recovery. The first boot is used to flash the boot partition and the second boot loads the new kernel and ROM.
Don't confuse the complete kernel with boot.img, which is only one of the files required.
ramjet73
thank you for your replies!!
flashallthetime my hboot version is 1.53.0007 and i am s-on.
I tried to flash the Cool-ICS and the cerom.
ramjet73 i tried flashing several diffrent roms(inclucing both of the above) with the 4ext smartflash enabled, but i only got to the animation an then
the whole process froze. And thank you for the explenation with fastboot i was only flashing the boot.img
i guess this is a total noob question but when i type fastboot boot recovery.img it says thatit cannot load recovery.img Where do i get this file from?
Or can you please link me to the thread with more noob friendly info on flashing roms with s-on?
Jaklo said:
thank you for your replies!!
ramjet73 i tried flashing several diffrent roms(inclucing both of the above) with the 4ext smartflash enabled, but i only got to the animation an then
the whole process froze. And thank you for the explenation with fastboot i was only flashing the boot.img
i guess this is a total noob question but when i type fastboot boot recovery.img it says thatit cannot load recovery.img Where do i get this file from?
Or can you please link me to the thread with more noob friendly info on flashing roms with s-on?
Click to expand...
Click to collapse
I'm not familiar with the S-ON flashing guides for GSM which will be a little different than those for CDMA, so someone else will have to help with that, but you can get the recovery.img file for 4EXT that you need from the OP of the XDA thread. It's right above the other download links on that page. Look for the following sentence that has the download link embedded:
If you somehow lost those files, there's a direct download for a version you can flash via fastboot.
Click to expand...
Click to collapse
ramjet73
the "fastboot boot recovery.img" is just a command to get into recovery. You could also use the command "adb reboot recovery" (unless you are in bootloader mode)
I think the problem is your hboot. loads of people have problems with the newer roms because of the 1.53.xxxx hboot
EM|NEM said:
the "fastboot boot recovery.img" is just a command to get into recovery. You could also use the command "adb reboot recovery" (unless you are in bootloader mode)
I think the problem is your hboot. loads of people have problems with the newer roms because of the 1.53.xxxx hboot
Click to expand...
Click to collapse
Thanks again for the quick replies!!!
Ok i got it, but if i am in fastboot and execute fastboot boot recovery.img i get an error , but if i execcute the adb command i get into the recovery normaly.
Have you got any idea on how to fix the hboot problems?
If not is there any easy way of downgrading the hboot except the wire trick becose it looks very dangerous and i realy dont wanna brick my phone.
Jaklo said:
Ok i got it, but if i am in fastboot and execute fastboot boot recovery.img i get an error , but if i execcute the adb command i get into the recovery normaly.
Have you got any idea on how to fix those problems?
If not is there any easy way of downgrading the hboot except the wire trick becose it looks very dangerous and i realy dont wanna brick my phone.
Click to expand...
Click to collapse
What error do you get when you try the "fastboot boot recovery.img" command? You have to be in the "fastboot USB" mode in the bootloader to run fastboot commands and if you were the ADB commands wouldn't work which require being booted into Android with "debug" on in the developer settings.
ramjet73
ramjet73 said:
What error do you get when you try the "fastboot boot recovery.img" command? You have to be in the "fastboot USB" mode in the bootloader to run fastboot commands and if you were the ADB commands wouldn't work which require being booted into Android with "debug" on in the developer settings.
ramjet73
Click to expand...
Click to collapse
i know that i have to be in fastboot usb mode
it gives me cannot load recovery.img error.
Buuuuut i finaly managed to install yoda´ s ICS custom ROM and EVERYTHING workssss
THX guys
Theres no way to downgrade your hboot without the wire trick my friend. you need s-off to downgrade your hboot. any older hboot could have easily been downgraded and then s-offed
I would suggest you try some other rom. This ones a pretty good rom (sense 4.1 but no 3d) and i'm sure it works with s-on/1.53
http://beta.androidfilehost.com/?fid=9390113915771289764
as always wipe then flash rom in recovery
then flash boot.img from fastboot and reboot
---------- Post added at 03:50 AM ---------- Previous post was at 03:46 AM ----------
oh good you already did another rom. good for you
EM|NEM said:
as always wipe then flash rom in recovery
then flash boot.img from fastboot and reboot
Click to expand...
Click to collapse
ok sorry for a noob question but does wipe mean factory data reset?
that is what i meant. do factory data reset and wipe dalvik cache as well
ramjet73 said:
What error do you get when you try the "fastboot boot recovery.img" command? You have to be in the "fastboot USB" mode in the bootloader to run fastboot commands and if you were the ADB commands wouldn't work which require being booted into Android with "debug" on in the developer settings.
ramjet73
Click to expand...
Click to collapse
The OP cant load his recovery because he might not have a file named "recovery.img" in his fastboot/adb folder.
Flashing a boot.img is just the part of flashing ROM, especialy on S-On state. It still has not flashing your ROM, until you "update from *.zip file" from recovery.
Eh, can someone please upload the latest 4ext recovery PG86IMG.zip for me? I want to flash a new ROM, but it requires 4ext. The system bootloops so I can't get it the normal way.
I found one around here, but it's for CDMA and my bootloader told me to go eat a rock. So GSM, please.
Cheers!
xXx420SwegQuickScopesxXx said:
Eh, can someone please upload the latest 4ext recovery PG86IMG.zip for me? I want to flash a new ROM, but it requires 4ext. The system bootloops so I can't get it the normal way.
I found one around here, but it's for CDMA and my bootloader told me to go eat a rock. So GSM, please.
Cheers!
Click to expand...
Click to collapse
Can u tell us ur HBoot and S-on or S-off
Try to flash other recovery , install a stock rom then install 4ext.I was in same problem too
http://4ext.net/ddl/shooteru/recovery.zip
please note this is not a PG86IMG file. you have to extract recovery.img and flash via your pc using cmd. put your phone is fastboot and use this command in cmd
fastboot flash recovery recovery.img
make sure you have drivers for phone installed
XeNNz said:
Can u tell us ur HBoot and S-on or S-off
Try to flash other recovery , install a stock rom then install 4ext.I was in same problem too
Click to expand...
Click to collapse
HBoot 1.49.1107, S-Off. I was thinking of going that way, but that seems too much of a hassle for something that could be simply downloaded.
EM|NEM said:
please note this is not a PG86IMG file. you have to extract recovery.img and flash via your pc using cmd. put your phone is fastboot and use this command in cmd
fastboot flash recovery recovery.img
make sure you have drivers for phone installed
Click to expand...
Click to collapse
Thanks, I'll try this out right now.
Edit: I ended up flashing with fastboot, then installing an older version of the ROM, then installing recovery from the app and only THEN the ROM version I wanted. Apparently the latest version required the most recent 4ext, I'm dazed and confused but everything is working now.
Haven't used the phone for an year or so, restoring some old SMS messages out of the nandroid backup brought up some memories. Now I'll be using it to test my mobile app. Thanks again!
now that you can boot your rom, download 4ext Recovery Updater and update to latest version of 4ext from there