My phone:
- was Jelly Bean.
- upgraded normally to KitKat
- some time passed and it crashed.
- installed RSD Lite
- unlocked my bootloader
- flashed Jelly Bean stock firmware
- back to life
- one month later crashed again
- flashed the same ROM without erasing anything
- back to life
- two months later crashed again
- flashed the same ROM
- back to life for ONE DAY then CRASHED AGAIN GODDAMMIT
- flashed the ROM - only now it can't complete the boot at the end and ASKS ME TO MANUALLY BOOT IT. That was the problem I was trying to fix, RSD. I can't manually boot it.
- tried a different stock firmware, still doesn't work
Should I try erasing user data? Or a different ROM/MOD? Help... =(
Did you try the XT907 fastboot files for 4.4.2? That might work, if you edit the xml file and remove all but the "security signed" line...
Related
Hello,
I unlocked bootloader and flash ROM from this thread:
http://forum.xda-developers.com/showthread.php?t=1936512
I used Retail Europe (91.2.26001.Retail.en.EU - 4.1.2).
I would like back to stock, because I have phone only for test (I must "hunt it" on ebay)
The problem is that I encrypt the phone...
When I try to factory reset by phone menu, there is no results.
I've already seen that on my Galaxy Nexus. In this case relock bootloader solved the problem.
Unfortunatelly, fastboot oem lock doesn't work (Error: Please run fastboot oem lock begin first).
Bootloader isn't problem, the most important thing is stock ROM. I downloaded from sbf.droid-developers.org:
CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml.zip
But... what can I do? CWM can't mount encrypted storage.
EDIT:
I tried and it's works
I extract archive (CFC), there are many files like boot_signed, system_signed etc.
Then, I go fastboot and flash:
- system (it's about ~800 MB but flashing without problem)
- boot
- recovery
- logo
- ulogo
- gpt
- cdrom
Reboot... no results. I tried to do factory reset and... it's working
I have decrypted phone with stock ROM.
Now, I must only lock bootloader.
I'm trying to install an OTA update to get to the newest version of android for my (Rogers) ONE M7.
I had:
- Unlocked the bootloader
- Flashed a custom recovery
- Flashed a custom kernel
- Installed Supersu and rooted phone
- BUT KEPT STOCK ROM
Phone worked wonderfully with no problems but slowly became dated (4.4.2)
My phone still received OTA's, after ignoring them for a while I would like to move to the newest available (5.1) for all the upgrades like ART.
I then:
- Flashed stock recovery (successfully)
- Flashed stock kernel (successfully)
- Relocked bootloader (successfully)
- But this is where the weirdness starts. I can't unroot, and thus the OTA fails.
I have tried:
- Full unroot using supersu
- Disabling super user
- Uninstall Supersu
- Deleting all .su, su, supersu.apk, busybox (which I suppose supersu installed?) and all other associated files using file explorer.
- Using apps like Universal Unroot.
The best I can do is temporarily remove root by using supersu full unroot, BUT UPON RESTART THE PHONE REINSTALLS SUPERSU AND ROOTS ITSELF. This has me completely stumped.
I then tried installing a ruu to wipe the root off my phone but the ruu always crashes at 5%... with windows telling me "htc_fastboot.exe stopped working".
I tired extracting the ruu and flashing it using fastboot but in that case the cmd window fails with "invalid sparse file format at header magi"
And yes, the MID, CID and carrier match up exactly for my phone and the ruu.
The only option I have left is to redo everything so I can flash an (updated) custom rom on my phone. But I want to stay on stock rom so I don't lose all my files. Which I wouldn't with an OTA, or when using HTC's awesome backup feature (which I'll lose with a custom rom). (As well as holding its resale value!)
Thanks for reading, if anyone know's how to get around this seemingly impossible problem please let me know!!
123ethan said:
I'm trying to install an OTA update to get to the newest version of android for my (Rogers) ONE M7.
I had:
- Unlocked the bootloader
- Flashed a custom recovery
- Flashed a custom kernel
- Installed Supersu and rooted phone
- BUT KEPT STOCK ROM
Phone worked wonderfully with no problems but slowly became dated (4.4.2)
My phone still received OTA's, after ignoring them for a while I would like to move to the newest available (5.1) for all the upgrades like ART.
I then:
- Flashed stock recovery (successfully)
- Flashed stock kernel (successfully)
- Relocked bootloader (successfully)
- But this is where the weirdness starts. I can't unroot, and thus the OTA fails.
I have tried:
- Full unroot using supersu
- Disabling super user
- Uninstall Supersu
- Deleting all .su, su, supersu.apk, busybox (which I suppose supersu installed?) and all other associated files using file explorer.
- Using apps like Universal Unroot.
The best I can do is temporarily remove root by using supersu full unroot, BUT UPON RESTART THE PHONE REINSTALLS SUPERSU AND ROOTS ITSELF. This has me completely stumped.
I then tried installing a ruu to wipe the root off my phone but the ruu always crashes at 5%... with windows telling me "htc_fastboot.exe stopped working".
I tired extracting the ruu and flashing it using fastboot but in that case the cmd window fails with "invalid sparse file format at header magi"
And yes, the MID, CID and carrier match up exactly for my phone and the ruu.
The only option I have left is to redo everything so I can flash an (updated) custom rom on my phone. But I want to stay on stock rom so I don't lose all my files. Which I wouldn't with an OTA, or when using HTC's awesome backup feature (which I'll lose with a custom rom). (As well as holding its resale value!)
Thanks for reading, if anyone know's how to get around this seemingly impossible problem please let me know!!
Click to expand...
Click to collapse
When your have problems flashing a RUU, just flash the Same version Firmware first then the RUU
also your PC needs all the C++ installed (2005 - 2008 - 2010 both x64 and x32 bit versions)
Hello!
I was trying to apply the Stagefright OTA on my XT1058, but I soft bricked it. Whenever a new update comes out, I prefer to flash stock image to avoid any unecessary issues that may arise from dirty flashing and not having the system requirements to apply the update without having problems. So that's what I did:
- I flashed the 5.1 stock image for my carrier (Vivo) using RSD and it worked fine, phone booted normally and etc.;
- I skipped the Google account setup and got the Stagefright OTA notification. Since I had already downloaded it before, I wanted to test it by sideloading it from Recovery. So I did it, I entered recovery mode and sideloaded the OTA. All went fine, no errors in the log. Rebooted phone. New bootanimation. Apps optimized;
- But I was getting 'gapps process has stopped' error and couldn't log into my Google Account, so I decided to reflash the stock image (I guess this was my error) using RSD;
- gpt partition flash fails;
- Phone stops booting, it just gets to the recovery menu or to the 'No command' screen;
- I tried flashing everything manually, doesn't work;
- I tried flashing gpt.bin from a Brazilian Retail firmware. It flashes without errors, but phone doesn't boot either;
Is there a way to recover from that? I have a TWRP backup from before I started all this process, but it looks like I can't restore it because my PC doesn't seem to recognize the sdcard when mounted.
Thanks in advance!
EDIT: managed to restore it using the steps from option 5 in Mark Venture's guide here. It was the only one that worked. BUT I had to flash gpt.bin and fsg.mbn from the OTA zip. Only then the phone booted. Then I took OTA normally and it installed without any hassle. So it looks like hash mismatches do not happen in this version of the firmware.
Hi,
Problem:
I don't know the cause. I was casually reading an article in Firefox then the phone suddenly freezes for a few seconds. After that, the phone is now on bootloop.
Phone's status before the problem:
rom - stock (from V12.0.1.0.QFKEUXM to V12.0.2.0.QFKEUXM via MIUI updates)
bootloader - locked
twrp - not installed
root - none
The things I tried to fix the problem were:
- Factory reset
- Flash a recovery rom (V12.0.2.0.QFKEUXM) via Mi Phone Assistant v4.2
Flash was a success, with no problems during the flash phase. But the bootloop was still there.
- Flash a fastboot rom (V12.0.2.0.QFKEUXM) via MiFlash (Xiaomi_Flash_20170425.zip)
Flash was a success, with no problems during the flash phase. Still, the bootloop was evident.
- Flash a PixelExperience rom via TWRP (twrp-3.4.0-0-raphael-mauronofrio)
Flash was a success, with no problems during the flash phase. I saw the Google Logo after the "adb reboot" command but the bootloop was still apparent.
- I tried "XiaoMiTool V2 project" as well that installed V12.0.3.0.QFKEUXM with no problems during the flash phase. But the bootloop was still there.
- Manually flashing a persist.img via TWRP or Fastboot. Bootloop was still there.
The things I have not tried were:
- Wiping all the partitions (https://forum.xda-developers.com/showpost.php?p=83713173&postcount=8). The instructions were a bit vague I'm afraid to try it without the full context of the fastboot commands.
I'm at a loss. Based on my research, the recovery rom should have fixed the problem, but it didn't, so I don't know what the cause of the bootloop problem is.
I hope the community could help me.
=== UPDATE ===
I managed to fix the issue by using this method -> https://forum.xda-developers.com/k20-pro/development/rom-lineageos-17-0-t3976469
I strictly followed the steps under the instruction part and, viola! The phone manages to reach the setup screen of Lineage OS.
I hope this helps!
Thanks,
Temberness
Greetings,
in a last month or so, im trying to revive this tablet, mostly because of the dual boot posibilities, but that can be done only with lollipop uefi bios.
My device is currently running 4.4 .201 OTA and im unable to update to 5.0 with whatever step i do.
First of all, i hard bricked my first device of this model myself completely, so i decided to replace my motherboard, somehow i lost the side buttons aswell, so i did order a "non-working" device from e-bay. I made it working by just flashing the .182 firmware.
I wasnt able to apply OTAs to the device, always got Status 7 Error in recovery, i did fix that by using a modified update script that i had to apply to every single OTA i flashed.
Finally got to 201, now its time to go to Lollipop.
I tried
- flashing LP firmware through temporary recovery (CWM/TWRP)
- flashing every single firmware thats available - .17; .24; .33; .36 - every single one with the KK "prefix"
- flashing every single firmware with the official firmware update method aswell (putting the update file to root of internal/sd memory and applying it within the tablets system
- flashing the official OTA updates that arrived as dlpkgfile
- flashing the firmware with the command file (putting renamed firmware to update.zip, to /data/ + command file to /cache/recovery/
- flashing service firmware with Intel Phone Flash Tool (KK/LP)
- reseting data/factory reset before and after the update, with cache included
- restoring both backups of KK/LP
- flashing boot.img extracted from the ROM after applying the update
Maybe im missing something, but in every single case, the update went through (some maybe had error in TWRP, but were fine in CWM/stock), but the system doesnt upgrade itself.
The update completes, then after a system reboot the device just goes to the ASUS logo (first one), gets stuck for roughly 30 seconds and bootloops. The droidboot/bootloader is not changing after update.
Any ideas on how to proceed now? I believe i tried every single method of updating, could not suceed unfortunately.
Thanks!
FIXED
The original system update process (putting update file in the root of sdcard,blablabla) always ended up on like 70% and rebooted, with no bootloader upgrade.
So the system didnt boot up, had to revert back to kitkat.
I found OTA Verifier app, that verifies the update script and selects the error in it.
I saw, its saying my device model number is K013_1, but thats not true! For some reason i had 2 build.props in my system files, so i rooted, deleted build.prop_K013_1 (or some name like this) and kept the original one.
! The update itself didnt give any kind of error, it went through without saying anything, thats why i didnt think the updater script would be the problem!
I believe, just deleting the first 2 lines in the update script would help aswell.
After that, i applied the update and waited for it to finish, at 70% once again it rebooted, but this time it started upgrading the bootloader. Lollipop installation finished and im finally at 5.0