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.
Related
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....
Good day. I am using viper one ROM and today I mistakenly wiped everything on my phone using TWRP recovery. So I can not boot my phone but I am able to enter TWRP. I tried to push ROM zip to phone using adb to data/media/0 but I cannot find the zip file anywhere, this is strange since the storage size on my phone showed in TWRP changes meaning the file is succesfully copied. My only choice now is use RUU which I never did before. I am coming from Samsung so HTC is new to me. I cannot run ADB sideload, it is stuck on starting when I do this.
{
"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"
}
My main version number is: 2.24.707.1 CID is 0_44. I have read that RUU's for this is not available?
Use vomers Guide
and also Mike`1986's guide
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
http://forum.xda-developers.com/showthread.php?t=2265618
KristianKenneth said:
Good day. I am using viper one ROM and today I mistakenly wiped everything on my phone using TWRP recovery. So I can not boot my phone but I am able to enter TWRP. I tried to push ROM zip to phone using adb to data/media/0 but I cannot find the zip file anywhere, this is strange since the storage size on my phone showed in TWRP changes meaning the file is succesfully copied. My only choice now is use RUU which I never did before. I am coming from Samsung so HTC is new to me. I cannot run ADB sideload, it is stuck on starting when I do this.
My main version number is: 2.24.707.1 CID is 0_44. I have read that RUU's for this is not available?
Click to expand...
Click to collapse
I honestly never tried TWRP (though will do so in a minute or two, just out of curiosity), but did you try pushing the rom to /sdcard/ or /data/media/ (no 0)?
I'm downloading TWRP now, just out of curiosity :cyclops:
EDIT: ok, tried TWRP and it seems it does go to /data/media/0 as default, though it seems some files were hidden or I just overlooked them.
Anyway, try pushing to /data/media/ and then in TWRP use the "up one level" or whatever they called it, and you should see your zip there.
you can adb sideload in TWRP http://forum.xda-developers.com/showthread.php?t=2317986
I always just do adb push rom.zip /sdcard/Roms/rom.zip and it shows up fine.
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
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.
Hello all,
I recently got my motherboard replaced after the pixel 5a died. The problem was covered under the extended warranty. Phone works just fine when I received it back. I tried rooting it using magisk to patch the boot.img file. After fastboot flash boot file.img, my phone would say device is corrupt and unable to start.
I downloaded the factory image from google. Tried using flash-all to completely restart the process. Used latest platform-tools (downloaded today). Bootloader is unlocked. I keep getting this error during the flash-all process and my phone is unable to boot. I'm still able to access fastboot. Where am I going wrong?
{
"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"
}
Here is larger screen shot of the entire flash-all process.
The issue is a known bug with latest SDK platform tools. Download and install platform-tools ver 33.x and you'll be fine.
Cheers!
flash stock rom via chrome browser , then patch boot.img and flash again to root , i am in lastest version a13 and root work fine
Typhus_ said:
The issue is a known bug with latest SDK platform tools. Download and install platform-tools ver 33.x and you'll be fine.
Cheers!
Click to expand...
Click to collapse
This is the fix, download platform-tools 34.0.0
Typhus_ said:
The issue is a known bug with latest SDK platform tools. Download and install platform-tools ver 33.x and you'll be fine.
Cheers!
Click to expand...
Click to collapse
This was my problem. I used 33 and it worked fine, thanks. Anyone know when it'll get fixed for 34?
when flash patched boot.img and is corrupt!!! Than Patch the recovery.img and flash it to Recovery Partition, you must start the device with Buttons-Combo in Recovery-Mode to start the System with Root!!! think you have no Recovery-Mode on this Method, you must Flash recovery.img new to use Recovery-Mode!!!