hello
my device has suddenly got stuck on the Google logo and wont boot normaly, i have no idea what to do.
please help
Nexus 9 WiFi'
** edit: i was trying to install a stock lolipop using Nexus Tool Kit and these are the resault many errors and mainly this error "out of memory"...
i would provide a pic but i cant upload due to the span prevention system in the forum...
Hard to say for sure what happened, but I can say it is always best to stay away from a toolkit as problems like this arise all too frequently
So long as your bootloader is unlocked flashing a factory image is the best choice
https://developers.google.com/android/nexus/images?hl=en
If you need a hand setting this up let me know
Best of luck
hey many thanks for the kind offer to help, i've been trying to flash a new factory image but no luck, i keep getting an erot while flashing [something about too many links or not enough memory], i'll provide a pic soon.
edit: i ran the flash-all script as instructed in the link you gave me, ended up with these errors: [i cant attach a pic since im a new user, system alert]
update package missing "system.img"
"archive does not contain "boot.sig"
"archive does not contain "recovery.sig"
in other case the fastboot froze [on the tablet] and an error popped up in the terminal "out of memory"
Try erasing and flashing partitions separately
fastboot format system
fastboot format cache
fastboot format data
fastboot format recovery
fastboot format boot
Now
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash data data.img
fastboot flash cache cache.img
Just unpack the .zip you downloaded and you'll find another zip with all these files
Some more help can be found here
http://forum.xda-developers.com/showthread.php?t=2277112
demkantor said:
Try erasing and flashing partitions separately
fastboot format system
fastboot format cache
fastboot format data
fastboot format recovery
fastboot format boot
Now
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash data data.img
fastboot flash cache cache.img
Just unpack the .zip you downloaded and you'll find another zip with all these files
Some more help can be found here
Click to expand...
Click to collapse
thanks, but when i was trying to format i got this error:
FAILED (data transfer failure (too many links))
every fastboot command i run fails for this reason.
when i try again to format the operation crushes.
just found a pic from other tread in this forus so i could add it, i have the same errors.
http://forum.xda-developers.com/attachment.php?attachmentid=2790293&d=1402378385
Shouldn't get that error when erasing, try updating your fastboot binary on PC, maybe also try another USB cable
demkantor said:
Shouldn't get that error when erasing, try updating your fastboot binary on PC, maybe also try another USB cable
Click to expand...
Click to collapse
can you please tell me how to do that? i tired several cables and ports, same error every time.
Guessing you are using windows? If so the best way is to have the android SDK downloaded and update through the available ui
More detailed instructions are available from the fastboot link I sent earlier
But the error you are getting is almost always a bad USB cable or port, at least whenever I have troubleshot that error with others that's what turned out to be the fault
demkantor said:
Guessing you are using windows? If so the best way is to have the android SDK downloaded and update through the available ui
More detailed instructions are available from the fastboot link I sent earlier
But the error you are getting is almost always a bad USB cable or port, at least whenever I have troubleshot that error with others that's what turned out to be the fault
Click to expand...
Click to collapse
Well yes i do use android SDK and its always up to date, i really dont understand the cables and port i have been using are all good since i use them with other devices too, i really dont know what else i should do...
one more thing, when trying to format boot and data i got this error:
formatting is not supported in filesystem type "raw" [something like that]
what does this mean?
edit: i was able to flash the system. boot, cache and recovery but the tablet still stuck on google logo
edit #2: i wasnt flashing correctly, i used the flash all script and it ran flawless, the tablet has booted and its faster then ever! i have another shot to a cable and port i still didnt use
and now its working, i cant thank you enough!
EladC said:
Well yes i do use android SDK and its always up to date, i really dont understand the cables and port i have been using are all good since i use them with other devices too, i really dont know what else i should do...
one more thing, when trying to format boot and data i got this error:
formatting is not supported in filesystem type "raw" [something like that]
what does this mean?
edit: i was able to flash the system. boot, cache and recovery but the tablet still stuck on google logo
edit #2: i wasnt flashing correctly, i used the flash all script and it ran flawless, the tablet has booted and its faster then ever! i have another shot to a cable and port i still didnt use
and now its working, i cant thank you enough!
Click to expand...
Click to collapse
How were you not flashing correctly?
I had the same issue.
Go into fastboot and flash the vendor.img
fastboot flash vendor vendor.img
Flashing the vendor.img actually did it - I followed the explanations above and was still stuck at the Google screen.
Formatting and flashing the following finally did the trick:
fastboot format system
fastboot format cache
fastboot format data
fastboot format recovery
fastboot format boot
(the three above failed due to an unsupported file system which didn't make a difference in my case)
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash data data.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
I have a Nexus 5X but it was the same issue when trying to flash LineageOS 14 after using Android 8.
I downloaded the vendor image from the official Linage OS thread and that fixed it. Only command I had to run was "fastboot flash vendor vendor.img". I did a factory reset with TWRP before booting though.
Related
I had TnT 0.2 installed when i got message internal storage damaged so i boot to clockwork and try to format and wipe device. then go back to FolioMod but when trying to install it installs system then it try to install boot.img i get error message:
assert failed: write_raw_image("/cache/boot.img", "linux")
E:Error in /sdcard/FolioMod.zip
(Status 7)
Installation aborted. Then i read someone else had the same issue onetime and his device had booted anyways and he had managed to fix it but it didnt say how?
I dont know these things but i was thinking maybe i could fastboot boot.img and that would work. But i really dont know these things well enough, im just used to follow guides, so i really dont know the right procedure. Or maybe theres another answer, anyways i need help. Some info my device boots in to recovery and it reads my external sdcard. Thankfull for help, i want my Folio
Hi, it was me who had the same problem.
Try "LOST or Destroyed partitions - METHOD 2 - ADB USB" on http://bb2k.org/folio100wiki/index.php/FolioMod_Issues
Loupák said:
Hi, it was me who had the same problem.
Try "LOST or Destroyed partitions - METHOD 2 - ADB USB" on http://bb2k.org/folio100wiki/index.php/FolioMod_Issues
Click to expand...
Click to collapse
Thank you for answering. but i dont see how i can connect to adb. I was thinking maybe i can flash a rom from clockwork as it installs system and if i could fastboot boot.img to get it to boot. Or if i can flash stock recovery so I could go by Method 1. But the links are broken for the partion map. Please if anybody has any ideas or knows a way. If not I was thinking of fastbooting stock recovery and send it in to toshiba and just say its broken.
Anyone? Problem not solved. If anyone could please help me or guide me in the right direction
It's simple
Put a boot.img on your android files (computer)
Launch Fastboot on command DOS
Fastboot flash linux boot.img
If this don't work
Fastboot erase cache
Fastboot erase system
Fastboot erase userdata
And try again and launch recovery on your Folio to install system/cache partition etc
Sinate said:
It's simple
Put a boot.img on your android files (computer)
Launch Fastboot on command DOS
Fastboot flash linux boot.img
If this don't work
Fastboot erase cache
Fastboot erase system
Fastboot erase userdata
And try again and launch recovery on your Folio to install system/cache partition etc
Click to expand...
Click to collapse
Thank you sounds good. Do i need a special fastboot? Because the with the one that comes with SDK i seem to have some problem. I put my Folio in fastboot, i insert mini usb, computer recognizes, i update folio driver in device manager to the one we use for ADB(Bootloader). And all goes well but when i open comman window and type fastboot devices i get:
fastboot devices
? fastboot
Then i rememberd something , when instaling fastboot for DesireHD on my other computer i had to download another fastboot from Modaco for it to work.
Gratefull for help if anyone recognizes this when setting up fastboot or knows what im doing wrong.
Come on, someone. Still not fixed. Cant get fastboot to work, i have fastboot setup for Nexus S and always had it setup for my phones but i dont get this, why doesnt it work?
PROBLEM SOLVED
Did you get the message: Magic Value Mismatch:-.-.-.-.-.-?!
After flashing a new recovery it happens sometimes.
GREEN ZONE
Are you able to go to the recocery menu(power + vol up)? If not, go to BLUE ZONE. If yes, follow these steps
1. check whether you have copied your rom as "update.zip" to your SD card's root directory
2. Go to recovery menu and install update.zip
BLUE ZONE
You may did something wrong while flashing a new recovery. Here is the right method:
1. go back to fastboot mode(power+power+power+vol up) and type these commands on your PC
2. fastboot erase userdata
3. fastboot erase system
4. fastboot erase cache
5. fastboot erase linux
6. fastboot erase recovery
7. fastboot flash recovery recovery.img (change path, if recovery.img is not in the same directory as fastboot.exe)
8. fastboot reboot
Are you able now to go to the recovery menu? If yes, go to GREEN ZONE and follow steps. If not, go to ORANGE ZONE.
ORANGE ZONE
Are able to unpack the update.zip and find the system.img and boot.img files? If not, then go to RED ZONE. If yes, copy these 2 files to the directory where the fastboot.exe is, run these commands:
1. fastboot erase recovery
2. fastboot flash recovery recovery.img
3. fastboot -w
4. fastboot erase linux
5. fastboot erase system
6. fastboot flash system system.img
7. fastboot flash linux boot.img
8. fastboot reboot
ROM is installed. Enjoy it!
RED ZONE
Make sure, that you copied the same recovery.img to fastboot folder, that you had flashed before to your tablet.
Type this command in recovery mode:
1. fastboot boot recovery.img
This command will run the recovery from your PC. After the recovery menu is booted, go to GREEN ZONE and enjoy your ROM!
If this was helpful to you, please do not hesitate to click on Thanks!
Lol, nice to see my post copy/pasted without any links indicated. Anyway, I hope It's helpful for ppl.
Tried following these steps, however, I'm still getting this error... followed this thread
http://forum.xda-developers.com/showthread.php?t=1470823
installed recovery successfully (via fastboot), and update seems to install fine, until I reboot and get the "Magic Value Mismatch" again..
Any ideas?
yellowumbrella said:
Tried following these steps, however, I'm still getting this error... followed this thread
http://forum.xda-developers.com/showthread.php?t=1470823
installed recovery successfully (via fastboot), and update seems to install fine, until I reboot and get the "Magic Value Mismatch" again..
Any ideas?
Click to expand...
Click to collapse
So you installed the recovery via fastboot. Did you manage to boot into recovery mode?
I had that issue, that I couldn't boot into recovery mod from my Folio, by pressing power+Up button. Thats why I added the RED ZONE method. Its like booting recovery from your PC. (fastboot boot recovery.img). All the times I wanna upgrade my current ROM, I have to do this step, because the power+up does not work, and the Folio skips booting in recovery and wanna do normal booting. However there is no Rom installed on machine, so I get the magic value mismatch message.
So try to boot recovery from your PC, but be sure you have copied to your fastboot folder the same recovery, that you flashed onto the tablet.
I hope it was helpful. If something is not clear, feel free to ask.
Hi there, thanks for the answer.
I am able to install recovery images via fastboot.
Device is showing up as a question mark with >fastboot devices
but recovery installs fine. CWM gives a series of e: can't opne/mount /cache errors.
Foliomod 1.4 installs no problem, thanks to the method here
http://forum.xda-developers.com/showthread.php?t=1458876
yellowumbrella said:
Hi there, thanks for the answer.
I am able to install recovery images via fastboot.
Device is showing up as a question mark with >fastboot devices
but recovery installs fine. CWM gives a series of e: can't opne/mount /cache errors.
Foliomod 1.4 installs no problem, thanks to the method here
http://forum.xda-developers.com/showthread.php?t=1458876
Click to expand...
Click to collapse
Are you able to wipe cache from recovery? And what else errors are listed?
One more thing, try to flash your boot.img and system.img via fastboot as written above.
If I follow this
http://forum.xda-developers.com/showthread.php?t=1458876
and let it install cwm v 3, I get the cache error and cannot wipe or mount via recovery.
If I follow the ICS thread, and flash the new cwm v5 via fastboot, I don't get the cache error, but the rom simply won't start. If I open the package, there is a boot.img, but not a system.img, just a system folder...
I could try flashing boot.img, but I don't see how that could help
yellowumbrella said:
If I follow this
http://forum.xda-developers.com/showthread.php?t=1458876
and let it install cwm v 3, I get the cache error and cannot wipe or mount via recovery.
If I follow the ICS thread, and flash the new cwm v5 via fastboot, I don't get the cache error, but the rom simply won't start. If I open the package, there is a boot.img, but not a system.img, just a system folder...
I could try flashing boot.img, but I don't see how that could help
Click to expand...
Click to collapse
Well just to see it clear. So you are able to install Foliomod 1.4, so your Internal storage is not broken.
When I get home, I will check the system folder of ICS rom. There are some method to create system.img from an unpacked folder...
So, in CWM 5.5.0.4 you manage to install Zip from SD card, ROM and GAPPS as well, but the Rom does not boot?!
yup, that's exactly it.
Haven't tried installing Gapps since I can't even get the rom to boot.
I have a perfectly working tablet with foliomod 1.4, and I did get honeycomb to run but some apps crashed so I reverted back to foliomod.
with CWM CWM 5.5.0.4 everything seems to work great, except at reboot, nothing happens (somehow, I no longer even get the magic value mismatch)
------------------
PS. not sure if this is at all relevant, but I cannot fastboot from win7, I'm fastbooting in either ubuntu or xp via VirtualBox, and the device, when calling >fastboot devices shows up as ?????????? (ubuntu) and ? (xp)... :\
yellowumbrella said:
yup, that's exactly it.
Haven't tried installing Gapps since I can't even get the rom to boot.
I have a perfectly working tablet with foliomod 1.4, and I did get honeycomb to run but some apps crashed so I reverted back to foliomod.
with CWM CWM 5.5.0.4 everything seems to work great, except at reboot, nothing happens (somehow, I no longer even get the magic value mismatch)
------------------
PS. not sure if this is at all relevant, but I cannot fastboot from win7, I'm fastbooting in either ubuntu or xp via VirtualBox, and the device, when calling >fastboot devices shows up as ?????????? (ubuntu) and ? (xp)... :\
Click to expand...
Click to collapse
Try to install gapps as well. Maybe it helps...
nope, no luck even with gapps installed..
just a blank screen..
sigh
yellowumbrella said:
nope, no luck even with gapps installed..
just a blank screen..
sigh
Click to expand...
Click to collapse
Have you tried all the roms? ICS Alpha 1,2,3 and 4?
Tried 3 and 4, didn't bother trying earlier ones, as it seems the latest ones work for most users
yellowumbrella said:
nope, no luck even with gapps installed..
just a blank screen..
sigh
Click to expand...
Click to collapse
Hmmm strange. I ask it for you on developers forum. What you can still do, is to check the steps, that you did them correctly. In most of the cases users forget something, or do some steps incorrectly.
Try to erase userdata, cache, system, linux and recovery in fastboot. You mentioned you had problem with fastboot under Win7. Problem may occur, in case of not proper erasing.
Thanks, I'll give it another try tonight.
Fastboot in win7 is simply not seeing the device. It shows up in XP and Ubuntu, but as "??????" - not sure if that could be a symptom.
I'll post a reply as soon as I've tried, and let you know how it went.
yellowumbrella said:
Thanks, I'll give it another try tonight.
Fastboot in win7 is simply not seeing the device. It shows up in XP and Ubuntu, but as "??????" - not sure if that could be a symptom.
I'll post a reply as soon as I've tried, and let you know how it went.
Click to expand...
Click to collapse
For me it works perfectly on Win7. After Installing SDK and JDK the in the devicemanager it is shown as an Unknown device. Simply add the driver manually to it.
Download driver from attachment.
Copy it to SDK\USB_driver folder
That works for me. After its done, the Folio is shown as "Fastboot" in device manager. But connect the tablet in fastboot mode to your PC before you add driver manually to it.
Thanks for that.
Tried it, still not working in win7. It shows up correctly in device manager, but fastboot itself just doesn't want to see it...
I've attached a screenshot for you
EDIT: screenshot gets resized, but it shows device manager listing
NVIDIA Android Fastboot Device
and a terminal with fastboot not seeing the device
yellowumbrella said:
Thanks for that.
Tried it, still not working in win7. It shows up correctly in device manager, but fastboot itself just doesn't want to see it...
I've attached a screenshot for you
EDIT: screenshot gets resized, but it shows device manager listing
NVIDIA Android Fastboot Device
and a terminal with fastboot not seeing the device
Click to expand...
Click to collapse
When You have win7, You have run the console as admin!
Or copy the complete Fastboot folder to another Destination like c:\temp...
Thanks stefannsv, tried it, still not showing...
But I can access fastboot on another platform, so I assume it's not an issue, I can just switch over to another OS to flash
no go, followed both this original post (tried all steps except orange, cause the rom I'm trying to install has a system folder, not a system.img)
Last method I tried was:
1) boot into fastboot
2) boot cwm-recovery-5.5.0.4.img directly from PC
3) wipe data/factory reset
4) wipe cache partition
5) install zip from SD card and chose the alpha 4 release
installing update...
then back to recovery, reboot and voilà... magic value mismatch again (it had disappeared for a while... )
Also, when booting into CWM 3.0.0.5, I get a series of "E: Can't mount/cache/recovery" type errors.. could this be related?
booting directly into recovery from PC doesn't alllow me to install any ROMS, not even foliomod 1.4 which works if using puppet13th's method
So I relocked my bootloader after upgrading to marshmallow and forgot that I did that..... I tried to flash a stock boot img so I could utilize the ota, and it sort of bricked my tablet. Being a total dumbass I didn't realize that was the problem. Having had a similar issue before on my galaxy s4 where I follow a similar solution. I already have twrp installed, and it was asking for encryption for which there was none. So I wiped data and formatted to get past the encryption. On my s4 I was then able to reinstall the stock firmware and software. However when I tried to push the bootloader to my nexus I got this weird error.. can someone pleeeeeeease spare me and help me out. This tablet is my lifeline for college...
Don't get me in trouble for posting this image please lol, I just don't have enough posts. http ://i67.tinypic.com/v80vwl.jpg[/B][/B]
I figured it out, I was just being dumb. I just needed to use the fastboot commands and not try to use twrp
tdct12 said:
So I relocked my bootloader after upgrading to marshmallow and forgot that I did that..... I tried to flash a stock boot img so I could utilize the ota, and it sort of bricked my tablet. Being a total dumbass I didn't realize that was the problem. Having had a similar issue before on my galaxy s4 where I follow a similar solution. I already have twrp installed, and it was asking for encryption for which there was none. So I wiped data and formatted to get past the encryption. On my s4 I was then able to reinstall the stock firmware and software. However when I tried to push the bootloader to my nexus I got this weird error.. can someone pleeeeeeease spare me and help me out. This tablet is my lifeline for college...
Don't get me in trouble for posting this image please lol, I just don't have enough posts. http ://i67.tinypic.com/v80vwl.jpg[/B][/B]
I figured it out, I was just being dumb. I just needed to use the fastboot commands and not try to use twrp
Click to expand...
Click to collapse
If your able to access the bootloader menu or the fastboot menu, you could flash the stock and would fix the brick,soft brick or boot-loop.
Head to Google developer nexus image. Download the factory image of your devices on your devices. Extract all the files and copy paste the fastboot and adb files. Head to your devices and open the fastboot menu.
Type the following commends to restore your devices if the flashall did not work.
Fastboot oem unlock
Fastboot flash bootloader bootloader....
Fastboot reboot-bootloader
Fastboot erase boot
Fastboot flash boot boot.img
Fastboot erase recovery
Fastboot flash recovery recovery.img
Fastboot erase system
Fastboot flash system system.img (this could take up to 15 minutes, don't do anything to stop the process you can make your devices and a worst state)
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot erase vendor
Fastboot flash vendor vendor.img
Fastboot reboot
This should fix your devices. I did not and it save each time I broke my device or anything similar.
If you want after all that. You can enter the following commends to relock your devices but don't make the same mistake you did before. If you want to avoid that same mistake just don't enter the commends.
What the guy above me said, also pro tip, some times not all the files will extract just keep extracting till all the image files are there.
Current State:
TWRP Installed, no OS, no system partition, instead a super partition.
I also flashed an orange_state_disabler which seems to have worked just fine.
ADB Sideload:
When I try to start ADB Sideload Feature this is what I get:
https://pastebin.com/k3gJ048P
when trying to use the adb sideload command:
Code:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
I converted the lineageos img file I have to a flashable zip using the tool from here:
https://forum.xda-developers.com/nu.../swapper-generate-flashable-zips-img-t4133591
but when I try to flash that zip file tho it returns this:
Code:
Installing zip file '/usbotg/system.zip'
Checking for Digest file...
Unmounting System...
Invalid zip file format!
Error installing zip file '/usbotg/system.zip'
Updating partition details...
...done
so... yeah, I don't know what else to do right now.
A Custom ROM like LineageOS can only get installed via TWRP, not by any other means: in no case by "adb sideload".
jwoegerbauer said:
A Custom ROM like LineageOS can only get installed via TWRP, not by any other means: in no case by "adb sideload".
Click to expand...
Click to collapse
Heh, I was just trying to get the ROM on the device so I could flash it then via TWRP but maybe I just misunderstood what adb sideload does
0
Seppppx said:
The Oneplus 8 Pro has a dynamic partition layout and you flash a system image by doing "fastboot flash system system.img"
See : https://forum.xda-developers.com/oneplus-8-pro/development/rom-lineageos-17-1-t4122983
Click to expand...
Click to collapse
Yeah I tried that already, the problem is that it doesn't have a system partition
MoonPadUSer said:
Yeah I tried that already, the problem is that it doesn't have a system partition
Click to expand...
Click to collapse
Your posted error messsage suggests the zip install has failed. So no change to device should have happened.
Current twrp cannot flash system.img
Only super.img(combined system.img, vendor.img, and product.img)
The systemswapper you refered to is from a qualcom device thread, and uses some *qti* device binaries that are not in your recovery. It is unlikely to have worked. (I might be wrong about the *qti* binary being only a qualcom device tool)
These new devices with dynamic partition have 2 fastboot modes.
The bootloader mode (adb reboot bootloader)
This is used for unlocking bootloader, flashing standard partitions
There is fastbootd mode (adb reboot fastboot)
This mode is only available if stock recovery is installed.
It also requires r30 or higher fastboot binary file on PC.
From fastbootd you can flash the sub partitions on super.img
There is alot of changes that take place with this new partition setup.
As for your phone no longer booting into original system, and bootlooping to recovery, I suggest first try boot to bootloader, and flash stock recovery, see if this stopps the bootlooping.
If not then use sp flash tool and flash full stock room and start fresh
mrmazak said:
From fastbootd you can flash the sub partitions on super.img
Click to expand...
Click to collapse
How?
MoonPadUSer said:
How?
Click to expand...
Click to collapse
Fastbootd is part of stock recovery, it will look different than what you may be used to as being fastboot mode.
You should see options on screen to select just like stock recovery has.
One for boot to bootloader
One for boot to recovery.
When you confirm you are in fastbootd
You just use
Code:
fastboot flash system /some-directory-on -pc/gsi-system.img
You should see messages on screen
Resizing system
Sending sparce system chunck. 1 of x
Writing system chunck 1 of x
There could be more descriptive guide on flashing gsi on dyniamic partitions if your Search google, (xda).
But it is hard to guide you to fixing device, when I'm not sure how you got stuck. I mean the description you have said should not have made you loose system partition or fail to boot, so I said it before and will suggest it again. If you have a non booting device , the FIRST thing you should do is flash it with sp flash tool and full factory rom, before messing around with other stuff before you get into worse condition
MoonPadUSer said:
How?
Click to expand...
Click to collapse
I did another post about using fastbootd on similar device. The information is all relevant to your a7pro too.
https://forum.xda-developers.com/showpost.php?p=83241985&postcount=3
mrmazak said:
Fastbootd is part of stock recovery, it will look different than what you may be used to as being fastboot mode.
You should see options on screen to select just like stock recovery has.
One for boot to bootloader
One for boot to recovery.
When you confirm you are in fastbootd
You just use
You should see messages on screen
Resizing system
Sending sparce system chunck. 1 of x
Writing system chunck 1 of x
There could be more descriptive guide on flashing gsi on dyniamic partitions if your Search google, (xda).
But it is hard to guide you to fixing device, when I'm not sure how you got stuck. I mean the description you have said should not have made you loose system partition or fail to boot, so I said it before and will suggest it again. If you have a non booting device , the FIRST thing you should do is flash it with sp flash tool and full factory rom, before messing around with other stuff before you get into worse condition
Click to expand...
Click to collapse
Ok, I am back to a fully working device again, where I got stuck was that I do not have a system partition, thus I can't flash it. Whenever I try to flash it using fastboot flash system or anything else, it just says that I do not have a system partition
Where I am right now:
I am back to a fully working device after downloading the stock ROM from my manufacturer and plugging that into SP Flash tool
After that I researched and figured out that the super partition I have basically acts like a container for
system.img, boot.img and vendor.img
which explains while simply flashing LineageOS.img to my super partition (
Code:
fastboot flash system Lineage.img
) resulted in
my device not booting anymore.
I found a tool which can unpack those super.img into system, boot and vendor
(using this youtube video: https://youtu.be/J5cQdzivtXk)
I used that to unpack the super.img which I got from my stock ROM and
now I have system.raw, boot.raw and vendor.raw, I do not know what kind of file these are but my plan is to replace system.whatever with the lineageos.img and then repack it into super.img which I can then use to flash the super partition on my phone
MoonPadUSer said:
Ok, I am back to a fully working device again, where I got stuck was that I do not have a system partition, thus I can't flash it. Whenever I try to flash it using fastboot flash system or anything else, it just says that I do not have a system partition
Click to expand...
Click to collapse
Can you show picture of this .
Of both pc screen and phone screen, please
mrmazak said:
Can you show picture of this .
Of both pc screen and phone screen, please
Click to expand...
Click to collapse
I'd love to but how am I supposed to take a picture of my phone screen in fastboot mode? (I don't have any other devices with a camera)
@MoonPadUSer
Code:
fastboot flash system Lineage.img
must have failed.
Reason: This command tries to write a complete Lineage OS ( what itself contains a partition named /system, too ) into phone's Android's current /system partition - what only is 1 partition of multiple ones that exist.
Note: You can't flash a Custom ROM by means of Fastboot.
Re-read post #2
0
Seppppx said:
That's not true when you are flashing a Generic System Image.
Click to expand...
Click to collapse
ROFL
Remember OP wants to install LineageOS 17.1 what isn't a GSI as it is with LineageOS 18.x
jwoegerbauer said:
ROFL
Remember OP wants to install LineageOS 17.1 what isn't a GSI as it is with LineageOS 18.x
Click to expand...
Click to collapse
Actually... I don't really care about the version all that much, whatever works, just didn't know if 18x is supported
Downside to Lineage GSI is for Umidigi you can't flash gapps. So unless someone adds it to the gsi for you it's best to use something else.
I went with this
https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559
You have to get the AB version with GAPPS if you want them
Comes pre rooted as well and gave my phone a huge speed boost
Flash the stock ROM
Unlock bootloader
fastboot flashing unlock
(unnecessary if already unlocked)
fastboot flashing unlock_critical
enter fastboot
fastboot reboot (to enter fastbootd)
fastboot erase system
(optional but I had to do this myself)
fastboot delete-logical-partition product - deletes the product partition, allowing a larger system partition
fastboot flash system (gsi file)
And you're good
Don't try to install magisk because it causes a bootloop. Even when installing it through the app. Once the boot image is patched you're in a bootloop until you reflash the stock boot
Made a generic ish Umidigi flashing tutorial because it's the same in all of them I've had so far
https://forum.xda-developers.com/an...ng-rom-gsi-t4182673/post83803205#post83803205
I can't install any rom, ADB sideload fails with this error:
Unable to mount storage.
Devices on super may not mount until rebooting recovery.
To flash additional zips, please reboot recovery to switch to the updated slot.
I already tried to switch the slots many times.
I also tried to format data, but it tells me:
E: unable to check merge status
Updating partition details...
...done
Unable to mount storage
I can access the recovery and the factory-reset android, but i can't do anything more.
I think the problem is relative to encryption but I can't even format data, so I don't know how to escape this...
Now I can't even access the rom, I can only access TWRP and fastboot. The problem is that format data does not work, with the same error:
E: unable to check merge status
I tried repairing and changing filesystem, now I don't really know what to do...
just install rom using fast boot tool and
format data after that
muneeb rizwan said:
just install rom using fast boot tool and
format data after that
Click to expand...
Click to collapse
I have never used fastboot tool. I'm on linux. Is this the program i must install?
And also, do I need a fastboot rom?
[Tool] Flash Custom ROMs through Fastboot [mojito / sunny]
Are you struggling to install custom roms on this device? Lots of recovery errors? Can't boot to any rom? Don't worry. Fastboot is a good way to avoid such nonsense... Install any custom rom & miui recovery rom through fastboot Steps: 1...
forum.xda-developers.com
USE THIS TOOL AND YOU DONT NEED FASTBOOT ROM
Ok, i installed CrDroid with fastboot tool, then format data and then re-flashed the rom with adb, but the phone starts just on the CrDroid recovery (slot b) or on fastboot (slot a)...
What is the correct process to install a ROM? This A/B thing gets me mad
Now I managed to install an old MIUI fastboot rom from this link with XiaomiADBFastbootTools (a kind of mi flash tool for linux) and this rom now it is working, so I think I had some problems with the fastboot tool you suggested. But I don't really know what was the problem, the installation process seemed to work, It restarted to recovery, I rebooted to system but then it kept returning to recovery or to fastboot without entering in the system...
Switching slots directly in recovery is not functional. Just look after switching what the active slot is and you will see that it has not changed. Do the slot switching with the fastboot command from the PC.
fastboot --set-active=a
fastboot --set-active=b
StaryMuz said:
Switching slots directly in recovery is not functional. Just look after switching what the active slot is and you will see that it has not changed. Do the slot switching with the fastboot command from the PC.
fastboot --set-active=a
fastboot --set-active=b
Click to expand...
Click to collapse
yes, I was using these commands to switch slots. but when it is necessary to switch slots in the flashing process? I mean, what is the correct order? format - flash rom with adb - reboot to fastboot - switch slot - reboot to system...is this correct?
Slot swapping may not be required. Do it only when it is requested or when the boot crashes into recovery.
StaryMuz said:
Slot swapping may not be required. Do it only when it is requested or when the boot crashes into recovery.
Click to expand...
Click to collapse
OK, so is this the correct order?
Format - flash rom with adb - reboot to system
Now I have a problem with fastboot...I don't know why but it can't boot any recovery...
"fastboot boot recovery.img" remains stuck at:
Sending 'boot.img' (131072 KB)
Click to expand...
Click to collapse
and nothing happens! I tried with TWRP and OrangeFox.
I also tried to change slot but it fails:
fastboot --set-active=a
Setting current slot to 'a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
The command 'Fastboot reboot' gives me a black screen with a white message: 'any key to shutdown', then the phone reboots to system...
What is the full designation of your phone?
StaryMuz said:
What is the full designation of your phone?
Click to expand...
Click to collapse
what is the designation?
Xiaomi Redmi Note .....
All of it, exactly.
StaryMuz said:
Xiaomi Redmi Note .....
All of it, exactly.
Click to expand...
Click to collapse
Redmi Note 10 64GB/4GB, I think the codename is sunny because I have the global/european version. Do you need more?
I think the best step is to upload the original Miui using MiFlash with the "clear all" setting.
Use this version of MiFlash.
You can get the right Miui here.
Before using MiFlash, I recommend loading the boot.img included in the downloaded Miui into your phone in fastboot mode.
Use the command:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Then use MiFlash and don't play Miui. Wait until the phone starts itself, then you can disconnect it.
If anything is not clear, ask questions.
StaryMuz said:
I think the best step is to upload the original Miui using MiFlash with the "clear all" setting.
Use this version of MiFlash.
You can get the right Miui here.
Before using MiFlash, I recommend loading the boot.img included in the downloaded Miui into your phone in fastboot mode.
Use the command:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Then use MiFlash and don't play Miui. Wait until the phone starts itself, then you can disconnect it.
If anything is not clear, ask questions.
Click to expand...
Click to collapse
Actually I'm already in a original MIUI and it is working. My pc is on linux so I can't use MiFlash but I used XiaomiADBFastbootTools (a kind of MiFlash tool for linux). Can I start from here or I have to install the MIUI version you linked?
The only thing is that I didn't specifically load the boot.img
Unfortunately I don't know the Linux version of MiFlash. They may not work equivalently. It needs to properly clean all the partitions of the phone and load all the files supplied in the ROM.
I recommend to use the Miui listed by me.