Related
Hi everybody!! I have a BIG issue: my nexus 4 is unlocked, with the CWM recovery and CyanogenMod 10.1 installed. Due to some technical problems, I decided to flash the factory rom again (following this guide http://forum.xda-developers.com/showthread.php?t=2010312) but I can't do it!! Indeed when I try to flash the factory rom the prompt says
file:could not allocate 544035848 bytes
error:cannot load system.img :not enough space
And when i checked the system capacity the result is that my system partition doesn't exist (as you can see on the pic attached)!
I wish to send my phone back to google with the RMA (it was delivered 7 days ago) but I'm not sure that the warranty is still valid (what do you think about that?). Indeed there is no OS now, and everything is unlocked.
Anybody could help me?
Thanks a lot!!
StefanoRedi said:
Hi everybody!! I have a BIG issue: my nexus 4 is unlocked, with the CWM recovery and CyanogenMod 10.1 installed. Due to some technical problems, I decided to flash the factory rom again (following this guide http://forum.xda-developers.com/showthread.php?t=2010312) but I can't do it!! Indeed when I try to flash the factory rom the prompt says
file:could not allocate 544035848 bytes
error:cannot load system.img :not enough space
And when i checked the system capacity the result is that my system partition doesn't exist (as you can see on the pic attached)!
I wish to send my phone back to google with the RMA (it was delivered 7 days ago) but I'm not sure that the warranty is still valid (what do you think about that?). Indeed there is no OS now, and everything is unlocked.
Anybody could help me?
Thanks a lot!!
Click to expand...
Click to collapse
use the fastboot commands to erase system, boot, and data. then use flashboot to flash bootloader, then stock recovery, then stock system.
EvoXOhio said:
use the fastboot commands to erase system, boot, and data. then use flashboot to flash bootloader, then stock recovery, then stock system.
Click to expand...
Click to collapse
Thanks!! Just a couple of questions: 1. the prompt commands are "fastboot erase system" "fastboot erase boot" and "fastboot erase data", right? 2. Have I to reboot the system between every erase and every flash?
StefanoRedi said:
Thanks!! Just a couple of questions: 1. the prompt commands are "fastboot erase system" "fastboot erase boot" and "fastboot erase data", right? 2. Have I to reboot the system between every erase and every flash?
Click to expand...
Click to collapse
That sounds right but Fiona search to be safe. No reboots needed.
StefanoRedi said:
Thanks!! Just a couple of questions: 1. the prompt commands are "fastboot erase system" "fastboot erase boot" and "fastboot erase data", right? 2. Have I to reboot the system between every erase and every flash?
Click to expand...
Click to collapse
I tryed to do it without results. I attach the screen.
Have you some other advises? I really don't know what i can do it with my phone. If i send it back to google, do you think that they will check if my phone is locked/unlocked, with/without os, ecc? Because I'm afraid to have wasted my money!
Have you tried booting into recovery and wiping everything before flashing system? Also you're sure you have the right system.img? Maybe re-download the files from google and try again?
---------- Post added at 09:23 AM ---------- Previous post was at 09:22 AM ----------
also, do you have any nandroids or downloaded ROMs on the phone? If so, you could try flashing CWM, and then booting into it and restoring the nandroid or installing a ROM.
R: Cannot flash system.img, df shows no system partition
We tried wiping everything trough fast boot, he does not have any nandroid backup and I think he tried to flash another ROM (cm) with no luck.
We downloaded the right images, we tried both 4.2.1 and JOP40D from the Google site and from the mirror that we found in some thread here on xda.
(I'm his friend and I was helping him via Skype, that's why I know these informations)
I think now we'll try to flash cwm and wipe everything trough it and install a stock ROM or a custom one.
Ty for the help.
Sent from my Nexus 4
squalluca said:
We tried wiping everything trough fast boot, he does not have any nandroid backup and I think he tried to flash another ROM (cm) with no luck.
We downloaded the right images, we tried both 4.2.1 and JOP40D from the Google site and from the mirror that we found in some thread here on xda.
(I'm his friend and I was helping him via Skype, that's why I know these informations)
I think now we'll try to flash cwm and wipe everything trough it and install a stock ROM or a custom one.
Ty for the help.
Sent from my Nexus 4
Click to expand...
Click to collapse
It really sounds like someone made a mistake and ran the wrong command and actually remove the /system partition. Not erased or formatted, but actually removed the mount point. I'm sure there is a way to recreate it, but I have no idea how.
R: Cannot flash system.img, df shows no system partition
That's what I think too... this error appeared before we tried any wipe/erase command trough fastboot... hope someone can help us in recrate the mount point for the system partition...
Sent from my Nexus 4
EvoXOhio said:
It really sounds like someone made a mistake and ran the wrong command and actually remove the /system partition. Not erased or formatted, but actually removed the mount point. I'm sure there is a way to recreate it, but I have no idea how.
Click to expand...
Click to collapse
Thanks guys! I really hope that someone knows how to recreate it and, if it's possibile, very soon, because the RMA expiration day is coming!!
This is generally to be avoided, but I think this may actually be a last resort situation. Download the full factory image extract down a few levels until you have flash-all.bat extracted, at that point you'll also see the radio, bootloader, an image zip, and some linux scripts. Make sure you've actually extracted them and that you aren't just looking in the zip. Run flash-all.bat Don't touch anything until it's done, if you disrupt the write to bootloader or possibly radio, you brick.
By the way, the factory image is here and you may need to use 7zip to extract it. 7zip will have shell integration, so just right click what you want, drop down to 7zip and extract to.
Also, you may be able to accomplish the same thing with:
Code:
fastboot -w update image-occam-jop40c.zip
so maybe try that first.
USSENTERNCC1701E said:
This is generally to be avoided, but I think this may actually be a last resort situation. Download the full factory image extract down a few levels until you have flash-all.bat extracted, at that point you'll also see the radio, bootloader, an image zip, and some linux scripts. Make sure you've actually extracted them and that you aren't just looking in the zip. Run flash-all.bat Don't touch anything until it's done, if you disrupt the write to bootloader or possibly radio, you brick.
By the way, the factory image is here and you may need to use 7zip to extract it. 7zip will have shell integration, so just right click what you want, drop down to 7zip and extract to.
Also, you may be able to accomplish the same thing with:
Code:
fastboot -w update image-occam-jop40c.zip
so maybe try that first.
Click to expand...
Click to collapse
Fine, I will try when I come back home. Just a question: what do you think about the warranty? Do you think that google will check if the phone is unlocked and without os? It is better for me risk with the last suggested process and (maybe) brick the phone or send it back as it is now? It's because I'm just a beginner with mod, scripts, prompts, ecc..sorry!
StefanoRedi said:
Fine, I will try when I come back home. Just a question: what do you think about the warranty? Do you think that google will check if the phone is unlocked and without os? It is better for me risk with the last suggested process and (maybe) brick the phone or send it back as it is now? It's because I'm just a beginner with mod, scripts, prompts, ecc..sorry!
Click to expand...
Click to collapse
The phone was damaged from user error. It is unethical and probably illegal to RMA it. Try to fix it yourself, and if you can't, man up and buy a new phone. RMAs are for faulty products, not products ruined by an inexperienced user doing something wrong.
EvoXOhio said:
The phone was damaged from user error. It is unethical and probably illegal to RMA it. Try to fix it yourself, and if you can't, man up and buy a new phone. RMAs are for faulty products, not products ruined by an inexperienced user doing something wrong.
Click to expand...
Click to collapse
You are completely right. I wrote that just because I messed up the phone (following guides, using toolkit, using cmd in a proper way) trying to fix it (from the first day it was impossible to call due to microphone/speaker software problem). And sometimes, while a was doing the same stuff that everybody do with good results, the phone didn't do what it was supposed to do. Consequently I wanted to RMA it because i think it's my fault (I know it and I admit it) but not completely. I really don't want to cheat anyone.
Well, I fixed it. I don't know the reason but the day after everything was fine (maybe it's because I erased everything from CWM; i wiped everything and then i wen on Mount and I erased everything). Btw, the day after I reflashed everything from prompt with the phone in fastboot and i flashed also system (the partition was "avaible" again); the .img flashed was the factory rom 4.2.0. Then I reboot it but the problem with microphone/speacker wasn't fixed; i updated to 4.2.1 and it still didn't work. Today I will call google to RMA it because now (just now) the phone is not working properly but not due to my errors. Thanks to everybody!!!! :laugh:
StefanoRedi said:
Well, I fixed it. I don't know the reason but the day after everything was fine (maybe it's because I erased everything from CWM; i wiped everything and then i wen on Mount and I erased everything). Btw, the day after I reflashed everything from prompt with the phone in fastboot and i flashed also system (the partition was "avaible" again); the .img flashed was the factory rom 4.2.0. Then I reboot it but the problem with microphone/speacker wasn't fixed; i updated to 4.2.1 and it still didn't work. Today I will call google to RMA it because now (just now) the phone is not working properly but not due to my errors. Thanks to everybody!!!! :laugh:
Click to expand...
Click to collapse
Make sure flash stock recovery and relock the device before sending it in.
EvoXOhio said:
Make sure flash stock recovery and relock the device before sending it in.
Click to expand...
Click to collapse
Of course! In theory it will not be a problem if there is the CWM recovery and if the phone it's unlucked (at least, I read that for Google and LG is not a problem), but I flashed the stock recovery and then I lucked the phone again. Thanks for your advises.
system.img cannot load, not enough space error
StefanoRedi said:
Well, I fixed it. I don't know the reason but the day after everything was fine (maybe it's because I erased everything from CWM; i wiped everything and then i wen on Mount and I erased everything). Btw, the day after I reflashed everything from prompt with the phone in fastboot and i flashed also system (the partition was "avaible" again); the .img flashed was the factory rom 4.2.0. Then I reboot it but the problem with microphone/speacker wasn't fixed; i updated to 4.2.1 and it still didn't work. Today I will call google to RMA it because now (just now) the phone is not working properly but not due to my errors. Thanks to everybody!!!! :laugh:
Click to expand...
Click to collapse
hey can anyone help me i have this error when i flash Stock 5.0.1 Lollipop, Kitkat flashing is working!
Modified boot.img of a rom is required to be flashed on that rom so that it works with TWRP.
Enabling ADB during first boot creates a way out in case your phone bootloops or stuck at MI logo and also hardbricked.
Many people hardbricked their phone while flashing MIUI based roms through TWRP, and they had to test-point to bring their phone back to life, my mod enables adb during boot and so people who used my mod and hardbricked their phone can access adb when their phone is stuck at MI logo or bootlooping and thus revive their phone.
Tools needed:-
1)Notepad++ (google it and download)
2)Android Image Kitchen(AIK) http://forum.xda-developers.com/attachment.php?attachmentid=3638835&d=1454959265
Steps:-
1)Download the required rom and extract its boot.img
2)Copy the boot.img to AIK folder and drag boot.img and drop it on unpackimg.bat
3)Open ramdisk folder and look for default.prop , open them with Notepad++
4)Editing default.prop Note:- This will enable adb at first boot
5)Change
Code:
ro.secure=1 to ro.secure=0
ro.adb.secure=1 to ro.adb.secure=0
ro.debuggable=0 to ro.debuggable=1
persist.sys.usb.config=none to persist.sys.usb.config=adb
delete the line ro.secureboot.devicelock=1 if present
OR (Alternate way)(recommended)
open ramdisk and look for fstab.qcom, open with notepad++ and search for ",verify" (without quotes) and delete it and save.
6)Now execute repackimg.bat, a image-new.img file will be compiled.
7)Flash the image-new.img through TWRP or through fastboot using "Fastboot flash boot image-new.img"
That's all
P.S:- Remember only use Boot.img specific for the miui version you wanna run, boot.img version not matching with MIUI version
will cause the Wifi to stop working.
Press thanks If this helped.:good:
Any queries feel free to ask me.:laugh:
Does the modified boot.img procedure need to be done for every ROM or just for the MIUI ROMs? I want to install the AOSP ROM and later CM 13 but I'm still not sure about the whole flashing process.
Sent from my Redmi Note 3 using XDA-Developers mobile app
SkinCoffin said:
Does the modified boot.img procedure need to be done for every ROM or just for the MIUI ROMs? I want to install the AOSP ROM and later CM 13 but I'm still not sure about the whole flashing process.
Sent from my Redmi Note 3 using XDA-Developers mobile app
Click to expand...
Click to collapse
modified boot.img is only for official MIUI roms, all other roms doesnt need it
Rajdip said:
modified boot.img is only for official MIUI roms, all other roms doesnt need it
Click to expand...
Click to collapse
So if I'm on Miui Official Global ROM 7.2.3 all I have to do is flash TWRP through fastboot, boot into it and flash the new ROM+GApps through it?
SkinCoffin said:
So if I'm on Miui Official Global ROM 7.2.3 all I have to do is flash TWRP through fastboot, boot into it and flash the new ROM+GApps through it?
Click to expand...
Click to collapse
exactly
Rajdip said:
exactly
Click to expand...
Click to collapse
Thank you! I just did it. It has booted and almost over in the "Optimizing apps" window. Thing is, I did forget to wipe system, data and cache before flashing, should I do it again or will it be fine like this?
EDIT: I rebooted the phone into recovery, wiped system, data and cache, flashed the ROM zip and wiped cache and dalvik cache. I booted the phone and it showed the Mi logo, then 4 circles screen flying around (green, red, blue and yellow) and it has been like this for like 5 min now.. Did I do something wrong? I'm starting to worry to be honest.
SkinCoffin said:
Thank you! I just did it. It has booted and almost over in the "Optimizing apps" window. Thing is, I did forget to wipe system, data and cache before flashing, should I do it again or will it be fine like this?
EDIT: I rebooted the phone into recovery, wiped system, data and cache, flashed the ROM zip and wiped cache and dalvik cache. I booted the phone and it showed the Mi logo, then 4 circles screen flying around (green, red, blue and yellow) and it has been like this for like 5 min now.. Did I do something wrong? I'm starting to worry to be honest.
Click to expand...
Click to collapse
it takes time to boot for the first time, did it boot now?
Rajdip said:
it takes time to boot for the first time, did it boot now?
Click to expand...
Click to collapse
Still hasn't booted. It has been on the flying circles screen for around 10 minutes now. Maybe fastboot twrp again and do the process all over again?
SkinCoffin said:
Still hasn't booted. It has been on the flying circles screen for around 10 minutes now. Maybe fastboot twrp again and do the process all over again?
Click to expand...
Click to collapse
Try again, goto TWRP, wipe system,data,cache,dalvik and flash the rom. Now reboot...
Rajdip said:
Try again, goto TWRP, wipe system,data,cache,dalvik and flash the rom. Now reboot...
Click to expand...
Click to collapse
So I shouldn't reinstall TWRP through fastboot?
EDIT: Ok so I restarted the phone and it booted normally into the ROM, everything seems alright. Will check if I have any problem, if I do I'll just reflash it.
SkinCoffin said:
So I shouldn't reinstall TWRP through fastboot?
Click to expand...
Click to collapse
No, first try what I said, dont wipe cache and dalvik after the rom is flashed
Rajdip said:
No, first try what I said, dont wipe cache and dalvik after the rom is flashed
Click to expand...
Click to collapse
Ok so I restarted the phone and it booted normally into the ROM, everything seems alright. Will check if I have any problem, if I do I'll just reflash it.
SkinCoffin said:
Ok so I restarted the phone and it booted normally into the ROM, everything seems alright. Will check if I have any problem, if I do I'll just reflash it.
Click to expand...
Click to collapse
okay
i do exactly like your tutor...i edit boot.img n delete ",verify"
repack than delete original boot.img, than use moded boot.img... but wifi doesn't work...
where my mistake...?
Mayoz said:
i do exactly like your tutor...i edit boot.img n delete ",verify"
repack than delete original boot.img, than use moded boot.img... but wifi doesn't work...
where my mistake...?
Click to expand...
Click to collapse
are you sure you are using the boot.img of the MIUI version you are flashing? there is two 7.2.3.0 version of boot.img one for global and one for china. Anyway try this and see if wifi works, goto TWRP(I hope you've already deleted the emmc_appsboot file), select mount and then tick on mount system as read only. Then flash the rom. This method will replace TWRP with MIUI recovery but your wifi should start working.
Rajdip said:
are you sure you are using the boot.img of the MIUI version you are flashing? there is two 7.2.3.0 version of boot.img one for global and one for china. Anyway try this and see if wifi works, goto TWRP(I hope you've already deleted the emmc_appsboot file), select mount and then tick on mount system as read only. Then flash the rom. This method will replace TWRP with MIUI recovery but your wifi should start working.
Click to expand...
Click to collapse
yes using the boot.img of the MIUI version to flashing...from recovery rom stable 7.2.3.0 china....maybe my mistake i replace emmc_appsboot file from miui forum...not delete "will replace TWRP with MIUI recovery...' still can booting? i already UBL...
Mayoz said:
yes using the boot.img of the MIUI version to flashing...from recovery rom stable 7.2.3.0 china....maybe my mistake i replace emmc_appsboot file from miui forum...not delete "will replace TWRP with MIUI recovery...' still can booting? i already UBL...
Click to expand...
Click to collapse
I didnt get you, can you be more clear?
Do I need to use Windows 64bits to flash TWRP?
Thanks.
pepemonje said:
Do I need to use Windows 64bits to flash TWRP?
Thanks.
Click to expand...
Click to collapse
no need 32bit works
Hello, I've followed a certain tutorial and flashed a fastboot Rom with modified emmc file in attempt to unlock bootloader by force because, even after two weeks of trying, I can't get a confirmation SMS from xiaomi to confirm sending an unlock request. After doing it and flashing TWRP onto my device, I'm still unable to enter recovery. Just shows a picture of device and a disconnected usb cable. I need to flash SuperSU in order to get root access.
Because this device is getting me really confused, please answer a couple of questions for me.
If I flash a recently uploaded global stable ROM 7.2.3.0. and flash TWRP with a modified boot image from this tutorial, will I finally be able to enter recovery and install SuperSU?
Flashing will probably relock my bootloader. Is it possible for me to finally enter TWRP and flash SuperSU after flashing the new boot image?
I've thought that I could enter TWRP just by unlocking the bootloader but it seems that I've missed something. I can't remember last time a phone got me this confused.
My only goal here is being able to enter TWRP and rooting my phone, I gave up on unlocking the bootloader officially because I can't ever get that confirmation SMS.
I appreciate the help!! :fingers-crossed:
I am using a Lenovo a6000 with 1gb ram and 16gb internal, , and I cant find a stock rom link for this variant..can anyone share a link please?
Fallen_Knight said:
I am using a Lenovo a6000 with 1gb ram and 16gb internal, , and I cant find a stock rom link for this variant..can anyone share a link please?
Click to expand...
Click to collapse
I only have the link update from s07 to s010, but dont have full stok rom.
Here the link http://phonedl.ota.lenovomm.com/dls/v6/A6000_S007_160105_16G_TO_A6000_S010_160420_16G_WCF963238D.zip
where can we find full s07 full rom?
Sorry bro i dont know , but why dont u backup your current rom?
bleedreader said:
Sorry bro i dont know , but why dont u backup your current rom?
Click to expand...
Click to collapse
how? without root and twrp
Fallen_Knight said:
how? without root and twrp
Click to expand...
Click to collapse
Yeah, you can actually do that without root. I assume you have knowledge to use fastboot tools.
Download twrp 3.0.2 and put it in fastboot folder on pc.
Now type in "fastboot boot twrpxxx.img"
Your phone will boot into twrp without actually flashing it. Then, select backup and choose "system, data, boot, recovery" and complete backup of your ROM will be created.
sasukay said:
Yeah, you can actually do that without root. I assume you have knowledge to use fastboot tools.
Download twrp 3.0.2 and put it in fastboot folder on pc.
Now type in "fastboot boot twrpxxx.img"
Your phone will boot into twrp without actually flashing it. Then, select backup and choose "system, data, boot, recovery" and complete backup of your ROM will be created.
Click to expand...
Click to collapse
will that replace my stock recovery or its just temporary?
Fallen_Knight said:
will that replace my stock recovery or its just temporary?
Click to expand...
Click to collapse
No it won't replace your stock recovery
sasukay said:
No it won't replace your stock recovery
Click to expand...
Click to collapse
one last qquestion before i sleep..should i back up all partition? or only those default selected?
Fallen_Knight said:
one last qquestion before i sleep..should i back up all partition? or only those default selected?
Click to expand...
Click to collapse
Well, that depends on you. You need to backup only system, boot and recovery, that will give you the clean backup. But, if you would like to revert back with the same settings and apps installed earlier then you might choose to backup data and cache too.
I flashed Lineage Os 15.1 from stock feb. update rooted, it gets stuck in bootanimation and does not go into system, any solution?
U have twrp? Can u boot into it? If yes do a clean flash or use miflash to get back to stock
If u have TWRP installed then like @apexashwin said clean flash with the recommended process if u dont have twrp u can first boot your phone into TWRP for a while from fastboot commands and clean flash rom and if you want to go to stock use Mi Flash Tool data backup will be recommended .
Sry guys
apexashwin said:
U have twrp? Can u boot into it? If yes do a clean flash or use miflash to get back to stock
Click to expand...
Click to collapse
iamlfcfan said:
If u have TWRP installed then like @apexashwin said clean flash with the recommended process if u dont have twrp u can first boot your phone into TWRP for a while from fastboot commands and clean flash rom and if you want to go to stock use Mi Flash Tool data backup will be recommended .
Click to expand...
Click to collapse
Yes, I have TWRP installed, and i have tried with a lot of clean flashes, installing the rom and the steps that you know.
Nothing have worked, and i don't know what else to do.
Nothing works
Sry guys
apexashwin said:
U have twrp? Can u boot into it? If yes do a clean flash or use miflash to get back to stock
Click to expand...
Click to collapse
iamlfcfan said:
If u have TWRP installed then like @apexashwin said clean flash with the recommended process if u dont have twrp u can first boot your phone into TWRP for a while from fastboot commands and clean flash rom and if you want to go to stock use Mi Flash Tool data backup will be recommended .
Click to expand...
Click to collapse
Yes, I have TWRP installed, and i have tried with a lot of clean flashes, installing the rom and the steps that you know.
Nothing have worked, and i don't know what else to do.
Nothing works
AnonyIsRight said:
Yes, I have TWRP installed, and i have tried with a lot of clean flashes, installing the rom and the steps that you know.
Nothing have worked, and i don't know what else to do.
Nothing works
Click to expand...
Click to collapse
Use mi flash tool to clean install your rom then please take backup of ur data
iamlfcfan said:
Use mi flash tool to clean install your rom then please take backup of ur data
Click to expand...
Click to collapse
Also tried with MiFlash, with the flash_all.bat, the flash_all_lock.bat, and all of that. ( in fastboot mode and edl mode, also tried with qfil )
Idc about my personal data, but if what you mean is the phone data... i have formated it a lot of times :/
I'm going to try with "tissot_images_7.8.23_7.1", i hope it works, but i'm thinking that it will give me the same result https://www.youtube.com/watch?v=3YcWsWYQVGQ
I will write over here if i am able to solve it, and if not, i will write too.
Hello, idk if im doing something wrong, but recently, i get enough of custom roms and just wanted to get back to miui, but, every time i flash miui from custom orange fox recovery, it does not feel smooth, feels laggy and sometimes even freeze for couple of seconds, tried several build of miui including latest official, wiped everything, formated data, nothing helped. Can someone help me to get back to working miui? thanks
meezy5 said:
Hello, idk if im doing something wrong, but recently, i get enough of custom roms and just wanted to get back to miui, but, every time i flash miui from custom orange fox recovery, it does not feel smooth, feels laggy and sometimes even freeze for couple of seconds, tried several build of miui including latest official, wiped everything, formated data, nothing helped. Can someone help me to get back to working miui? thanks
Click to expand...
Click to collapse
Why don't you use fastboot , it will work 100% .
Z750z said:
Why don't you use fastboot , it will work 100% .
Click to expand...
Click to collapse
but this method override orange fox recovery?
meezy5 said:
but this method override orange fox recovery?
Click to expand...
Click to collapse
You can flash it again after that, just make a backup in your pc, your data, because fastboot will wipe everything.
Z750z said:
You can flash it again after that, just make a backup in your pc, your data, because fastboot will wipe everything.
Click to expand...
Click to collapse
finally got time to give it a another try, im unable to flash through miflash tool always ended up with could not find file flash_bat error, and yes, i do have fast boot rom, idk
meezy5 said:
finally got time to give it a another try, im unable to flash through miflash tool always ended up with could not find file flash_bat error, and yes, i do have fast boot rom, idk
Click to expand...
Click to collapse
There is another simple way for flashing via fastboot, open the fastboot rom file copy all the files from there ,go to the file of Xiaomi drivers open and paste , than put your phone in fastboot mode and connect it via USB, find the file named " flash all " double click , done .