I flashed a Custom ROM with bootstrap recovery and not boot (boot loop), and flashed in fastboot this ROM: InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml (Stock ICS ATT&T) and work perfect, I try again other ROM and have similar result, and flashed again the ROM stock ICS and now no have radio.
I have unknown baseband, no imei and random reboots
I try flash only the radio, other radio (int ver, GB) but I no have any result.
in all occasions with fastboot, all part mark "okay" and writing "okay", in flash radio only and flash all ROM Stock (flashed with moto fastboot, fastboot other version, rds lite 5, 6.1.5)
ROM info:
4.0.4 build number 6.7.2-226-EDICS-10 date Aug 31, with this rom I do not want to try to downgrade to GB, hard brick possibility
With boot mananger, have a option to flash firmware files in recovery boot (radio.img, system.img), but have error (Status 7)
In fastboot, try "moto-fastboot erase radio": no such partition
During boot, I see a blue screen, after the boot image logo Motorola dual core technology
Inreparable radio?
Related
Not sure what happened but I can't flash any custom ROM. This is what I did so I can start flash. I "fastboot OEM lock" then run RUU (RUU_Ville_U_TMOUS_1.53.531.16_Radio_0.16.31501S.02_10.1..._262073_signed.exe). Everything went good. After that I did a factory reset and erase phone thought Setting. This should be fresh.
Now I unlock bootloader. I did not request a new Unlock_code.bin. I just use the old one i had. Unlock when good. Now I flash "fastboot flash recovery recovery-clockwork-5.8.3.1-ville.img", success. I reboot and when into recovery then flash "SuperSU v0.96", success and i do see SuperSU on the phone. Finally I install Goomanager. GooManager installed "openrecovery-twrp-2.3.0.0-ville.img", success.
Now I install custom ROM. I open the custom ROM and drag "boot.img" so i can flash it first before flashing the ROM.
did a "fastboot flash boot boot.img" success. Then when into TWRP v2.3.0.0, and did a wipe cache, wipe devlik, and factory reset, finally flash the ROM. It flash only like less than 5% and then the phone just reboot, Now I'm stuck at HTC Logo w/red letter below..
Could the ROM not compatible w/TWRP v2.3.0.0. This are the ROM i tried, Unofficial AOKP JellyBean Build 4.1 [10/8/12] and Venom ROM, all said ROM flash success and stop at about 5% of flashing, then it reboot and stuck at HTC Logo
Please help.
PS. if I lock BL and run RUU it's working but after unlock BL, root and all success, i cannot flash any rom as stated above.
My BHoot 1.09
cat2115 said:
Not sure what happened but I can't flash any custom ROM. This is what I did so I can start flash. I "fastboot OEM lock" then run RUU (RUU_Ville_U_TMOUS_1.53.531.16_Radio_0.16.31501S.02_10.1..._262073_signed.exe). Everything went good. After that I did a factory reset and erase phone thought Setting. This should be fresh.
Now I unlock bootloader. I did not request a new Unlock_code.bin. I just use the old one i had. Unlock when good. Now I flash "fastboot flash recovery recovery-clockwork-5.8.3.1-ville.img", success. I reboot and when into recovery then flash "SuperSU v0.96", success and i do see SuperSU on the phone. Finally I install Goomanager. GooManager installed "openrecovery-twrp-2.3.0.0-ville.img", success.
Now I install custom ROM. I open the custom ROM and drag "boot.img" so i can flash it first before flashing the ROM.
did a "fastboot flash boot boot.img" success. Then when into TWRP v2.3.0.0, and did a wipe cache, wipe devlik, and factory reset, finally flash the ROM. It flash only like less than 5% and then the phone just reboot, Now I'm stuck at HTC Logo w/red letter below..
Could the ROM not compatible w/TWRP v2.3.0.0. This are the ROM i tried, Unofficial AOKP JellyBean Build 4.1 [10/8/12] and Venom ROM, all said ROM flash success and stop at about 5% of flashing, then it reboot and stuck at HTC Logo
Please help.
PS. if I lock BL and run RUU it's working but after unlock BL, root and all success, i cannot flash any rom as stated above.
My BHoot 1.09
Click to expand...
Click to collapse
Everything looked like you did it right. I never new TWRP had a 2.3 version so I looked it up and found this.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may not longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated.
Click to expand...
Click to collapse
It might not be related but since you seem to be doing it write I would go back to TWRP 2.2.2.0 and try to flash a rom there. I'll test it out myself this morning.
Yes the Roms you are using are not compatible with twrp that you are using.I went through this sane exact thing last night.in the thread here they say there is aNew updater binary needed in roms to be ABLE to flash.they provide one but when I put it in my roms they still didn't flash. Boot into bootloader and adb flash cwmr or the previous version of twrp.
Hey guys, thanks for all the previous help i've gotten from here.
Here's the deal, I have a 2.2, rooted and unlocked ATT HOXL. I flashed the SU binary and have root and everything. I'm on the stock 2.2 ROM.
Do you need to install a different ROM before flashing the kernel? If so, then I will wait until this download finished for CleanROM. If not, then continue below..
I flashed the boot.img for ElementalX-3.1 in Fastboot (Fastboot 1.14), rebooted phone like normal, phone came up, kernel is showing in the information page on the phone, it is running at 1.7ghz. That's fine, but then I realized I had never gotten any installer or anything. So, I went into recovery to flash the whole ZIP file. Go to reboot the phone and it hangs on boot after the first HTC logo.
I tried flashing the boot.img, then rebooting to recovery, and flashing the ZIP, then clearing the cache, and then rebooting. Still hangs. I am able to go into recovery and restore a backup if I need to, so at least my phone isn't dead, but I want to do this.
I also tried installing the ZIP, then rebooting into Fastboot and flashing the img, and then booting the phone up normal.
So as it sits now, I have the Kernel installed from ONLY the boot.img, I did not run the ZIP.
Do I need to flash a stock kernel in Fastboot, and then try just flashing the whole thing in TWRP? From what I have read, the steps for flashing the kernel on 1.14 is:
1. Flash boot.img
2. Reboot to recovery
3. Flash ZIP
4. Clear cache
5. Reboot phone as normal
Are those the correct steps? Do I need to flash a stock kernel before trying this again, or can I just start from square one, as if I were using a stock kernel?
Thanks
You can't flash kernels from recovery on the higher hboot. You have to fastboot them or use the flash image GUI app.
Some ROMs/kernels use a script that works around that, but not all do.
Hi all. I own a Moto G xt1032 UK version. (GSM right?)
I was on 4.4.4 Epsilon ROM but I wanted to flash stock 4.4.4, so I used a tutorial I found on youtube that set me up to stock 4.4.2, then I upgraded to 4.4.4 and THEN there was another update to 5.0.1. So as you can guess, I upgraded to lollipop and that was it - bootloop. I have tried flashing other roms through fastboot and nothing worked, I get an error when I flash ''system'' that says ''image is too large'' once all is done, phone restarts and its stuck on bootloop once again. The bootlogo changes when I flash different rom etc. But I don't know what to do, any ideas? :/ I have also tried to flash a custom recovery and sideload the Epsilon ROM but I only get an error in my command line that says no device connected after I hit the command. Any suggestions guys? I appreciate any sort of help, thanks guys.
I'll also add that I think I have the 41.18 bootloader if it helps (it says so in the bootloader settings)
When flashing a ROM in fastboot, are you also flashing the gpt file?
Yeah. I flash everything there's to flash as all tutorials instruct.
To try and get your phone up and running, flash a custom recovery from fastboot. Once the recovery image has been flashed, use the phone's volume buttons to boot into recovery. If you can get into recovery, try and flash a custom ROM.
Ah, I forgot to add. When I attempt to flash anything from my storage it says some sort of error coun't mount /sdcard and others when the recovery opens up. I tried flashing other recoveries, TWRP, CWM both show the exact same errors..Can't mount SDcard etc. :/ That is why I tried the sideload method which didn't work for me either.
You're flashing recovery for the falcon?
Yes..for falcon. I've done it a bunch of times before, however I never had the unable to mount error in the recovery..
I don't have my moto g on me but I found Philz Touch (based on CWM) worked besr for me after i switched back from GPE to CM12. I was getting weird error messages in TWRP.
Hello,
I was running the LMY48B-radio, then was flashing the KTU84Q-Radio because I've read that the GPS performs better, the .zip file had no .img file to flash, so I went ahead & just flashed the KTU84Q radio via recovery, now I'm experiencing very weak GPS signal and no lock.
I've tried to re-flash the LMY48B radio, didn't fix it.. I think I've maybe done something wrong, so I'm gonna write down the steps of how I flashed it:
1) Bootloader mode
2) flash radio.img via fastboot
3) reboot bootloader
4) boot into recovery
5) flash radio.zip
6) reboot
Is there anything I've forgot? Or didn't do properly?
I'm running Cataclysm ROM/LP 5.1.1 (Stable release, 20th June 2015) and ElementalX kernel.
My device is hiaeuhl, S-ON and UNLOCKED. Flashing 1.27.709.15 works fine, but cannot OTA to newer 1.58.
So I try to flash 1.58.709.1, but it just reboot endlessly, never get into home screen.
The steps are: (1) erase system, boot and recovery (2) flash boot, recovery and system images (3) wipe data/cache
The ROM image files should be OK because it works on another A9.
I also tried flashing 6.0 and install CM13. Can boot but SIM card is not detected.
Thanks for any suggestions!!
have you tried to install OTA with custom Recovery (TWRP)?
Flash RUU 1.27.709.15 and take then the OTA to 1.58.709.1