Ohh man, i was seriously disappointed in this release. All was good til let CM Updater automatically update the firmware, then all of a sudden my SD card was corrupt.
But wait, i go to "Update from any zip" And my previous installs are there.
4.9.* is corrupt, so i do a nandroid backup and b00m theres HERO... OMFG
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
First, this belongs in Q&A and as such has been reported.
But, to be helpful, you can manually flash the system.img and data.img from your backups to make sure that it restores the correct backup via fastboot
If you copy the files to your computer (system.img, data.img, and boot.img) to where-ever you have fastboot then you can run the commands in the bootloader:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata data.img
and this should be the same as a NANDROID/switchrom restore.
couple of thing - wrong section
the 4.2.x are stored in /sdcard/cmupdater/ or thereabouts and its unlikely they are all corrupt
its your own fault for not doing a nandroid of a CM (you may have an old one in there if you went to hero after cm and then back again)
if not, start again with 1.6 then CM
CM doesnt screw your sd, improper use does
I am seriously disappointed with your post.
why-o-why do we let people with less than 50 posts create threads anywhere but the QnA?
ZALGO - that was wrecking-crew-esque....let me shake your hand
i miss those guys....
ohh stfu -- all you, i have been flashing PC bios for years, but i "update" my phone with and automatic update, and you jump on my back. and where so you think i got my information to flash my phone. "YES" xda.. so swallow it up.. Question is there a thread for the new Cyanogen 4.12.2 release, if so point me to it. THANKS!!!
fukin look for it you lazy buggar
its staring you in the face...infact it was 2 under your thread when you first posted
and so what if you flash pc bios(s) all the time, this is even easier, you dont even need to push a button until its finished
I'm new with like no post an I can tell your a tool. Do a little search douch nozzle. I am a noob and I agree garok89, no new threads for noobs outside of Q+A before they can show there not tools like this douch who started the tread
cm updater could do with the option to do a Bart / Switchrom / Nandroid backup though.
I have clicked apply now many times and forgotten to manually reboot and do a backup first.
If it fails I just curse myself, but it would be a nice feature.
the cmupdater can easily have the feature to autonandroid - we have the code for it
only problem is, none of the recovery images support it
the second its supported in cyanogens recovery image (and therefore RAs recovery image as it is based on cyanogens) we will enable the feature
reading is the best way to avoid these types of problems.
but lets face it, this is total....
Related
I can't boot to CM Recovery 1.4.
But I can boot to the SPL (Three Skateboards with white Screen)
I have a white G1 specs are:
* 8GB ADATA SD Class 6
* Partioned at: 2GB EXT 2 32MB Swap Rest FAT32
* I am updated on the newest radio and the SPL.
* I am running Cyan 4.0.4
The Scenario:
I was playing COD5 on PS3. I went to Ifap.to on phone while it was on Wifi. So then I was trying to skip through the video and the phone obviously froze up and then it shut off and reboot itself. It never got past the T-Mobile G1 screen.
Then I tried to go to recovery by holding home + power and it doesn't work. So I held down power + camera and it goes to the three skateboards so I know I'm not bricked(not yet) What can be the issue and what would I have to do to fix this.
Please email me or post here whichever is convenient to you.
Thanks,
I WILL DONATE BEER MONEY TO 1ST PERSON WHO HELPS FIX MY DAMN PHONE!!
set up fastboot and fastboot flash one of your nandroids.
http://www.4shared.com/file/136452986/f9d297d5/nandroid-cm41111
if you don't have one (for some unknown reason) here is one i uploaded a while back to help some one who couldn't get their touch screen to work.
http://forum.xda-developers.com/showthread.php?t=532719
there is good thread to get fastboot/adb set up.
to restore you nandroid via fastboot
Code:
fastboot flash system system.img
fastboot flash userdata data.img
fastboot flash boot boot.img
fastboot reboot
those 3 images are the only ones you will need to restore via fastboot.
i suggest putting them in the folder that has fastboot.exe in it, and cd to that folder.
also since you say you have the new spl, i assume you mean 1.33.2005, then you will need the updated drivers found here (http://sapphire-port-dream.googlecode.com/files/usb_driver_updated.zip)
if you can't get all this set up then i suggest trying to apply the DREAIMG.nbh file in bootloader (screen with the androids)
you can get the DREAIMG.nbh file here (http://forum.xda-developers.com/showthread.php?t=563679). also you can use that guide as a resource to re-root your phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Beer Monet
bansawbanchee
The Scenario:
I went to Ifap.to on phone while it was on Wifi. So then I was trying to skip through the video and the phone obviously froze up and then it shut off and reboot itself.
Click to expand...
Click to collapse
Same thing happened to me but I was lucky enough to get into recovery and do a nandroid...givin I had to re-root and reinstall everything.
STAY AWAY FROM IFAP.TO!!!
I have nothing but bootloader. No system. No recovery. I've attached a screenshot. Do I have any hope?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You should be fine, because your device is unlocked. The only way you likely would have screwed yourself is if the OEM Unlocking toggle in Developer Options within Android was turned off.
EDIT: Using Fastboot you should be able to flash TWRP, which will give you your recovery. From there, flash a ROM and you should be good.
spastico said:
I have nothing but bootloader. No system. No recovery. I've attached a screenshot. Do I have any hope?
Click to expand...
Click to collapse
Go here DL the latest shamu factory image and follow the instructions. It will delete everything though.
Thanks guys. I'll let you know how it goes.
I'll be using a Mac.
Still struggling, but made a little progress.
I'm using a mac with terminal.
I don't know the terminal commands, but searching around the forums By doing this: ./fastboot boot twrp.img I now have twrp recovery working. But I still can't figure out how to flash.
Browsing around my nexus using twrp, it looks like I have no system partition.
Any more advice?
Woohoo!
Reading these forums, I figured out how to sideload the rom using ./adp with twrp sideload adb.
Back up and running.
All of this started while I was trying to switch from SuperSU to Magisk.
I still want to move to Magisk, but I obviously need to do some more reading.
For some reason I couldn't get the factory images to sideload. It kept saying invalid zip. So I sideloaded PureNexus.
All is good, but I just don't have a radio.
Off to do more reading.
Got a radio and posting from my Nexus.
Thanks again guys.
./fastboot flash radio radio.img
Great read, seeing the progress reported on like that. Thanks for updating.
If you ever want to move to the stock factory image, you don't sideload it. You'll need to run the flash-all.bat file (edit it and remove the -w flag to keep your data) or unpack it and use fastboot to flash each separate image (skip userdata and if you want to have TWRP installed to your device also recovery).
And if you have further issues with getting Magisk running, check out the Magisk guide.
@spastico @Didgeridoohan
To sideload a stock image on an N6, you have to use a full OTA image as compared to using fastboot flash (or the flashall.bat) with a Google factory image.
The instructions for each are well written right on the linked page from google.
@spastico, you commented that with TWRP booted, you didn't see a system partition. System is not mounted in TWRP, but you can manually mount it if you choose. As you discovered, mounting isn't necessary to flash an image.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Awesome! I keep forgetting about those full OTAs. They weren't around when I used stock factory images on my Nexus...
Thanks for the additional advice.
I am not responsible for people bricking their devices because they haven't made a backup.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Downloads
TWRP For P10 lite: HERE
ADB & Fastboot: HERE
The first step is to make a backup.
2. Download your Treble ROM, i recommend a GSI ROM.
In my case I'll be using Havoc-OS
Download: https://forum.xda-developers.com/project-treble/trebleenabled-device-development/rom-havoc-os-8-1-t3819050
3. Go into TWRP and do a FACTORY RESET and then reboot into fastboot.
4. The only thing you need to do now is flash the ROM, so get your downloaded ROM & extract the .img file from it (if there is no .img file and you see other files, flash via twrp).
On your PC open the fastboot command prompt and type
fastboot -u flash system <YourImageFileHere>
Click to expand...
Click to collapse
After just type : "fastboot reboot" and wait until your phone boots into the system. You may need to flash google apps afterwards.
It is normal for the phone to reboot a couple times so be patient.
Congratz, your phone is not running a treble ROM with your stock ROM's vendor.
Click to expand...
Click to collapse
Video:
I just need backup Boot, System and data if i want go back to stock?
Bad idea to factory reset with TWRP, it doesn't do it clean enough.
You could get in serious problems by doing it, such as random apps crashing, sd unmounting and worse.
Safer option is to factory reset and wipe cache with stock recovery after every system flash.
I'm telling this from my own experience, I don't want people to mess up like I did :highfive:
Ret-Zero said:
I just need backup Boot, System and data if i want go back to stock?
Click to expand...
Click to collapse
Yes that should be enough, vendor stays the same anyway.. I recommend flashing roms designed for kirins cpus btw because there is a higher chance it will work
Hi,
There is this bug on LOS16 that if the pop up camera is up and then the device switches off, the camera stays up permanently until a stock rom is reflashed. I had this issue before, so I restored a backup I made on MIUI 10.3.16 using TWRP, but the device was stuck in a bootloop, and the camera was still stuck, so after restoring different backups I made, I decided to finally use MiFlash to fastboot flash MIUI 10.3.16, and I chose the 'keep user data' option, however this also bootlooped and went into MIUI recovery. I reflashed TWRP and now I face this issue:
TWRP does not recognise that my phone is encrypted, and does not ask for my password, so I can see that my files are here, but they have random folder and file names. (example shown below)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I managed to get MIUI running, however it does not ask me for my password, only my Mi account password.
I restored a LOS16 backup I made ages ago, and that also does not ask me for my password - the files I see in the file manager are all encrypted like TWRP.
I attempted the 'twrp decrypt' command, but that does not work either.
I attempted flashing backups and custom roms from a USB, using PitchBlack recovery, OrangeFox, and two TWRP versions.
All I want is for either a recovery or a rom to ask for my unlock password, so it can use that to decrypt my files.
I am not 100% sure if using MiFlash is what caused this, but is there anything else I could try? Are all my files gone? I cannot copy my encrypted files over to my PC and Windows returns an error when trying to do so. Are there any 3rd party tools I can use to decrypt my stuff?
I know I could just wipe my storage and start again, but I do not really want to do that until I know for sure that my files are gone.
I was thinking that MiFlash wiped the decryption keys from my device, but wouldn't a backup restore them?
If it is not possible to save my files, could someone explain why, so I do not make the same mistake again?
Any help would be appreciated.
Format Data, you cant go from miui to aosp or vice versa without doing that. backup your data to pc before or whatever cuz it wipes all internal.
Best thing to do is to fastboot flash again, but use the clean all option.
It's never a good idea to dirty flash when doing anything other than updating a ROM. You might sometimes be OK if flashing from one AOSP ROM to another AOSP ROM.
If your going from MIUI to a custom ROM, or from a custom ROM to MIUI, then it's not worth the aggro you'll most likely get by dirty flashing. Just spend the extra time backing up your data and save the headache.
As for the data, try installing a different TWRP and see if that will then ask for a password to decrypt the phone, before you do a clean install of MIUI.
I've followed the process outlined here. After installing the ZIP, it rebooted, but went back to recovery. When I said reboot system, it said No OS installed.
So, I tried to start over by formatting data and then copying the zip again via ADB Push. Then the trouble starts. After adb push, which takes about 5 minutes, it says
Code:
failed to copy 'xiaomi.eu_multi_HMNote10Pro_V12.5.3.0.RKFMIXM_v12-11.zip' to '/sdcard/xiaomi.eu.zip': write failed: No space left on device
After that, the data partition seems corrupted. Whenever I go to Install, it shows 0 bytes. Upon Googling I found a solution by formatting to ext2 and back to ext4. Then, it shows again as 100000MB. However, adb push every time fails with same problem.
For some weird reason, I can push to /data. But still running into same problem after installing ROM and rebooting, it goes back into recovery.
I also tried to sideload, but then I run into this issue:
Code:
D:\Tools\ROMs>adb sideload xiaomi.eu_multi_HMNote10Pro_V12.5.3.0.RKFMIXM_v12-11.zip
loading: 'xiaomi.eu_multi_HMNote10Pro_V12.5.3.0.RKFMIXM_v12-11.zip'
* cannot read 'xiaomi.eu_multi_HMNote10Pro_V12.5.3.0.RKFMIXM_v12-11.zip' *
So, I'm stuck with a device without any ROM. Any suggestions please?
Did you ask in the MIUI EU forums as well? Since there would be more ppl familiar with these issues than here.
I'm also interested in this since I prefer EU roms. Also you need a specific TWRP version which I believe is still in alpha stage for the 10 Pro since its still a new device. There should be a TWRP thread somewhere here where you can also ask.
I just got my 10 pro and need to wait a few more days to unlock BL, then I will be flashing an EU rom, hence my interest. Hope you find a solution.
Use TWRP from here:
https://forum.xda-developers.com/t/4248449/
fastboot reboot bootloader
fastboot boot TWRP_file_name.img
Format Data, type yes.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Reboot to recovery.
The internal storage should be visible.
Connect phone to PC and put ROM into phone.
Flash ROM, format data, yes
Reboot to system.
If above not work, make your phone under fastboot mode, Mi-Flash, and flash your stock fastboot MIUI. Don't lock your bootloader.