Related
Hi folks,
5 day ago i rootet my tablet 16GB WE and installed Koshu`s CWM step by step like discribed in his threat [http://forum.xda-developers.com/showthread.php?t=1831161]. At the end there was an error message..., i was too quick and made an reboot bevor i could read it.
But i tested if i rooted the tablet succesfully and the superuser-app said that i am root now....
Then i installed the v.0.8.1 Version and everything was fine!
a few days later i got reboots during normal use.
Now i cant boot in the OS, there are bootloops the hole time.
I think that i have not installed the CWM correct...
Any ways to check this with adb commands or something else?
It would be great if someone could help me....
Sorry for my bad english!
Thomas
tpauli said:
Hi folks,
5 day ago i rootet my tablet 16GB WE and installed Koshu`s CWM step by step like discribed in his threat [http://forum.xda-developers.com/showthread.php?t=1831161]. At the end there was an error message..., i was too quick and made an reboot bevor i could read it.
But i tested if i rooted the tablet succesfully and the superuser-app said that i am root now....
Then i installed the v.0.8.1 Version and everything was fine!
a few days later i got reboots during normal use.
Now i cant boot in the OS, there are bootloops the hole time.
I think that i have not installed the CWM correct...
Any ways to check this with adb commands or something else?
It would be great if someone could help me....
Sorry for my bad english!
Thomas
Click to expand...
Click to collapse
You can still boot into CWM? Well you could make a backup of the installed recovery (like shown in the CWM thread) and check if the md5sums are equal to the downloaded image. Btw. linebreaks in the logcat would really help reading it
Koshu said:
You can still boot into CWM? Well you could make a backup of the installed recovery (like shown in the CWM thread) and check if the md5sums are equal to the downloaded image. Btw. linebreaks in the logcat would really help reading it
Click to expand...
Click to collapse
yes i can Boot into CWM, but i cant restore my backup. I tried to install cm10 clean again but after rebooting CWM and booting the OS Android is updating the apps. But i did a full wipe bevor.Thats why i think that the CWM is not in an good state.
i am in the road and maybe i can later check the md5sum.
I can attach an picture from the CWM during trying formating and fixing permissions.
thank you!
Problem solved
tpauli said:
yes i can Boot into CWM, but i cant restore my backup. I tried to install cm10 clean again but after rebooting CWM and booting the OS Android is updating the apps. But i did a full wipe bevor.Thats why i think that the CWM is not in an good state.
i am in the road and maybe i can later check the md5sum.
I can attach an picture from the CWM during trying formating and fixing permissions.
thank you!
Click to expand...
Click to collapse
Koshu helped me! The problem was, that my data partion was read only and my wipes befor and installs was more or less unusefull!
Big thanks to koshu!!!!!
tpauli said:
Koshu helped me! The problem was, that my data partion was read only and my wipes befor and installs was more or less unusefull!
Big thanks to koshu!!!!!
Click to expand...
Click to collapse
Hi. I have the same Problem. Can you tell me how Koshu helped to fix the problem.
the checksum and stuff. thx
florian1985 said:
Hi. I have the same Problem. Can you tell me how Koshu helped to fix the problem.
the checksum and stuff. thx
Click to expand...
Click to collapse
I linked a zip file in the CM10 Thread that formats the data partition: http://forum.xda-developers.com/showthread.php?t=1846044
You can find it in the "addition steps" section. Beware that it will delete all your personal data including the internal sd-card (also nandroid backups if you have stored them on the internal sdcard). So make sure you have EXTERNAL backups if you want to keep some of the data.
I have same problem
After install CM10 ,my TPT cant boot
I turn on My tablet and see loop forever logo : Lenovo ==> CyanogenMod....
Please help me, how to fix it ????
cachlanhuong said:
I have same problem
After install CM10 ,my TPT cant boot
I turn on My tablet and see loop forever logo : Lenovo ==> CyanogenMod....
Please help me, how to fix it ????
Click to expand...
Click to collapse
I have nearly the same problem.
I rooted my TPT a few weeks ago, today I was reading about Cyanogen and decided to install CWM. After some issues with the adb drivers, I managed to install the clockwork recovery.
Now I followed the steps from the cm-thread. I did a nandroid backup and wiped my tablet. After that, I flashed CM10. But all I get is the CyanogenMod logo spinning around.
I tried to go back to my nandroid backup, but it seems broken somehow.
I also tried several several CM-versions and downloaded them several times, without success. But I realised, that the installation procedure of CM was very quick, too quick maybe? Could it be that my clockworkmod isn't installed correctly, because the installation of CM and the nandroid backup won't work.
I hope you guys can help me out. Because I only could find nandroid backups for ROW and US version. I also don´t have adb access anymore.
TPT 16GB 3G WE
Ottilooping said:
I have nearly the same problem.
I rooted my TPT a few weeks ago, today I was reading about Cyanogen and decided to install CWM. After some issues with the adb drivers, I managed to install the clockwork recovery.
Now I followed the steps from the cm-thread. I did a nandroid backup and wiped my tablet. After that, I flashed CM10. But all I get is the CyanogenMod logo spinning around.
I tried to go back to my nandroid backup, but it seems broken somehow.
I also tried several several CM-versions and downloaded them several times, without success. But I realised, that the installation procedure of CM was very quick, too quick maybe? Could it be that my clockworkmod isn't installed correctly, because the installation of CM and the nandroid backup won't work.
I hope you guys can help me out. Because I only could find nandroid backups for ROW and US version. I also don´t have adb access anymore.
TPT 16GB 3G WE
Click to expand...
Click to collapse
Koshu helped me!
I linked a zip file in the CM10 Thread that formats the data partition: http://forum.xda-developers.com/showthread.php?t=1846044
You can find it in the "addition steps" section. Beware that it will delete all your personal data including the internal sd-card (also nandroid backups if you have stored them on the internal sdcard). So make sure you have EXTERNAL backups if you want to keep some of the data.
tpauli said:
Koshu helped me!
I linked a zip file in the CM10 Thread that formats the data partition: http://forum.xda-developers.com/showthread.php?t=1846044
You can find it in the "addition steps" section. Beware that it will delete all your personal data including the internal sd-card (also nandroid backups if you have stored them on the internal sdcard). So make sure you have EXTERNAL backups if you want to keep some of the data.
Click to expand...
Click to collapse
But how can formatting my data partition help? You mean after a format, the installation of cm would work?
And how do I use the .zip, just flashing with cwm?
Ottilooping said:
But how can formatting my data partition help? You mean after a format, the installation of cm would work?
And how do I use the .zip, just flashing with cwm?
Click to expand...
Click to collapse
You have to download the formatdata.zip on your external sd-card.
After that you can boot in the recovery and flash this .please dont juse the cwm! Do you know how to boot into the recovery?
Power on and during that you should drop-down the volume + key a few seconds.
This helped me and others.
Please read in this threat: http://forum.xda-developers.com/showthread.php?t=1831161
tpauli said:
You have to download the formatdata.zip on your external sd-card.
After that you can boot in the recovery and flash this .please dont juse the cwm! Do you know how to boot into the recovery?
Power on and during that you should drop-down the volume + key a few seconds.
This helped me and others.
Please read in this threat: http://forum.xda-developers.com/showthread.php?t=1831161
Click to expand...
Click to collapse
But I have no recovery anymore. The cwm replaced the "normal" recovery.
Ottilooping said:
But I have no recovery anymore. The cwm replaced the "normal" recovery.
Click to expand...
Click to collapse
Send me an photo from your "recovery"...
tpauli said:
Send me an photo from your "recovery"...
Click to expand...
Click to collapse
https://www.dropbox.com/s/xl9fx8rb8bpqgkf/IMG_20130212_110830.jpg
Here is the photo.
I was thinking about 2 possible solutions right now.
1. get another nandroid backup (Problem didnt see any for the 16gb WE version)
2. try no reflash another CWM version or maybe ventana cwm and try again to flash Cyanogen (don't know if its possible to just flash another recovery as an image with the current working recovery)
So what do you guys think?
Ottilooping -
You were running ICS before flashing to CM, right?
da_reeseboy said:
Ottilooping -
You were running ICS before flashing to CM, right?
Click to expand...
Click to collapse
Yes, thats correct.
Ottilooping said:
https://www.dropbox.com/s/xl9fx8rb8bpqgkf/IMG_20130212_110830.jpg
Here is the photo.
I was thinking about 2 possible solutions right now.
1. get another nandroid backup (Problem didnt see any for the 16gb WE version)
2. try no reflash another CWM version or maybe ventana cwm and try again to flash Cyanogen (don't know if its possible to just flash another recovery as an image with the current working recovery)
So what do you guys think?
Click to expand...
Click to collapse
That looks good!
My suggestion: Flash the formatdata.zip and than install the last v0.9.2 from koshu located here: http://forum.xda-developers.com/showthread.php?t=1846044
I was coming from ics too.
Problem solved. CM is running. Thanks for your help, exspecialy to you tpauli.
The formatdata.zip was the key
One last question. I am using the folio keyboard with an european layout (qwertz), but with Cyanogen it is us layout (qwerty). How can I change this?
Hi guys, I've accidentally flashed a p4wifi aokp milestone6 on my nexus S (didn't pay enough attention)
Now my phone boots correctly, but I can't mound sdcard, and this happens on recovery too
Is there anything I can do? I can't flash back any roms
P.S: It seems that I have my old rom installed (aokp jb), that's what the Info says
Flash back the stock Rom buddy it ill help you
shazzy1 said:
Flash back the stock Rom buddy it ill help you
Click to expand...
Click to collapse
But How? I can't copy it
what version of recovery do you use?
Use odin man
I use CWM. I think that I can solve everything if I format the sd, but I really need to access it to save some files first
I use cwm 6.0.1.3 version and has problem mounting sd thats why i asked you. Try to flash a 5 version with fastboot to mount sd.
Sent from my Nexus S using xda app-developers app
fastboot
fastboot can update rom too.
fastboot flash [partition name] [image name]
three partition, system boot radio, needed for rom flashing.
fastboot flash system filename.img
fastboot flash boot boot.img
fastboot flash radio radio.img
Never had any problem with mounting sdcard with cwm, it would be way too coincidental that it stopped working just exactly when I flash a wrong rom.
And I have 5.5.0.4...
In theory, flashing the wrong boot.img could create a missmatch on the mount points. If all else fails you can fastboot in the various partitions directly to correct.
i have this problem too on my brother's gnex.
i currently downloading stock factory image to flash from fastboot.
just try that.
hope we can get back our usb storage.
if you found another way please share.
thanks.
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!
Hey guys question. Ever since yesterday for some reason anything i try to install will not boot. I have tried different roms and cant figure it out. any help would be appreciated. this is my only phone.
What have you tried, what model?
If you used Dirty Santa , I've seen a lot of people able to fix boot issues by following this step in his guide
me2151 said:
*****VERIZON USERS******
It has come to my attention that some users have encountered abnormally long first boot time(over 20 minutes before first time setup)
To resolve this issue:
Boot into bootloader by pulling the battery and reinserting it and holding VOL- and phugging in the phone. then typing:
Code:
fastboot flash boot boot2.img
fastboot reboot
**************
Click to expand...
Click to collapse
TGtheImmortal said:
What have you tried, what model?
If you used Dirty Santa , I've seen a lot of people able to fix boot issues by following this step in his guide
Click to expand...
Click to collapse
I have tried about 4 different roms and completely wiping and installing. the only thing that works is re flashing my stock backup i made after i rooted. I will try flashing boot2. Do roms change boot images when you flash? I am on the verizon verient.
pcwizkid1994 said:
I have tried about 4 different roms and completely wiping and installing. the only thing that works is re flashing my stock backup i made after i rooted. I will try flashing boot2. Do roms change boot images when you flash? I am on the verizon verient.
Click to expand...
Click to collapse
I'm not sure if you should flash the boot if you're on a custom rom. I am no expert so I don't want to make you brick your device.
Full wipe including formatting data when you are reinstalling custom roms?
TGtheImmortal said:
I'm not sure if you should flash the boot if you're on a custom rom. I am no expert so I don't want to make you brick your device.
Full wipe including formatting data when you are reinstalling custom roms?
Click to expand...
Click to collapse
Yes sir.
pcwizkid1994 said:
Yes sir.
Click to expand...
Click to collapse
Are you getting any errors whilst flashing custom roms?
The only thing I can think of right now would be following the steps from step 4 and reinstall and root a stock Verizon rom to see if it fixes your issue.
If that doesn't work someone else will have to come along and suggest some things.
TGtheImmortal said:
Are you getting any errors whilst flashing custom roms?
The only thing I can think of right now would be following the steps from step 4 and reinstall and root a stock Verizon rom to see if it fixes your issue.
If that doesn't work someone else will have to come along and suggest some things.
Click to expand...
Click to collapse
No nothing. Everything is flashing like it should.
Are /system and /data mounted in TWRP under mount before/after you flash a custom rom?
TGtheImmortal said:
Are /system and /data mounted in TWRP under mount before/after you flash a custom rom?
Click to expand...
Click to collapse
Now I am getting a system mount error when I try to back up my stock Rom... Will check when on break at work
TGtheImmortal said:
Are /system and /data mounted in TWRP under mount before/after you flash a custom rom?
Click to expand...
Click to collapse
Cach and data are the only things mounted
pcwizkid1994 said:
Cach and data are the only things mounted
Click to expand...
Click to collapse
/system definitely needs to be mounted before flash and after flash as well, otherwise it cannot override your stock rom.
Are you getting an error while trying to mount it? Or only during backup procedure? I was able to fix some mounting issues by simply rebooting TWRP.
TGtheImmortal said:
/system definitely needs to be mounted before flash and after flash as well, otherwise it cannot override your stock rom.
Are you getting an error while trying to mount it? Or only during backup procedure? I was able to fix some mounting issues by simply rebooting TWRP.
Click to expand...
Click to collapse
Ok so i went back into recovery and the only way I can get system to be cheacked is if I mount it as read only
TGtheImmortal said:
/system definitely needs to be mounted before flash and after flash as well, otherwise it cannot override your stock rom.
Are you getting an error while trying to mount it? Or only during backup procedure? I was able to fix some mounting issues by simply rebooting TWRP.
Click to expand...
Click to collapse
Hey. I emailed you back. Did you get my pm? Thanx
Hi to all
I'm a user of redmi 3s, and recently i'm having problems with my phone and i think it could be due to my mistake as i did the "dd" command on a wrong partition
Now everytime i turn my screen off, phone freezes, no response whatsoever. It can only be booted by holding all 3 buttons for 40 sec
Can anyone please do a full partition backup(without system,data,cache)? Almost lost my job cause of this bug.
Thanks
Jure_aleksic said:
Hi to all
I'm a user of redmi 3s, and recently i'm having problems with my phone and i think it could be due to my mistake as i did the "dd" command on a wrong partition
Now everytime i turn my screen off, phone freezes, no response whatsoever. It can only be booted by holding all 3 buttons for 40 sec
Can anyone please do a full partition backup(without system,data,cache)? Almost lost my job cause of this bug.
Thanks
Click to expand...
Click to collapse
Backup internal memory in PC or.. and flash miui via fastboot and thats it and then flash twrp and custom ROMs flashing via fastboot restores custom cache replaces partition via normal type and everything to normal that's it
Sunny Za said:
Backup internal memory in PC or.. and flash miui via fastboot and thats it and then flash twrp and custom ROMs flashing via fastboot restores custom cache replaces partition via normal type and everything to normal that's it
Click to expand...
Click to collapse
nah, u dont get it bro
i need partitions that are phone specific, like modemst1, or oem partitions
mine are bugged and cant be flashed cuz i dont have them
Why Not You Try Flashing Latest Firmware
Azzkaran said:
Why Not You Try Flashing Latest Firmware
Click to expand...
Click to collapse
because those partitions i need arent bundled with firmware releases
Jure_aleksic said:
because those partitions i need arent bundled with firmware releases
Click to expand...
Click to collapse
Then flash official Fast boot Build Or Full Flash Your Firmware
Azzkaran said:
Then flash official Fast boot Build Or Full Flash Your Firmware
Click to expand...
Click to collapse
dude, have you even read and understand my question? THE PARTITIONS I NEED CANNOT BE FLASHED FROM FASTBOOT ROM PACKAGE AS THEY DONT EXIST IN IT. PERIOD.
Jure_aleksic said:
dude, have you even read and understand my question? THE PARTITIONS I NEED CANNOT BE FLASHED FROM FASTBOOT ROM PACKAGE AS THEY DONT EXIST IN IT. PERIOD.
Click to expand...
Click to collapse
Read My Ans Again I Given You Two Methods
Jure_aleksic said:
dude, have you even read and understand my question? THE PARTITIONS I NEED CANNOT BE FLASHED FROM FASTBOOT ROM PACKAGE AS THEY DONT EXIST IN IT. PERIOD.
Click to expand...
Click to collapse
I had the same issue when I mounted all the partitions in twrp and then did rm -rf *
Just flashed the global stable romin edl mode and all is good
Flash latest miui by fastboot method