I dont usually make threads just for questions and just ask them in the question thread but i think this one deserves a thread as i can't find anybody else who has asked this same question.
Basically, i go into recovery and i wipe everything, i then flash the rom, it will go through the process and will say it is successful, however the rom doesnt boot and when i check the system folder through recovery file manager, it is empty. Which means the rom didnt install. How do i fix this?
Okay if nobody wants to help, can someone link me to a guide which will help me to restore back to stock kitkat. D802.
Can't help you with the flashing process and what's going wrong with the d802 here is guide for going back to stock
http://forum.xda-developers.com/showthread.php?t=2432476
use otg cable and install another rom from usb
Envy-X said:
Okay if nobody wants to help, can someone link me to a guide which will help me to restore back to stock kitkat. D802.
Click to expand...
Click to collapse
no one can help you because you didn't write the following:
1. your device model/variant
2. which rom you're trying to flash and/or which rom you're trying to get back to
3. which twrp version you have
4. everything else you find important and informative for someone to help you
cheers
60nine said:
no one can help you because you didn't write the following:
1. your device model/variant
2. which rom you're trying to flash and/or which rom you're trying to get back to
3. which twrp version you have
4. everything else you find important and informative for someone to help you
cheers
Click to expand...
Click to collapse
The only info i have is d802, cloudy 3.3 to cloudy 2.2, and twrp is 2.8.6.1
Envy-X said:
The only info i have is d802, cloudy 3.3 to cloudy 2.2, and twrp is 2.8.6.1
Click to expand...
Click to collapse
that already makes a difference...
i think i've already seen several posts that describe the same procedure that you want...
here is one of that posts
http://forum.xda-developers.com/showpost.php?p=62372703&postcount=11181
just do a full backup in twrp before you do anything...
60nine said:
that already makes a difference...
i think i've already seen several posts that describe the same procedure that you want...
here is one of that posts
http://forum.xda-developers.com/showpost.php?p=62372703&postcount=11181
just do a full backup in twrp before you do anything...
Click to expand...
Click to collapse
I dont think you understand my problem. No matter which rom i flash, nothing happens. I will go through the process of flashing, twrp will say it has installed successfully, but when i check the system folder, nothing is there. Meaning no rom has been installed.
Envy-X said:
I dont think you understand my problem. No matter which rom i flash, nothing happens. I will go through the process of flashing, twrp will say it has installed successfully, but when i check the system folder, nothing is there. Meaning no rom has been installed.
Click to expand...
Click to collapse
logic tells me you messed up the partitions trying to flash kk over lollipop...
so please try what i posted above...
returning to kk requires flashing that patch which sets up kk partitions again...
60nine said:
logic tells me you messed up the partitions trying to flash kk over lollipop...
so please try what i posted above...
returning to kk requires flashing that patch which sets up kk partitions again...
Click to expand...
Click to collapse
I followed what he did, flashed the return to kitkat patch, then wipe everything except internal, then flash rom but the same thing happens.
To people who may be reading this and not understanding the problem, ill try and explain a little more. When i enter recovery, i can see i have 1.5gb of internal memory left. I wipe everything except internal storage, now i have about 4.5gb left, because system and data has been wiped. Now i flash new rom from storage, it says rom installed successfully, however recovery still shows i have 4.5gb internal storage. Nothing has installed. Understand?
@bender_007 any idea on this?
---------- Post added at 04:13 AM ---------- Previous post was at 04:09 AM ----------
oh, one more question
when you checked system partition (which you say is empty) - did you mount it first? (in recovery)
system shows empty by default in twrp if you don't mount it first...
did you try to reeboot to rom after this last flash? (1st boot might take 10-15 minutes with half of it showing blinking led and lg logo)
btw internal storage is a different partition from system...
rom installs in "system" partition...
internal storage is used for all your data, pictures, music, etc... (like an internal sd card that's built in, not removable)
---------- Post added at 04:29 AM ---------- Previous post was at 04:13 AM ----------
addendum
i've just entered twrp, and mine shows "internal storage (6300mb)" (or around 6400mb)
so it's a max size i think, not available size...
sorry for the confusion (i may have even wrote the wrong thing about partitions), i'm tired, it's very late here...
60nine said:
bender_007 any idea on this?
---------- Post added at 04:13 AM ---------- Previous post was at 04:09 AM ----------
oh, one more question
when you checked system partition (which you say is empty) - did you mount it first? (in recovery)
system shows empty by default in twrp if you don't mount it first...
did you try to reeboot to rom after this last flash? (1st boot might take 10-15 minutes with half of it showing blinking led and lg logo)
btw internal storage is a different partition from system...
rom installs in "system" partition...
internal storage is used for all your data, pictures, music, etc... (like an internal sd card that's built in, not removable)
---------- Post added at 04:29 AM ---------- Previous post was at 04:13 AM ----------
addendum
i've just entered twrp, and mine shows "internal storage (6300mb)" (or around 6400mb)
so it's a max size i think, not available size...
sorry for the confusion (i may have even wrote the wrong thing about partitions), i'm tired, it's very late here...
Click to expand...
Click to collapse
When i said internal storage, i just meant memory all together of the phone.
I mounted system many times before flashing, still nothing and i also rebooted after flash and nothing, stuck ok boot anomation. No rom to start apparently.
Maybe twrp itself isn't working, should I try flashing the latest version from here? http://blastagator.ddns.net/twrp/2-8-7-1.php Will it work? Currently on LP.
You can safely flash it (it surely wont harm your system)
Maybe it's the older twrp that makes a problem (doesn't do any problems to me)
about twrp...
i'm using the version prior to latest and don't have problems (d802, cloudy3.3)
you say you're stuck on boot animation - did you let the phone boot for about 10 minutes? (i've said that the 1st boot takes some 10-15 minutes - half of that time the phone is in LG logo/flashing led state that looks like nothing is happening)
60nine said:
about twrp...
i'm using the version prior to latest and don't have problems (d802, cloudy3.3)
you say you're stuck on boot animation - did you let the phone boot for about 10 minutes? (i've said that the 1st boot takes some 10-15 minutes - half of that time the phone is in LG logo/flashing led state that looks like nothing is happening)
Click to expand...
Click to collapse
I left it over night. Ive updated to the latest twrp and nothing, same problem. TWRP says rom has installed even though nothing has.
Then I would flash a kdz, do a Factory deset. Then root, install twrp and then proceed to ROM flashing.
Poslano sa mog LG-D855 koristeći Tapatalk
bender_007 said:
Then I would flash a kdz, do a Factory deset. Then root, install twrp and then proceed to ROM flashing.
Poslano sa mog LG-D855 koriste?i Tapatalk
Click to expand...
Click to collapse
Does flashing kdz delete internal storage? and what is the difference between d80220d and d80210b?
10 is jellybean, 20 is KitKat. Cse flashing does wipe also the interval. Normal flashing doesn't.
Poslano sa mog LG-D855 koristeći Tapatalk
Thanks both of you for trying to help me.
Related
Sooo... Where to begin? I was previously on the latest Paranoid but decided I just couldn't wait so as soon as the stock 4.3 images were available, I wiped and went to 4.3. Used the updated SuperSU (chainfire's) and restored some apps from Titanium and all was well... Stock, rooted, and moving along. Then I see an amazing boot animation someone made for the N4 so I just had to have it. Downloaded it, rebooted into TWRP and flashed it and BOOM device no longer boots. I tried every which way from Sunday to get it to boot and to no avail it no boot. So I said screw it, I'll just wipe and start over. I formatted cache, flashed bootloader, boot.img, and system.img (didn't think there was any point to reflash radio) and still no boot... I'm stumped. Am I forgetting something blatantly obvious here? I mean I flashed, bootloader, boot image, and system image... I should basically be at a brand new device. I'm really trying not to format user data unless I have to, and I don't see how anything in user data would be preventing me from booting as it really only reads that stuff at started and not necessarily at 'boot' right? I'm hanging at the Google screen and never even make it to the Nexus X animation portion of boot. What am I missing?
itpromike said:
Sooo... Where to begin? I was previously on the latest Paranoid but decided I just couldn't wait so as soon as the stock 4.3 images were available, I wiped and went to 4.3. Used the updated SuperSU (chainfire's) and restored some apps from Titanium and all was well... Stock, rooted, and moving along. Then I see an amazing boot animation someone made for the N4 so I just had to have it. Downloaded it, rebooted into TWRP and flashed it and BOOM device no longer boots. I tried every which way from Sunday to get it to boot and to no avail it no boot. So I said screw it, I'll just wipe and start over. I formatted cache, flashed bootloader, boot.img, and system.img (didn't think there was any point to reflash radio) and still no boot... I'm stumped. Am I forgetting something blatantly obvious here? I mean I flashed, bootloader, boot image, and system image... I should basically be at a brand new device. I'm really trying not to format user data unless I have to, and I don't see how anything in user data would be preventing me from booting as it really only reads that stuff at started and not necessarily at 'boot' right? I'm hanging at the Google screen and never even make it to the Nexus X animation portion of boot. What am I missing?
Click to expand...
Click to collapse
boot animation goes into splash partition doesn't it? Still how many times do you see the splash screen on your device a day when you are not flashing systems?
boot animation goes either into /system/media/ or /data/local/ btw.
simply reflashing your rom without wiping anything would have resolved your issue. you are going to have to wipe data now most likely.
---------- Post added at 10:40 PM ---------- Previous post was at 10:28 PM ----------
did you make a nandroid backup in your recovery?
simms22 said:
boot animation goes either into /system/media/ or /data/local/ btw.
simply reflashing your rom without wiping anything would have resolved your issue. you are going to have to wipe data now most likely.
---------- Post added at 10:40 PM ---------- Previous post was at 10:28 PM ----------
did you make a nandroid backup in your recovery?
Click to expand...
Click to collapse
I didn't make a nandroid but its fine now. I finally decided to wipe the data and it booted. I wasn't actually running a custom ROM at this point though. Just stock and rooted. You think reflashing stock without wiping anything would,d have done the trick?
itpromike said:
I didn't make a nandroid but its fine now. I finally decided to wipe the data and it booted. I wasn't actually running a custom ROM at this point though. Just stock and rooted. You think reflashing stock without wiping anything would,d have done the trick?
Click to expand...
Click to collapse
if the zip puts the bootanimation.zip into /system/media/ then yes(it most likely does, you can look into the zip and see). if it puts the bootanimation.zip into /data/local/ then no, because just reflashing the rom wouldnt clear out that folder. btw, if you ever want a boot animation to stick between flashing roms, put it into /data/local/. you can do this manually, with a root file explorer, without the need to flash anything.
simms22 said:
if the zip puts the bootanimation.zip into /system/media/ then yes(it most likely does, you can look into the zip and see). if it puts the bootanimation.zip into /data/local/ then no, because just reflashing the rom wouldnt clear out that folder. btw, if you ever want a boot animation to stick between flashing roms, put it into /data/local/. you can do this manually, with a root file explorer, without the need to flash anything.
Click to expand...
Click to collapse
Ahhh thanks for the tip mate. Didn't know that. Now it seems I have another problem. My phone seems to think it only has 8GB of storage when it has 16GB... this can't be good. Wonder how I would go about diagnosing and fixing this or maybe I should start another thread?
itpromike said:
Ahhh thanks for the tip mate. Didn't know that. Now it seems I have another problem. My phone seems to think it only has 8GB of storage when it has 16GB... this can't be good. Wonder how I would go about diagnosing and fixing this or maybe I should start another thread?
Click to expand...
Click to collapse
First try wiping the cache and Dalvik cache and reboot. If your phone still sees only 8GB of storage, perform a factory reset and reboot.
Finally, if your phone does not see 16GB of storage, follow the guide at http://forum.xda-developers.com/showthread.php?t=2033692.
I successfully rooted and modded my Note 3 to run CyanogenMod 11-20140916-SNAPSHOT-M10-hlte. Since that time there have been 2 updates (M11 and M12).
I have downloaded and attempted to update both by using ROM Manager as well as the Update feature in the Settings Menu. Whenever I try to do this, I get the phone's opening splash screen along following messages:
RECOVERY BOOTING ...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
The phone then reboots and returns to this screen.
The only thing I can do is pull the battery, reinsert it, then perform the Volume Down + Home + Power reboot then press Volume Down to force the reboot back to normal.
Did I screw up something when I rooted my phone that is preventing the updates from processing, or am I stuck with manual updates from here on out. If that is the case, what do I need to do to make that happen?
Anyone? Anyone? Beuller? Beuller?
I am bumping this in hopes to get an answer. I am getting really sick of the instability and want to get the newest ROM flashed or, if that's not possible, flash the stock ROM back on the phone.
Odin a recovery like twrp after the odin is done shut down the phone . press volume up +power+home to get back in recovery . from here flash the cm ROM.
---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------
Lol and if you don't know what Odin is than you shouldn't be messing with your phone..
Do a clean flash and it will be good...factory reset+wipe cache and dalvik....
gabesir said:
Odin a recovery like twrp after the odin is done shut down the phone . press volume up +power+home to get back in recovery . from here flash the cm ROM.
---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------
Lol and if you don't know what Odin is than you shouldn't be messing with your phone..
Click to expand...
Click to collapse
I am familiar with Odin, but was able to do everything the first time with ROM Manager.
osutuba said:
I am familiar with Odin, but was able to do everything the first time with ROM Manager.
Click to expand...
Click to collapse
so it doesnt boot into recovery at all? the only way to fix it is to odin your recovery again and than flash your rom.
gabesir said:
so it doesnt boot into recovery at all? the only way to fix it is to odin your recovery again and than flash your rom.
Click to expand...
Click to collapse
Yeah, I had to Odin TWRP on there. Now, I just need to figure out which CM build to use, because there's only nightlies for my specific model (T-Mobile), while there are snapshots of the base model.
I'm welcome to trying other ROMS, but CM is what I am most accustomed to.
osutuba said:
Yeah, I had to Odin TWRP on there. Now, I just need to figure out which CM build to use, because there's only nightlies for my specific model (T-Mobile), while there are snapshots of the base model.
I'm welcome to trying other ROMS, but CM is what I am most accustomed to.
Click to expand...
Click to collapse
Awesome man! glad you back in TWRP..
Look for a CM11(most stable) port for your phone and go from there. :highfive:
gabesir said:
Awesome man! glad you back in TWRP..
Look for a CM11(most stable) port for your phone and go from there. :highfive:
Click to expand...
Click to collapse
Well, I have tried several different mods and keep getting the same error in TWRP:
E:Unable to open ZIP file
Error flashing zip <filename.zip>
Updating partition details ...
Ideas/suggestions? I'm comfortable enough with Odin now to the point that I can flash a ROM that way, if necessary.
rayman95 said:
Do a clean flash and it will be good...factory reset+wipe cache and dalvik....
Click to expand...
Click to collapse
Do read before you post. OP couldn't even access his recovery.
osutuba said:
Well, I have tried several different mods and keep getting the same error in TWRP:
E:Unable to open ZIP file
Error flashing zip <filename.zip>
Updating partition details ...
Ideas/suggestions? I'm comfortable enough with Odin now to the point that I can flash a ROM that way, if necessary.
Click to expand...
Click to collapse
First of all, why is it called filename.zip? Put the CM .zip file to internal or external SD card (latter preferred if you have one) and then flash it directly from there after wiping (I wipe system, data, cache, dalvik cache).
Someguyfromhell said:
Do read before you post. OP couldn't even access his recovery.
First of all, why is it called filename.zip? Put the CM .zip file to internal or external SD card (latter preferred if you have one) and then flash it directly from there after wiping (I wipe system, data, cache, dalvik cache).
Click to expand...
Click to collapse
why do you propose him to flash CM11 if he can't get recovery mode????
Someguyfromhell said:
First of all, why is it called filename.zip?
Click to expand...
Click to collapse
I used <filename.zip> as a generic marker, as I have tried several different ROMs with the same outcome. As I stated in a previous reply, I was able to flash TWRP using Odin without issue. I have even re-flashed it several times since getting the aforementioned error, thinking something wasn't working.
Someguyfromhell said:
Put the CM .zip file to internal or external SD card (latter preferred if you have one) and then flash it directly from there after wiping (I wipe system, data, cache, dalvik cache).
Click to expand...
Click to collapse
I don't have an external SD Card on hand at the moment, otherwise I would try that.
rayman95 said:
why do you propose him to flash CM11 if he can't get recovery mode????
Click to expand...
Click to collapse
Please keep an eye on the topic. You can see that he solved the issue (after your and before my post) with accessing recovery, thereby we have moved on to solve his next problem - flashing the ROM.
osutuba said:
I used <filename.zip> as a generic marker, as I have tried several different ROMs with the same outcome. As I stated in a previous reply, I was able to flash TWRP using Odin without issue. I have even re-flashed it several times since getting the aforementioned error, thinking something wasn't working.
I don't have an external SD Card on hand at the moment, otherwise I would try that.
Click to expand...
Click to collapse
Re-download the .zip file and place it on the internal storage then. Do MD5 check also before moving, seems like the zip file was corrupted (faulty download?) when you tried to flash it.
I saw the cm website had a new cm13 nightly for angler, so I decided to try it out, so I downloaded it and gapps, and rebooted into twrp, then I wiped everything besides for internal storage and then I proceeded to Install cm, it took a few minutes, and then when it was done I rebooted. The first sign of something weird was that after the regular your device can't be checked for corruption message it went black and then said that my device is corrupt in red letters, then it started the cm boot animation, I waited about 5 minutes and nothing happened so I rebooted into recovery and it asked me for an encryption password... My device was not previously encrypted and I didn't require a password to Install cm, so I tried wiping everything besides for internal storage, and then I was about to flash again, but non of my files were there so I had nothing to flash.... So I rebooted into my bootloader and fastbooted stock and now I'm on stock, but all my files and backups are gone. I guess that's why it's good to have an external sd, because that never got wiped by installing a rom before, and if I would have one, I would have all my pictures, music, and app backups. But now I have to start from scratch all because I tried a new build cyanogen mod
This is your fault not CM. You said you were on a rom that was unencrypted. CM roms default to encrypt so that is how you lost your data. You should have done research before you installed as CM with the start of LP ships encrypted.
CM ROMs usually encrypt the data partition which may explain your loss?
coldconfession13 said:
This is your fault not CM. You said you were on a rom that was unencrypted. CM roms default to encrypt so that is how you lost your data. You should have done research before you installed as CM with the start of LP ships encrypted.
Click to expand...
Click to collapse
So if I'm unencrypted and I Install an encrypted rom I lose the data partition?
Yes, you would have had to flash cm13 then a kernel that supports unencrypted storage then boot
coldconfession13 said:
Yes, you would have had to flash cm13 then a kernel that supports unencrypted storage then boot
Click to expand...
Click to collapse
Well I always flashed elementalX after flashing any roms but Its for aosp... I never had a nexus before and I guess I didn't know enough about encryption.
Yea it's one of those trial and error kind of deals. It sucks. That corruption error is because you need to flash the vendor.img file in fastboot. I believe we have a twrp one available as well but that link is buried in the chroma rom thread.
---------- Post added at 10:05 AM ---------- Previous post was at 10:01 AM ----------
https://androidfilehost.com/?fid=24269982086996393
You can flash that in twrp to get that corruption. But that could be the unlocked bootloader message which nobody has found to get rid of yet
coldconfession13 said:
Yea it's one of those trial and error kind of deals. It sucks. That corruption error is because you need to flash the vendor.img file in fastboot. I believe we have a twrp one available as well but that link is buried in the chroma rom thread.
---------- Post added at 10:05 AM ---------- Previous post was at 10:01 AM ----------
https://androidfilehost.com/?fid=24269982086996393
You can flash that in twrp to get that corruption. But that could be the unlocked bootloader message which nobody has found to get rid of yet
Click to expand...
Click to collapse
So its different than the stock vendor.img that come with the factory build?
I saw two messages one about that it can't check for corruption and that I always see, and another that my device is corrupted and that was a first.
I think that second one is also kernel related. I remember Leankernel saying the corruption and then he fixed it and now its just the bootloader one.
coldconfession13 said:
I think that second one is also kernel related. I remember Leankernel saying the corruption and then he fixed it and now its just the bootloader one.
Click to expand...
Click to collapse
What I mean is that I had already flashed the vendor.img that came with the mdb08m build using fastboot
Then I believe you are experiencing that kernel error. They have to change some settings in the default kernel in cm13 to get rid of that error. If you flash leankernel it should get rid of that one.
aryehzev said:
.....[cut] So I rebooted into my bootloader and fastbooted stock and now I'm on stock, but all my files and backups are gone.
Click to expand...
Click to collapse
If you used the flash-all helper script to reinstall stock, it will wipe all internal storage (if you look at the script contents, that's what the "-w" does).
I know it's a bit late now but I'd recommend always copying backups off the device when making major changes.
sam3000 said:
If you used the flash-all helper script to reinstall stock, it will wipe all internal storage (if you look at the script contents, that's what the "-w" does).
I know it's a bit late now but I'd recommend always copying backups off the device when making major changes.
Click to expand...
Click to collapse
I did not use flashall I flash everything individually. (system,boot,cache,vendor)
Guys I'm a liitle late to the party on this convo but I'm in a similar but different situation. I installed the latest temasek 11/29 ROM. Was previously on purenexus. After installing the ROM and gapps I restarted the system and got a message that my phone can't be trusted. The phone then went on to encrypt itself. Booted fine so I just wanted to see if I could still access twrp and if all my internal storage was OK. Good on both accounts. So my question is do I have to decrypt before switching ROMs say back to purenex or can I boot to recovery and just wipe cache,dalvik, sys and data and flash whatever rom I want?
Sent from my Nexus 6P using Tapatalk
jeff5347 said:
Guys I'm a liitle late to the party on this convo but I'm in a similar but different situation. I installed the latest temasek 11/29 ROM. Was previously on purenexus. After installing the ROM and gapps I restarted the system and got a message that my phone can't be trusted. The phone then went on to encrypt itself. Booted fine so I just wanted to see if I could still access twrp and if all my internal storage was OK. Good on both accounts. So my question is do I have to decrypt before switching ROMs say back to purenex or can I boot to recovery and just wipe cache,dalvik, sys and data and flash whatever rom I want?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No you never have to unencrypt
How are you guys even booting? I keep getting stuck at the Google logo on reboot.
akellar said:
No you never have to unencrypt
Click to expand...
Click to collapse
That I didn't know.
Sent from my Nexus 6P using Tapatalk
Dear all,
I stupidly bricked my Mi Note 2 by doing OTA with TWRP installed (at least I think that is the reason) - although I have done this once with success, but at the second time, the phone won't boot anymore.
- In TWRP, it says that the internal storage is encrypted and prompts me for code
- In TWRP the storage cannot be mounted (none of the partitions can be mounted)
- Tried to flash stock ROM or stock recovery in fastboot mode, seems like the internal storage cannot be accessed either
- With Mi Assistant, still no lock
It seems that the internal storage is totally corrupted...
What can I do without going to service (luckily I'm in China right now...)? Perhaps ADB sideload stock ROM would work?
Thanks!
Delete data partition an try reboot
Can't. Got some error message - see attached.
Sense like that the internal storage can't be found at all...
Also tried to side load DEV rom via adb, but got the attached error.
No clue how to proceed...
1. Format your data partition, and then reboot TWRP. This will decrypt your phone.
2.After entering TWRP, wipe all partition and then reboot TWRP
3.Copy your ROM file into your phone, and then flash ROM
Kris Chen said:
1. Format your data partition, and then reboot TWRP. This will decrypt your phone.
2.After entering TWRP, wipe all partition and then reboot TWRP
3.Copy your ROM file into your phone, and then flash ROM
Click to expand...
Click to collapse
Hi, I have assumed this as well, however didn't figure out a way to format the data partition. In my previous screenshot I showed the error ("unable to mount" or "no such device") when trying to delete the data partition.
Do you have a more detailed instruction?
Thanks!
Here you are.
See that "Format Data" ?
CrisperNeO said:
Hi, I have assumed this as well, however didn't figure out a way to format the data partition. In my previous screenshot I showed the error ("unable to mount" or "no such device") when trying to delete the data partition.
Do you have a more detailed instruction?
Thanks!
Click to expand...
Click to collapse
Kris Chen said:
Here you are.
See that "Format Data" ?
Click to expand...
Click to collapse
That's exactly what I have done... However: "unable to mound" or "no such device", it did not work
Which one of TWRP version do you use now ?
---------- Post added at 09:51 PM ---------- Previous post was at 09:46 PM ----------
https://mega.nz/#!NBwyjKrK!XELWAAwehtKnXgXOge_y16kEP0Uqscv_5LVx-YqTzcc
I use this version !
Kris Chen said:
Which one of TWRP version do you use now ?
---------- Post added at 09:51 PM ---------- Previous post was at 09:46 PM ----------
https://mega.nz/#!NBwyjKrK!XELWAAwehtKnXgXOge_y16kEP0Uqscv_5LVx-YqTzcc
I use this version !
Click to expand...
Click to collapse
3.0.2-X by BY~XM
Do you want to switch mostly updated one and try again?
Sometime it may come from outdated version of TWRP.
CrisperNeO said:
3.0.2-X by BY~XM
Click to expand...
Click to collapse
Kris Chen said:
Do you want to switch mostly updated one and try again?
Sometime it may come from outdated version of TWRP.
Click to expand...
Click to collapse
Actually I cannot flash any recovery now: FAILED (remote: flash write failure)
Download fastboot rom and flash it with miflash tool.
Can you enter fastboot mode ? If yes, then you can do (1)as dtsun said that; (2)flash the new version of TWRP(fastboot flash recovery xxxx.img ===> "XXXX.img" means the whole file name of TWRP image file), rebooting to TWRP again and then flash your recovery ROM.
dtosun said:
Download fastboot rom and flash it with miflash tool.
Click to expand...
Click to collapse
tried and also no luck, internal storage seems like not accessible
Kris Chen said:
Can you enter fastboot mode ? If yes, then you can do (1)as dtsun said that; (2)flash the new version of TWRP(fastboot flash recovery xxxx.img ===> "XXXX.img" means the whole file name of TWRP image file), rebooting to TWRP again and then flash your recovery ROM.
Click to expand...
Click to collapse
I can enter fastboot, but like said before, cannot flash any recovery
Sorry for that. It's indeed that you have bricked your phone
Now you need to find local mobile store to repair it, or prepare for another phone - Mi 6 ~
dtosun said:
Download fastboot rom and flash it with miflash tool.
Click to expand...
Click to collapse
Do this.
What error are you getting when trying to flash MIUI fastboot rom?
I have had this problem before on my redmi note 3, although the cause was from flashing TWRP not OTA.
I tried everything I could think of to try fix it, in the end flashing fastboot rom and clean all and lock with mi flash tool was the only way.
You'll need to use mi unlock to unlock the phone again but that is easy if you have done it before.
Did you use official way to unlock bootloader?
Reply to all above:
I unlocked the phone in the official way;
Miflash didn't work, because the internal storage is not accessible.
So lessons learned: never do OTA update if you have a custom recovery installed.
But:
Latest report:
Sent back to Xiaomi (luckily I'm in China right now) and Xiaomi was awesome, the engineer replaced the main board and it costed me nothing...
If you guys help me to go back successfully to stock, I'll make a guide to explain the process, maybe for all 3 models. I just need help on this one
I have an A2017G
So this is my fourth time trying to get back to stock. the first one resulted on a DFU brick. The second one was through MiFlash and the system had random reboots. The third, I flashed tron1's A2017G B04 Bootstack and a DrakenFX flashable zip (for the U, just wanted to try) and TWRP said that there was no system which turned out to be true... i had wiped system, data and caches before, but it seemingly installed okay...
I also tried to use MiFlash again and get B10, but it started to throw an error out of the blue (the specified cast is not valid, or something along the lines). I used it at least 4 times before.
So what zip should I use? I never tried flashing one of those update zips (I have full official B10 on the sdcard) but I believe they won't work. Please tell me if they do work...
again, if i manage to get SAFELY to stock and AVOID DFU I'll make a nice guide so that we stop asking. Most custom roms are flawed, for ex. Lineage has bad compatibility, Pure Nexus (the one I'm using now) has extreme, Galaxy Y grade lag, and RR simply works worse than stock (it's probably the best one of the bunch though).
i am in in the process of going back to stock(A2017), will let you know.
---------- Post added at 04:07 AM ---------- Previous post was at 03:14 AM ----------
I have followed all the tutorials but its failed and now i cant even install any zip in twrp , cant mount internal storage.. deive or resource busy and cant restore my LOS based rom.. same errors..
satish.yarramsetti said:
i am in in the process of going back to stock(A2017), will let you know.
---------- Post added at 04:07 AM ---------- Previous post was at 03:14 AM ----------
I have followed all the tutorials but its failed and now i cant even install any zip in twrp , cant mount internal storage.. deive or resource busy and cant restore my LOS based rom.. same errors..
Click to expand...
Click to collapse
well you can get to EDL and flash a full A2017 EDL package. I can't, not on this computer
Does EDL work?
Choose an username... said:
well you can get to EDL and flash a full A2017 EDL package. I can't, not on this computer
Click to expand...
Click to collapse
TWRP doesnt mount /Data
---------- Post added at 04:19 AM ---------- Previous post was at 04:16 AM ----------
Choose an username... said:
well you can get to EDL and flash a full A2017 EDL package. I can't, not on this computer
Click to expand...
Click to collapse
I tried Format system option in Wipe Menu, and that caused this ' Cnat mount /Data ' issue.
satish.yarramsetti said:
TWRP doesnt mount /Data
---------- Post added at 04:19 AM ---------- Previous post was at 04:16 AM ----------
I tried Format system option in Wipe Menu, and that caused this ' Cnat mount /Data ' issue.
Click to expand...
Click to collapse
well I meant use MiFlash, but I don't know if you should even think about getting out of TWRP in this state. No idea
Hey how to boot EDL mode
Choose an username... said:
well I meant use MiFlash, but I don't know if you should even think about getting out of TWRP in this state. No idea
Click to expand...
Click to collapse
Please help, how to boot EDL mode? please help i forgot
satish.yarramsetti said:
Please help, how to boot EDL mode? please help i forgot
Click to expand...
Click to collapse
I don't think you should when having TWRP loaded on your RAM and your system probably not there...
My DFU brick was just because of that
but if you insist, turn your phone off and hold the two volume keys, then connect the USB cable (it has to be connected to the PC obviously)
Still had TWRP
Choose an username... said:
I don't think you should when having TWRP loaded on your RAM and your system probably not there...
My DFU brick was just because of that
but if you insist, turn your phone off and hold the two volume keys, then connect the USB cable (it has to be connected to the PC obviously)
Click to expand...
Click to collapse
Man, still i had twrp and i can access internal storage. let me see if i can restore my rom
---------- Post added at 04:37 AM ---------- Previous post was at 04:34 AM ----------
satish.yarramsetti said:
Man, still i had twrp and i can access internal storage. let me see if i can restore my rom
Click to expand...
Click to collapse
Thanks God! Restore is in progress and if it works i wont try to get back to stock until someone find a sure shot method for that... waiting.. waiting..
satish.yarramsetti said:
Man, still i had twrp and i can access internal storage. let me see if i can restore my rom
---------- Post added at 04:37 AM ---------- Previous post was at 04:34 AM ----------
Thanks God! Restore is in progress and if it works i wont try to get back to stock until someone find a sure shot method for that... waiting.. waiting..
Click to expand...
Click to collapse
MiFlash is that method. It only has to be in the mood to work...
restore failed
Choose an username... said:
MiFlash is that method. It only has to be in the mood to work...
Click to expand...
Click to collapse
restore failed "extracttarfork() process ended with error=255"
satish.yarramsetti said:
restore failed "extracttarfork() process ended with error=255"
Click to expand...
Click to collapse
i had that error when I was backing up. Try to wipe all the partitions but internal (not necessarily format, go to settings and tick use rm -rf) maybe it works. if not try formatting with ext4
lol deleted
No, doesnt help
Choose an username... said:
lol deleted
Click to expand...
Click to collapse
No its doesnt help wiping all partitions.. same error
Mount -> Unmount /data
Wipe -> Format Data (the actual button next to 'Advanced Wipe')-> type 'yes' -> Reboot Recovery
Wipe -> Advanced Wipe -> Tick 'Data' -> Change File System -> EXT4
Try to mount /data
This has worked for me going from an LOS system back to Stock.
satish.yarramsetti said:
No its doesnt help wiping all partitions.. same error
Click to expand...
Click to collapse
QuantumFluxx said:
Mount -> Unmount /data
Wipe -> Format Data (the actual button next to 'Advanced Wipe')-> type 'yes' -> Reboot Recovery
Wipe -> Advanced Wipe -> Tick 'Data' -> Change File System -> EXT4
Try to mount /data
This has worked for me going from an LOS system back to Stock.
Click to expand...
Click to collapse
It might have worked post restart. I am unable mount internal storage or fash but Post restrat it worked
QuantumFluxx said:
This has worked for me going from an LOS system back to Stock.
Click to expand...
Click to collapse
could you tell us how you did to get to stock? What's your device, A2017G? What did you flash?
That's pretty much everything I want to know
A2017U from LOS to stock using the files on https://forum.xda-developers.com/showpost.php?p=68873482
The only reason I mentioned it when I have the United States model is because I have ran into a problem on multiple devices going from CyanogenMod to any sort of AOSP-based ROM without clicking that format data button. The first time I ran into the problem comma I could not mount my data partition.
I advised @satish.yarramsetti about this here. @satish.yarramsetti, can you confirm that the ZIP I linked you to in the other thread is the one you flashed and is booting?
Choose an username... said:
could you tell us how you did to get to stock? What's your device, A2017G? What did you flash?
That's pretty much everything I want to know
Click to expand...
Click to collapse
QuantumFluxx said:
A2017U from LOS to stock using the files on https://forum.xda-developers.com/showpost.php?p=68873482
The only reason I mentioned it when I have the United States model is because I have ran into a problem on multiple devices going from CyanogenMod to any sort of AOSP-based ROM without clicking that format data button. The first time I ran into the problem comma I could not mount my data partition.
I advised @satish.yarramsetti about this here. @satish.yarramsetti, can you confirm that the ZIP I linked you to in the other thread is the one you flashed and is booting?
Click to expand...
Click to collapse
I am Nuclear Rom(LOS Based) and tried to go back to stock. I have followed all tutorials but when i try to reboot, TWRP warned me that there is no OS. So i didn't reboot as it might remove TWRP ( it might have booted but not sure) ( i also flashed NO verify zip) , so i thought of formatting in wipe menu which caused a lot of problems like cant mount data & device busy errors . I tried to flash N boot loader and mod but every FLASH is getting failed. So i decided to restart and luckily i have TWRP and no os and my nandroid back up niether worked.
Finally i flashed Clean LOS.
Understood. I have received that same warning in the past after flashing stock. At any rate, if there's no OS installed, there's nothing to overwrite TWRP. The phone would just sit at the ZTE logo and you would have to hold Vol Up+Power to get back into TWRP. If you decided to try again, at least you know you can restore LOS if it doesn't work... Good luck.
satish.yarramsetti said:
I am Nuclear Rom(LOS Based) and tried to go back to stock. I have followed all tutorials but when i try to reboot, TWRP warned me that there is no OS. So i didn't reboot as it might remove TWRP ( it might have booted but not sure) ( i also flashed NO verify zip) , so i thought of formatting in wipe menu which caused a lot of problems like cant mount data & device busy errors . I tried to flash N boot loader and mod but every FLASH is getting failed. So i decided to restart and luckily i have TWRP and no os and my nandroid back up niether worked.
Finally i flashed Clean LOS.
Click to expand...
Click to collapse
QuantumFluxx said:
Understood. I have received that same warning in the past after flashing stock. At any rate, if there's no OS installed, there's nothing to overwrite TWRP. The phone would just sit at the ZTE logo and you would have to hold Vol Up+Power to get back into TWRP. If you decided to try again, at least you know you can restore LOS if it doesn't work... Good luck.
Click to expand...
Click to collapse
The restore is also not working i got some error 255 ... Strange thing is i got a warning like no OS after installing LOS but i booted.