Hi. I've flashed these two roms https://firmwarefile.com/nokia-4-2-ta-1157 by editing rawprogram0.xml. But after booting it shows Your Device is corrupt. May or may not work etc...
If I choose continue, then it just hangs on Android One logo and nothing happens. I put it there for a long long time. Tried factory reset from recovery, flashing the zip update from fastboot but still nothing happens. These are the only two roms I've found for free. Anyone can help my to bring my phone back?
Related
Hey guys, I'm having trouble with my nexus device, I was watching youtube on it and it froze and now doesnt boot. I can access hboot, but recovery just shows the X logo and restart. I've tried reflashing boot.img, reflashing the recovery, reflashed stock hboot, flashed new roms from fastboot. I've also tried passimg.zip, and flashing a different radio but it stops 90% the way through, and it gets stuck in loading passdiag.zip if I use the volume down button to boot instead of the trackpad button.
The graphic abnormality is like an artifacting. If you search youtube its called "Nexus one stuck on X, can't boot to recovery.", I cant however post a link.
Anyone encountered this before? Any insight is appreciated.
well I've managed to remove blackrose at least, and to get to the blackrose menu. You have to access it from command prompt with "blackrose.exe skip" while in fastboot. Though I'd put it here incase it helps someone else in a similar circumstance.
So I bought a HTC One Mini M7 recently (maybe a month back or so). I loved it, and I decided to root it, but I didn't know what custom ROMs were. So I decided to try getting one, and failed many times because it said failed. I had TWRP, so when I tried to flash the zip, and when it failed, it said clear cache/davlik or whatever, and I clicked it. Ever since, I've been stuck in a boot loop, and whenever I tried to press recovery, or factory reset, it would say Entering Recovery... at the top, and then the teamwin logo part would flash for a split second and keep flashing for like 3 seconds, and the bootloop would start all over again.
I tried to fastboot erase cache, I even fastboot oem lock 'd, but now it's relocked and whenever I try to enter recovery or factory reset, it just puts me back into the bootloop/bootloader. I really need help on this please.
I've also flashed a new recovery when my bootloader was unlocked, and that didn't work either. Please help, thanks!
HTC One Mini is M4 - http://forum.xda-developers.com/htc-one-mini
Hi guys, I'll try to explain my problem:
My Milestone has been running the rom "cm-7.2.4e-umts_sholes" since two years without issues... until a few days ago: aleatory restarts and freezes. Yesterday, I turned it on and was stuck on "M" logo. Several restarts later, it shows the "2ndBoot - Kernel Restart in progress" logo and nothing else.
I tried to reflash the rom and encountered some issues:
Bootloader 90.73, I flashed the vulnerable recovery "vulnerable_recovery_only_RAMDLD90_78.sbf" and enter in recovery stock. When I tried to run the "OpenRecovery_2ndbootOR_v1_2" the OR doesn't start at all. Black screen, restarts and recovery stock again. Only the "OpenRecovery_v1_46_SHOLS_inkl_ext_mmcfix_parted_update" does the trick and starts the OR with red letters. After all the obligatory wipes, applied update from "cm-7.2.4e-umts_sholes" and then reboot system. And the same "M" stuck or "2ndboot" stuck screen. I tried wipes again, but no results.
So, I tried to go back to an earlier version and installed "SHLA_U2_02.02.0_USASHLSPERARLA017.0R_USASHLSPERARLAT_P037_A015_HWp2a_1FF" with RDSLite. It boots up Android BUT the touchscreen not works at all, even with several reboots. Tried to reflash Cyanogenmod from here, but the same issues above listed appears.
I really going crazy with this... Did I make some mistake at any point? Must I reflash the bootloader 90.73 if I found it? (besides all the webs containing all the .sbf's and bootloaders appears to be offline by now).
Any solution/advice you can give me please?
Thanks in advance and sorry my english, isn't my first language.
my mini s3 was with lolipop rom downloaded from maclaw.pl and i factory reset it
and when it restarted the teamwin logo appears an goes
again appears and goes
please help me
Same here. Same software, same procedure, same problem
Even same day! :/
EDIT: Tried to upload TWRP again, worked so far, but I still have the same error
Same Here Dude
Yeah I am too waiting for solution.When the admins or experts will reply this..
So tried of trying every solutions
i too tried clock work recovery but the screen goes blank after samsung booot logo appears after flashing cmw
i think there is bug in lolipop version
and i am regreting why i have factory reset :'(
Here is the solution.
Go to http://www.android-hilfe.de/thema/q...-zu-samsungs-gesamt-software-firmware.518903/
Choose a way to download your Stock-Rom. Then go to http://novafusion.pl/tutorials/installation-guide-golden/
Follow the instructions but use the stock-rom, not the custom rom. Reboot into downloadmode again.
Repeat but now install the custom rom. When you start it now, it will stuck at the system loading screen. But dont worry... restart into recovery mode (Vol+ + Home + Power) and go to Wipe, factory reset.
Restart and be happy.
EDIT: I could also reproduce the bug... It really happens when you use factory reset in cm.... So.. just dont use it. Start it for a factory reset manually into twrp and make there the factory reset.
Here's the deal, I have a sprout8 device (the Indonesian Nexian Journey One) running stock 6.0 with some xposed mods installed on it. Suddenly the device shuts down and when I try to boot it up it only goes halfway through the bootanimation when it shuts down again. I wasn't too worried as I thought it was just a conflicting system issue and I also thought it was time to re-flash fresh stock 6.0 to freshen up my phone anyway. So I went ahead and did it.
Here's where the problems start to show up, I had a hard time booting to recovery through the power + volume up combination. The phone suddenly shuts down on its own as it boots up. I tried it a few times and finally got to recovery. After that, as I flashed stock 6.0 the phone shut down again. I thought it was an issue with my recovery so I tried wiping everything through fastboot and re-flashed recovery through fastboot aswell. From there I tried again to flash stock 6.0 through recovery and again, the phone shut down. I tried a different ROM thinking it was a ROM issue but still got the same results.
After hours of trying to flash a ROM through recovery (retrying over and over as it suddenly shut down while flashing), I finally got a ROM installed. Then I rebooted my phone, but again it freezes halfway through the bootanimation (literally freezing the bootanimation) and refused to do anything. I took off the battery and booted up the phone countless tries trying to get it to boot up. When it finally booted up, I filled in all the Google startup credentials and finally got started on a fresh stock 6.0. However, I tried to restore my previous application data through Android's application recovery on startup but everytime the device installs a new application it would freeze up and shut down. This happened countless times. Then the phone, once again, shut down and could not start the ROM. It would freeze up on the bootanimation.
Then things started to get weird, when the phone turns on it should show the "Nexian" logo in all its glory before going to bootanimation. But here the screen gets all distorted and shows these weird horizontal (and sometimes vertical) lines. Nothing's wrong with my phone screen so I assume it is a system error. From here on, the phone refused to boot. It just shows the Nexian logo and restarts over and over. The same thing happens even after I re-flashed both my recovery and ROM. I even tried using SP Flash Tool to re-flash stock but still the same results.
Now, the device wouldn't even turn on. But when I connect it using USB to a Windows computer, it still gets detected through device manager as an ordinary MediaTek device.
I'm assuming now that it may be a problem with the /system parition where we install our ROMs in. The partition may be (partially) corrupt. Seeing as the device could still boot the ROM a few hours ago but freezing upon updates to the stated partition.
If you guys have any other ideas/solutions I'm all ears.