Related
I am on haykuros rom right now and i am wondering if i could download a jf rom, rename it to update.zip and flash it to get back to jf, instead of doing all of that fastboot stuff.
cookiemonster55 said:
I am on haykuros rom right now and i am wondering if i could download a jf rom, rename it to update.zip and flash it to get back to jf, instead of doing all of that fastboot stuff.
Click to expand...
Click to collapse
what fastboot stuff are you talking about?
and i dont see why not, although i havnt tried, i didnt do anything using fastboot to goto haykuros 5.0.2 (i just did a wipe), so i cant see why i couldnt just do the same to goto jf 1.42
wootroot said:
what fastboot stuff are you talking about?
and i dont see why not, although i havnt tried, i didnt do anything using fastboot to goto haykuros 5.0.2 (i just did a wipe), so i cant see why i couldnt just do the same to goto jf 1.42
Click to expand...
Click to collapse
on haykuros website to go back to jf he says you have to do this
PHP:
After playing with my ROMs, and if you don’t like them or for whatever reason you feel you want to go back, you can revert back at any time using fastboot.
Open a command prompt (Start -> Run, and type in “cmd”) and type in:
adb shell reboot bootloader
This will boot you, easily, into the SPL (as opposed to power off, holding CAMERA then power on.)
Now in the same command prompt navigate to where you have your nandroid backup (you need boot.img, data.img, and system.img) type in:
fastboot erase boot
fastboot erase system –w
fastboot flash system system.img
fastboot flash userdata data.img
fastboot flash boot boot.img
fastboot reboot
That’s it! You are now back to your original state!
i just want to put jf on it as update.zip and flash
cookiemonster55 said:
on haykuros website to go back to jf he says you have to do this
PHP:
After playing with my ROMs, and if you don’t like them or for whatever reason you feel you want to go back, you can revert back at any time using fastboot.
Open a command prompt (Start -> Run, and type in “cmd”) and type in:
adb shell reboot bootloader
This will boot you, easily, into the SPL (as opposed to power off, holding CAMERA then power on.)
Now in the same command prompt navigate to where you have your nandroid backup (you need boot.img, data.img, and system.img) type in:
fastboot erase boot
fastboot erase system –w
fastboot flash system system.img
fastboot flash userdata data.img
fastboot flash boot boot.img
fastboot reboot
That’s it! You are now back to your original state!
i just want to put jf on it as update.zip and flash
Click to expand...
Click to collapse
oh gotcha, never knew that
well you could get stuck on a flashing android, but even then you could still go do the fastboot stuff, and is there a reason against using the fastboot method? ive found fastboot to be a very reliable way of doing things, and if haykuro suggests you to do it that way, then id assume thats the best possible way of doing things
if you try to just flash the update.zip, let me know how it goes, im curious
The purpose of the "fastboot stuff" is to restore from a nandroid backup. You can flash with an update.zip of any jf version and be just fine.
yes, ive done it, worked fine, except you'll want to reflash to the radio jf has out there, if you've updated the radio. Which i know i did, the old radio has issues with 1.5
Just copy update.zip on the SD CARD of rooted Magic and install it.
It works fine for me. Hope this will help you
ilvolodel said:
Just copy update.zip on the SD CARD of rooted Magic and install it.
It works fine for me. Hope this will help you
Click to expand...
Click to collapse
????
why open a new thread for this ????
what new on 6.0r1 in compare to the original magic rom
well, theme and Exchange configurations for email, that doesn't works for now (for me.)
not working wifi and BT, it's not good for magic
look nice but same problem wifi and blut no working.
but now im trying to revert back to my backup with this comands
fastboot erase system -w
fastboot erase boot
fastboot flash system system.img
fastboot flash userdata data.img
fastboot flash boot boot.img
fastboot reboot
and it gives a "failed (remote signature verify fail) at the "flash user data.img and fastboot flash boot boot.img"
and after fastboot reboot i am stuck with the vodafone logo on the scrren, bum.
helppppppppppp
guinnes.s said:
look nice but same problem wifi and blut no working.
but now im trying to revert back to my backup with this comands
fastboot erase system -w
fastboot erase boot
fastboot flash system system.img
fastboot flash userdata data.img
fastboot flash boot boot.img
fastboot reboot
and it gives a "failed (remote signature verify fail) at the "flash user data.img and fastboot flash boot boot.img"
and after fastboot reboot i am stuck with the vodafone logo on the scrren, bum.
helppppppppppp
Click to expand...
Click to collapse
install the new SPL
is this the one?
http://code.google.com/p/sapphire-port-dream/
i did try apply the new SPL and not it is stuck at
"Formatting CACHE"
what to do now?
guinnes.s said:
i did try apply the new SPL and not it is stuck at
"Formatting CACHE"
what to do now?
Click to expand...
Click to collapse
If you have prompt to reboot avaible...reboot, it's done!
YAP sorted ,thak you HYKURO, i did restore back to my previous back up.
lots of learning with this Android business lol lol
I flashed the new RADIO and SPL,but forgot to flash a new recovery in HBOOT model. The flash was totally succeed (because after fashing,I tap "fastboot reboot-bootloader" command in HBOOT and it could reboot automatically into hboot model and I can see the new RADIO and SPL had been fashed.
But here comes the problem, I try to reboot my phone into recovery model to flash the new ROM, but no matter I press HOME+POWER or BACK+POWER this time, it reboots again and again at first boot screen, and donnot have any response with the key I tapped!
God! is that bricked? No please don't tell me it's true!
so to clarify, you didn't flash a recovery image and now you don't know why you can't boot to recovery?
boot to fastboot, flash the recovery only, reboot to recovery, flash the rom of your choice and enjoy
Of course, but I cannot boot into fastboot or recovery model now.
nabor said:
Of course, but I cannot boot into fastboot or recovery model now.
Click to expand...
Click to collapse
*facepalm*
if you can't get into fastboot and you can't get into recovery you just bricked your phone.
while it's bootlooping, can you adb devices and tell us what you get?
i'm surprised that it's bricked because you forgot to flash a recovery, would have thought you could still access fastboot...
I was surprised too.
I don't know why,but I can boot into fastboot model now, but my recovery and rom are still broken.
So I tried to type "fastboot boot recovery.img" on my computer, so that I can enter recovery temporary, but here comes another trouble, it can't mount sdcard now! Display "Can't mount /dev/block/mmcblk0p1(or /dev/block/mmcblk0)(No such file or directroy) E:Can't mount SDCARD
!"
So can I use adb shell to install a ROM???
calm down bro....
you didn't brick your phone...
i've same problem after I flashed the new radio SPL HBOOT and recovery...
I've used Hero Recovery...
after u flashed your handset with new radio SPL HBOOT and Recovery, the ROM file DELETED....
so, u just download new rom (that have SAME RADIO HBOOT and Recovery with your handset)
after finished the download, put the file into ROOT SDCard... and then flash it from your RECOVERY....
I've used HERO RECOVERY....
my handset is HTC MAGIC 32A
just do that, if the problem same with me....
BRAVO
nabor said:
I flashed the new RADIO and SPL,but forgot to flash a new recovery in HBOOT model. The flash was totally succeed (because after fashing,I tap "fastboot reboot-bootloader" command in HBOOT and it could reboot automatically into hboot model and I can see the new RADIO and SPL had been fashed.
But here comes the problem, I try to reboot my phone into recovery model to flash the new ROM, but no matter I press HOME+POWER or BACK+POWER this time, it reboots again and again at first boot screen, and donnot have any response with the key I tapped!
God! is that bricked? No please don't tell me it's true!
Click to expand...
Click to collapse
the command is
fastboot flash radio Radio_HTC_PVT_32A_6.35.10.18.img
fastboot flash hboot hboot-1.76.2007.img
fastboot flash recovery recovery-RA-hero-v1.5.2.img
fastboot erase system -w
fastboot reboot-bootloader
read from this thread
http://forum.xda-developers.com/showthread.php?t=605239
download all files you need....
better use last recovery.... (1.5.2 isn't last recovery)
I don't recall the OP mentioning what handset they have. If its the MyTouch 3G Limited Edition or 1.2 (has headphone jack on top) a new user to rooting may confuse that with a Magic 32A in which case your instructions without clarifying would surely brick his phone. (Though he's on Fido, so not likely to be a MyTouch, but he didn't even mention of it was a Magic, Hero, G1, or if it was a DVT board instead of a PVT)
LoGaY said:
the command is
fastboot flash radio Radio_HTC_PVT_32A_6.35.10.18.img
fastboot flash hboot hboot-1.76.2007.img
fastboot flash recovery recovery-RA-hero-v1.5.2.img
fastboot erase system -w
fastboot reboot-bootloader
read from this thread
http://forum.xda-developers.com/showthread.php?t=605239
download all files you need....
better use last recovery.... (1.5.2 isn't last recovery)
Click to expand...
Click to collapse
LoGaY said:
the command is
fastboot flash radio Radio_HTC_PVT_32A_6.35.10.18.img
fastboot flash hboot hboot-1.76.2007.img
fastboot flash recovery recovery-RA-hero-v1.5.2.img
fastboot erase system -w
fastboot reboot-bootloader
read from this thread
http://forum.xda-developers.com/showthread.php?t=605239
download all files you need....
better use last recovery.... (1.5.2 isn't last recovery)
Click to expand...
Click to collapse
You shouldn't offer instructions like this. You have no idea what phone he's using. You offer such a high risk of bricking the phone since most members here fail to read instructions before running a bunch of commands.
He's fido like the above guy said which could mean he's using a rogers magic, but it's also unlikely. Fido doesn't have Magic, so he definitely got it off someone. And since it's rootable (it is unlikely that he could get a hands on a rooted magic here since their lame update) it has a high chance that its from tmo or something which = 32B board.
my phone is htc magic with 32A and it's ENG S-ON so I can't flash a recovery through fastboot, so I have to use "fastboot boot recovery.img" to use a recovery temporary just I said above. I do know that I can put a rom into a sdcard to flash it, but it can't mount sdcard now
Try waiting 30-60 seconds before accessing the SD card. Some recovery images take a while to mount the card.
A few days ago, a friend present a G2 magic to me, it could be used normally.
However, when i want to flash ROM, i found it could not supports SDCARD in system and in recovery mode, only in fastboot mode.
I got the information in fastboot mode:32B ENG S-ON H ; HBOOT-1.33.2010; CPLD-10; RADIO-3.22.20.17;
You know, it is so interesting, because i could not match the RUU in the list. I think 32B is wrong, because i downloaded the 1.6.2g.img recovery and flash in fastboot mode, it is fake. but 1.6.2h.img is right after i boot the recovery.
First of all, I want to edit S-ON to OFF, for i read some articles in much android BBS, once it will be OFF, the G2 could support SDCARD in recovery mode again and flash other ROM.
I made a goldcard and copy the 2.53.707.2 sappimg.zip in the SDCARD, in fastboot mode, the system rebuilded again. i could power on the phone normally, and it could not support SDCARD.
in adb shell and fastboot mode, i try again to cover orginal hboot with the signed hboot.img(spl-1.33.2010) to OFF, but i failed.
what shall i do? i am nearly crying now.
fastboot oem enableqxdm 0
Good thing u reverted to stock SPL. Now the above option might not work.
the 32B is not wrong , the radio is. Flash a 2.xx.xx.xx radio and all will be well.
thanks eyegor
i followed your way, but it was failed. because it showed: signature verify fail.
In fastboot mode, input fastboot erase radio and fastboot flash radio radio.img
is it right?
i think the reason of verify fail is spl-ON.
hi
I would like to install twrp image, but adb says device not found, while on the list it sees, the serial nr is there..
I can even install the img, it writes 2x the okay, but doesn't boot. I'm stuck on fastboot screen, can I fix it?
When at the bootloader, you need to use fastboot commands, not adb.
So the command should be "fastboot boot imgname.img"
Hunter3U said:
When at the bootloader, you need to use fastboot commands, not adb.
So the command should be "fastboot boot imgname.img"
Click to expand...
Click to collapse
+1 for this.
Folks often mix up fastboot and adb. They are related, but different. Different operation requirements and functions.
adb:
- Only works in OS, or alternately in TWRP.
- Requires debugging toggled on in settings.
Fastboot:
- Only works in bootloader-fastboot mode.
- Does not require debugging to be toggled on.
Fastboot is typically what you want for unlocking bootloader, and booting TWRP (for root, etc.).
---------- Post added at 09:04 AM ---------- Previous post was at 09:00 AM ----------
ii9 said:
adb says device not found
I can even install the img, it writes 2x the okay, but doesn't boot. I'm stuck on fastboot screen, can I fix it?
Click to expand...
Click to collapse
Not completely clear based on your description. But is sounds like you are trying to do "adb devices" and then "fastboot flash twrp.img"?
In fastboot, you want to do "fastboot devices" (no quotes) and should see the phone's ID number in response.
Then you want to do "fastboot boot twrp.img" to boot TWRP, then flash the TWRP installer zip within TWRP. This is per the recommended install guide from the TWRP thread: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Although it's hard to determine exactly what you did wrong, unless you provide a more detailed sequence of what you did, and with the exact commands.
And to be clear, your bootloader is unlocked, correct?
well, sorry for being noob, for me was never a problem with older phones. I always managed to root, put twrp, change rom without any pc, but this double slot system kills me
so I managed to wipe everything before, vendor, sytem.., all
I wanted to put the havoc rom after formatting, but there was 5 local disks when I opened the phone folder on the pc, and obviously didn't copy the files on it. Therefore I did reboot to recovery, since that I had only the fastboot screen.
After that I unbricked it, all was fine again on the stock
After opened again the bootloader (yes, also before it was) installed the twrp.img, Installed the twrp zip, reboot it.
I followed the steps from havoc, but it said error 7, few times I tried. I reboooted the recovery again, and now I'm again the fastboot only, doesn't even show the warning msg about open bl, and doesn't go anywhere again.
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
So I'm affraid I need to unbrick again.
If You can help me out, I'd apprecite :good: thanks!
Edit: I'm doing the unbrick again, but this time I'll wait for some info before I try the havoc. Also I'd love to get rid off this double slot thing, is there any way to do the normal method?
ii9 said:
*SNIP*
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
So I'm affraid I need to unbrick again.
If You can help me out, I'd apprecite :good: thanks!
Edit: I'm doing the unbrick again, but this time I'll wait for some info before I try the havoc. Also I'd love to get rid off this double slot thing, is there any way to do the normal method?
Click to expand...
Click to collapse
I ran into the same error (and I have not been able to narrow down what causes it), and I had to fastboot flash boot twrp.img and actually flash TWRP to boot.
Once you flash TWRP to boot, and reboot your phone, you will be dropped right into TWRP.
Once in TWRP I was able to flash the stock boot image, then flash the TWRP installer zip, and finally Magisk. Basically you need to follow the instructions in the TWRP thread, with the only difference being that you flash TWRP to boot and not use fastboot boot. I hope to look into what the possible causes for this failure could be this weekend.
As for getting rid of slot A/B -- nope. That is part of the bootloader, so you will just have to get used to it. It is actually quite useful once you get the hang of it. For example, dual booting if you never intend to take OTA updates. It requires a bit of work to get setup (for example, you have to partition userdata since there is no userdata_a and userdata_b), and you need kernels and ROMs that understand the partitioning scheme.
-- Brian
Did you do fastboot flash boot imagename or fastboot flash recovery imagename
runningnak3d said:
I ran into the same error (and I have not been able to narrow down what causes it), and I had to fastboot flash boot twrp.img and actually flash TWRP to boot.
Once you flash TWRP to boot, and reboot your phone, you will be dropped right into TWRP.
Once in TWRP I was able to flash the stock boot image, then flash the TWRP installer zip, and finally Magisk. Basically you need to follow the instructions in the TWRP thread, with the only difference being that you flash TWRP to boot and not use fastboot boot. I hope to look into what the possible causes for this failure could be this weekend.
As for getting rid of slot A/B -- nope. That is part of the bootloader, so you will just have to get used to it. It is actually quite useful once you get the hang of it. For example, dual booting if you never intend to take OTA updates. It requires a bit of work to get setup (for example, you have to partition userdata since there is no userdata_a and userdata_b), and you need kernels and ROMs that understand the partitioning scheme.
-- Brian
Click to expand...
Click to collapse
I guess I lost it, time to accept the stock rom :crying:
I' not that old, but I can understand now why my grandma doesn't know even what is a phone
At the end I managed to do the unbrick again, after I installed havoc, I get rid of the error 7, and it showed me st like qualcomm crashdump, I was about to give up, but I went back to twrp installed again, now it's fine. Such a pity that it's not stable yet, I don't dare to touch after this..
tHanks for the info, in case I'll ever need I'll try to read again another 100x maybe I'll find out.
Bradl79 said:
Did you do fastboot flash boot imagename or fastboot flash recovery imagename
Click to expand...
Click to collapse
fastboot flash boot imagename
I did this
ii9 said:
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
Click to expand...
Click to collapse
I think you are doing something wrong.
boot.img is basically a kernel, not TWRP.
Booting TWRP and flashing a boot.img are two completely different things.
It would help if you cut/paste the actual command you typed, so we can see what you did.
The command should be: fastboot boot twrp.img
That isn't what you did.
---------- Post added at 11:55 AM ---------- Previous post was at 11:48 AM ----------
ii9 said:
fastboot flash boot imagename
I did this
Click to expand...
Click to collapse
Nobody told you to do this.
The proper syntax is:
fastboot boot twrp.img
Seems similar, but this does something very different from the command you used. Syntax in fastboot/adb is absolutely ciritical. Always type fastboot and adb commands exactly as indicated, and double check everything before issuing the command.
fastboot boot twrp.img This boots the image file that is named. Note that you are not flashing anything with this command. Think of it as a remote boot of the TWRP file that is on your computer.
fastboot flash boot imagename This flashes the named file to the boot partition (basically the kernel)
If Havoc is the end goal here, from absolute stock start to finish it would be
1. Enable developer options
2. Enable oem unlock and usb debugging through the developer options menu (I also enable advanced reboot but not required)
3. Reboot to bootloader via the advanced reboot menu or through adb command "adb reboot bootloader"
4. While in bootloader, type in cmd, "fastboot oem unlock"
5. Allow bootloader unlock and wipe and let system reboot back to oos
6. Repeat steps 1-3 to get back to bootloader
7. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
8. Wipe Data and Dalvik (after data wipe, you might not be able to copy files to phone)
9. Reboot back to bootloader
10. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
11. Copy Havoc, TWRP.zip, GAPPS, Magisk to device (GAPPS and Magisk are optional...if not needed, skip the steps for them)
12. Flash Havoc and TWRP.zip through normal install process
13. Reboot to recovery
14. Flash Havoc and TWRP.zip through normal install process again
15. Reboot to recovery
16. Flash GAPPS and Magisk (If error 70 thrown with GAPPS install, reboot to system once and run through any setup then reboot back to recovery to flash)
17. Reboot system
As long as no other errors are thrown, you should now be in Havoc with GAPPS and Magisk installed
redpoint73 said:
Nobody told you to do this.
The proper syntax is:
fastboot boot twrp.img
Click to expand...
Click to collapse
Sorry, I messed up with the copy and paste, I didn't sleep too much in the last days for the hot, I'm a bit heavy in the head, pls exuse my bs. I also tried this one that you wrote, but didn't manage to boot still.. I have no clue what went wrong, but again, thanks, in case I can come back to read again.
Hunter3U said:
If Havoc is the end goal here, from absolute stock start to finish it would be
1. Enable developer options
2. Enable oem unlock and usb debugging through the developer options menu (I also enable advanced reboot but not required)
3. Reboot to bootloader via the advanced reboot menu or through adb command "adb reboot bootloader"
4. While in bootloader, type in cmd, "fastboot oem unlock"
5. Allow bootloader unlock and wipe and let system reboot back to oos
6. Repeat steps 1-3 to get back to bootloader
7. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
8. Wipe Data and Dalvik (after data wipe, you might not be able to copy files to phone)
9. Reboot back to bootloader
10. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
11. Copy Havoc, TWRP.zip, GAPPS, Magisk to device (GAPPS and Magisk are optional...if not needed, skip the steps for them)
12. Flash Havoc and TWRP.zip through normal install process
13. Reboot to recovery
14. Flash Havoc and TWRP.zip through normal install process again
15. Reboot to recovery
16. Flash GAPPS and Magisk (If error 70 thrown with GAPPS install, reboot to system once and run through any setup then reboot back to recovery to flash)
17. Reboot system
As long as no other errors are thrown, you should now be in Havoc with GAPPS and Magisk installed
Click to expand...
Click to collapse
Not exactly, the end goal to have a clean rom, with basic custumization, that even stock should include in my opinion, like disable headups.., extended screen etc. Plus without google staff, for me it's too strict. As in this moment not so many choice, havoc looked the most near to my wishes, in fact very nice after these hours, I guess I'll be fine with it when the bugs will disappear.
Anyway 1-7 was always without problem. Today after 2 unbrick and bl opening what I did is, through fastboot I entered to the img, from there I flashed the zip, reboot recovery to make sure it stays. I put files on the phone, wiped dalvik and data, install rom+twrp and as it is written here and also on that thread, I rebooted recovery. And I wanted to repeat the flash, but I had the internal storage 0mb thing. So I needed to format data (that's the solition I found) and reboot again, put back files, flash, reboot, flash again, and after I got that qualcomm crashdump screen. I hold the up+power to get back to twrp (or down, not sure) and I flashed again, but only once, so after it worked finally. Since that I'm fine
But sure I need to learn this stuff, it cannot be that I always face st that nobody else does
I hope the managed soon the ota for custom roms and we can do it easy and quick without setting the phone over and over again with all the apps, settings.. (probably only me in the world need to do so, as I start to loose it with the tech staff)
Poor phone is just couple of weeks old, but already saw everything
Thanks for writing
If it means anything to you, I use stock OOS+TWRP+Magisk+Renovate ICE+Xposed (to ignore the secure flag, otherwise Netflix doesn't work over HDMI). Everything works, including Google Pay.