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.
Related
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 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.
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...
Dear XDA,
I screwed up... I think my device is now soft bricked.... :crying:
It all started good on a sunny saturday. I thought this was a good day to try another custom rom. Namely Codename Phoenix.
My device was already rooted so i started with upgrading my TWRP to the latest Blu_Spark TWRP 3.2.1. After flashing the recovery i continued with the ROM. It all went downhill from there....
The install finished and i booted my device. Knowing this could take a while i got into the shower thinking it would finish when i got back. But when i got back it was still booting. Knowing the first boot can take a while so I let it be. After an hour or so it was still stuck on the google logo and the weather and my mood changed for the worse.
I figured something in the process went wrong and tried to boot into recovery. That worked so I thought 'Cool, let's fix it there'. But the recovery was encrypted so i couldn't get to my data. Normally you put in your pincode and it decrypts your phone. This was not the case.... I couldn't put in my pincode so decrypting was out of the question.
Luckily ADB was still working so I downloaded the original Oxygen OS rom and tried to side-load it... This got stuck on 47% for no reason at all. Phone had 100% battery and didn't time-out..
I was really confused, but I let the device do it's thing and maybe things would work out... I was wrong. Everything was worse. Because i tried installing the original firmware it removed the custom recovery....
So now i have a device with no OS and I can't get into recovery. Luckily there is a unbrick tool for OnePlus 5. Following those steps i got stuck on the part that it does not show in my device-manager.
Currently i'm really grumpy and have no idea how to fix this.
I humbly ask for advice. Is this solvable or do i have a wasted OnePlus 5?
Thanks in advance,
Lennard
can you reboot to bootloader?
if yes, you can flash original or custom recovery...
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
[/COLOR]
len.asdf said:
Dear XDA,
I screwed up... I think my device is now soft bricked.... :crying:
It all started good on a sunny saturday. I thought this was a good day to try another custom rom. Namely Codename Phoenix.
My device was already rooted so i started with upgrading my TWRP to the latest Blu_Spark TWRP 3.2.1. After flashing the recovery i continued with the ROM. It all went downhill from there....
The install finished and i booted my device. Knowing this could take a while i got into the shower thinking it would finish when i got back. But when i got back it was still booting. Knowing the first boot can take a while so I let it be. After an hour or so it was still stuck on the google logo and the weather and my mood changed for the worse.
I figured something in the process went wrong and tried to boot into recovery. That worked so I thought 'Cool, let's fix it there'. But the recovery was encrypted so i couldn't get to my data. Normally you put in your pincode and it decrypts your phone. This was not the case.... I couldn't put in my pincode so decrypting was out of the question.
Luckily ADB was still working so I downloaded the original Oxygen OS rom and tried to side-load it... This got stuck on 47% for no reason at all. Phone had 100% battery and didn't time-out..
I was really confused, but I let the device do it's thing and maybe things would work out... I was wrong. Everything was worse. Because i tried installing the original firmware it removed the custom recovery....
So now i have a device with no OS and I can't get into recovery. Luckily there is a unbrick tool for OnePlus 5. Following those steps i got stuck on the part that it does not show in my device-manager.
Currently i'm really grumpy and have no idea how to fix this.
I humbly ask for advice. Is this solvable or do i have a wasted OnePlus 5?
Thanks in advance,
Lennard
Click to expand...
Click to collapse
Don't worry! Your device is safe. At most, you'll be required to wipe your data.
Try using the official twrp recovery here:
https://twrp.me/oneplus/oneplus5.html
If this doesn't work, let me know.
canteo said:
can you reboot to bootloader?
if yes, you can flash original or custom recovery...
Click to expand...
Click to collapse
I can go into fastboot and managed to install TWRP with the comment below!
Zohair.ul.hasan said:
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
[/COLOR]
Don't worry! Your device is safe. At most, you'll be required to wipe your data.
Try using the official twrp recovery here:
https://twrp.me/oneplus/oneplus5.html
If this doesn't work, let me know.
Click to expand...
Click to collapse
Thanks for these words! That's a big relieve
With your link I managed to install TWRP through fastboot. So now i have a custom recovery. The current problem is that my data is encrypted and I cannot decrypt it. There is no option to fill in a password since there is no OS that requires a password. So it's sort of a neverending cycle . Although fastboot, recovery and sideload should work now.
The thing is, previously I tried installing the original firmware and that failed at 47%. So i'm not sure what to do now.
I tried installing 'codeworkx universal twrp 3.2.1-0 recovery' since he seems to have fixed the encrypt issue. But when I tried sideloading the file it says "Zip file is corrupt!". So no succes there yet.
To be precise, this is the threat for Codeworkx Universal TWRP : https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
And i downloaded and tried installing: twrp-3.2.1-0-universal-codeworkx-cheeseburger.img
I was thinking about downloading the latest Codename Phoenix ROM, but when I try to download the latest release the file is name "Codename-Phoenix-NOS-8.1-oneplus5t-20180303.zip". That implies it's only for the 5t and not for the 5. So that could be my original problem? That i downloaded the wrong ROM?
That aside.
Should I try to get the download link for CNP and download the latest release for the OP5 and install that.
Or
Should i try to install the original firmware. Reset everything and start over from the beginning (unlocking, rooting, etc..)
Thanks again for all the help
len.asdf said:
I can go into fastboot and managed to install TWRP with the comment below!
Thanks for these words! That's a big relieve
With your link I managed to install TWRP through fastboot. So now i have a custom recovery. The current problem is that my data is encrypted and I cannot decrypt it. There is no option to fill in a password since there is no OS that requires a password. So it's sort of a neverending cycle . Although fastboot, recovery and sideload should work now.
The thing is, previously I tried installing the original firmware and that failed at 47%. So i'm not sure what to do now.
I tried installing 'codeworkx universal twrp 3.2.1-0 recovery' since he seems to have fixed the encrypt issue. But when I tried sideloading the file it says "Zip file is corrupt!". So no succes there yet.
To be precise, this is the threat for Codeworkx Universal TWRP : https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
And i downloaded and tried installing: twrp-3.2.1-0-universal-codeworkx-cheeseburger.img
I was thinking about downloading the latest Codename Phoenix ROM, but when I try to download the latest release the file is name "Codename-Phoenix-NOS-8.1-oneplus5t-20180303.zip". That implies it's only for the 5t and not for the 5. So that could be my original problem? That i downloaded the wrong ROM?
That aside.
Should I try to get the download link for CNP and download the latest release for the OP5 and install that.
Or
Should i try to install the original firmware. Reset everything and start over from the beginning (unlocking, rooting, etc..)
Thanks again for all the help
Click to expand...
Click to collapse
Nice to hear that!
To be clear, does the TWRP decrypt you data? When you click install in TWRP, is it a bunch of randomly named files?
I think you should go ahead with installing CNP, you shouldn't have any problems with it now that you've got the correct version.
Good luck!
Zohair.ul.hasan said:
Nice to hear that!
To be clear, does the TWRP decrypt you data? When you click install in TWRP, is it a bunch of randomly named files?
I think you should go ahead with installing CNP, you shouldn't have any problems with it now that you've got the correct version.
Good luck!
Click to expand...
Click to collapse
Yeah it's a bunch of random file names. Like "2TAjnCI8CpHDL38Oh684DuTSgaO".
Alright, i'll let you know if I succeed. Thanks for the help
len.asdf said:
Yeah it's a bunch of random file names. Like "2TAjnCI8CpHDL38Oh684DuTSgaO".
Alright, i'll let you know if I succeed. Thanks for the help
Click to expand...
Click to collapse
Wait! Staying encrypted is a bunch of trouble. I recommend u to follow these steps:
Go to recovery
Select wipe
Select advanced wipe
Clear dalvik and cache
Go back
Select wipe
Click "Format Data"
Type in yes
Go back
Select wipe
Swipe to factory reset
Reboot recovery
Transfer the ROM from PC to phone
Install it
Zohair.ul.hasan said:
Wait! Staying encrypted is a bunch of trouble. I recommend u to follow these steps:
Go to recovery
Select wipe
Select advanced wipe
Clear dalvik and cache
Go back
Select wipe
Click "Format Data"
Type in yes
Go back
Select wipe
Swipe to factory reset
Reboot recovery
Transfer the ROM from PC to phone
Install it
Click to expand...
Click to collapse
Haha thanks! Just in time. Was still downloading the latest CNP .
Whew! Update me after flashing.
Zohair.ul.hasan said:
Whew! Update me after flashing.
Click to expand...
Click to collapse
Hmm, the installation should be a succes. But when i tried to reboot and start up the OS / System it just reboots into TWRP.... ? It's sort of boot looping into recovery.
I tried installing a couple of times with and without wiping dalvik/cache/system.
Could the install file not be complete?
On a side note, my data is not encrypted
len.asdf said:
Hmm, the installation should be a succes. But when i tried to reboot and start up the OS / System it just reboots into TWRP.... ? It's sort of boot looping into recovery.
I tried installing a couple of times with and without wiping dalvik/cache/system.
Could the install file not be complete?
On a side note, my data is not encrypted
Click to expand...
Click to collapse
Did you factory reset by going into wipe>swipe to factory reset?
If not then do that and flash it
Zohair.ul.hasan said:
Did you factory reset by going into wipe>swipe to factory reset?
If not then do that and flash it
Click to expand...
Click to collapse
YES! It work. Many thanks
len.asdf said:
YES! It work. Many thanks
Click to expand...
Click to collapse
Congrats! Please like my replies if you don't mind
Zohair.ul.hasan said:
Congrats! Please like my replies if you don't mind
Click to expand...
Click to collapse
But of course! Already did that. But i'm not sure if it shows or not. Tried clicking multiple times on the thanks button but it doesn't highlight. It should do that right?
len.asdf said:
But of course! Already did that. But i'm not sure if it shows or not. Tried clicking multiple times on the thanks button but it doesn't highlight. It should do that right?
Click to expand...
Click to collapse
Yes it should but that's okay
Zohair.ul.hasan said:
Yes it should but that's okay
Click to expand...
Click to collapse
installed the xda app and there I could give you a 'thanks'
Okay, I want to flash a new rom, then I encounter this problem somehow (It's been a few week, so I forgot it). I can't flash stock rom, I've tried a lot of tutorial and tricks. Help me!
Some of the tutorial that I found on Google suggest me to repair my partition at first, here's what happen when I repair it
i.epvpimg.com/EhrJeab.jpg (Remove space)
andraantariksa said:
Okay, I want to flash a new rom, then I encounter this problem somehow (It's been a few week, so I forgot it). I can't flash stock rom, I've tried a lot of tutorial and tricks. Help me!
Some of the tutorial that I found on Google suggest me to repair my partition at first, here's what happen when I repair it
i.epvpimg.com/EhrJeab.jpg (Remove space)
Click to expand...
Click to collapse
Bro please tell are you able to access recovery ??
AYUSH KUMAR said:
Bro please tell are you able to access recovery ??
Click to expand...
Click to collapse
Yes, I'm still able to boot TWRP, use fastboot and adb
andraantariksa said:
Yes, I'm still able to boot TWRP, use fastboot and adb
Click to expand...
Click to collapse
Reboot to TWRP go to wipe first select system then change file system and select any file system. Then again do this steps abut change your file system to default.
Then do same with data partition
Then flash any ROM
If you need any help contact me at [email protected]
AYUSH KUMAR said:
Reboot to TWRP go to wipe first select system then change file system and select any file system. Then again do this steps abut change your file system to default.
Then do same with data partition
Then flash any ROM
If you need any help contact me at [email protected]
Click to expand...
Click to collapse
bro thanks bt this wont work i have seen abt 1k users have this error
after flashing many custom roms
emmc internel.memory get corrupted
and this is hardware problem phone doesnt have its memory so no r can be flash
and there is no emmc internel memory avaiable in market
all we can do is to change motherboard
gaganmalik said:
bro thanks bt this wont work i have seen abt 1k users have this error
after flashing many custom roms
emmc internel.memory get corrupted
and this is hardware problem phone doesnt have its memory so no r can be flash
and there is no emmc internel memory avaiable in market
all we can do is to change motherboard
Click to expand...
Click to collapse
I too have this problem the service centre cost me 5500 Rupee's but with this method I repaired my partition
try once
AYUSH KUMAR said:
Reboot to TWRP go to wipe first select system then change file system and select any file system. Then again do this steps abut change your file system to default.
Then do same with data partition
Then flash any ROM
If you need any help contact me at [email protected]
Click to expand...
Click to collapse
It's not workin. I've tried it serveral times, changing the /systems to F2FS and change it back to EXT4.
/systems, /cache and /data belong to EXT4 right ?
AYUSH KUMAR said:
Reboot to TWRP go to wipe first select system then change file system and select any file system. Then again do this steps abut change your file system to default.
Then do same with data partition
Then flash any ROM
If you need any help contact me at [email protected]
Click to expand...
Click to collapse
gaganmalik said:
bro thanks bt this wont work i have seen abt 1k users have this error
after flashing many custom roms
emmc internel.memory get corrupted
and this is hardware problem phone doesnt have its memory so no r can be flash
and there is no emmc internel memory avaiable in market
all we can do is to change motherboard
Click to expand...
Click to collapse
Well, I see they sell it for $16 (In Indonesia marketplace). Some of people that my emmc is broken, I don't really know about this, am I should buy it?
AYUSH KUMAR said:
I too have this problem the service centre cost me 5500 Rupee's but with this method I repaired my partition
try once
Click to expand...
Click to collapse
That's really expensive. If that's the only way, I'd rather buy a new phone.
andraantariksa said:
That's really expensive. If that's the only way, I'd rather buy a new phone.
Click to expand...
Click to collapse
Try any latest TWRP
And by the way you have qfil flash able firmware
AYUSH KUMAR said:
Try any latest TWRP
And by the way you have qfil flash able firmware
Click to expand...
Click to collapse
I did, I'm using 3.2.1 TWRP from dev harsh.
I'll try qfil ASAP.
https://forum.xda-developers.com/lenovo-a6000/how-to/guide-hard-brick-lenovo-a6000-t3581892
Okay I can't enter QFil by holding the + volume button, it only make me stuck at boot image and my computer won't detect my phone. Any idea?
andraantariksa said:
Okay I can't enter QFil by holding the + volume button, it only make me stuck at boot image and my computer won't detect my phone. Any idea?
Click to expand...
Click to collapse
Hey copy the partition
Img in adb interface folder and try flashing partition by
Fastboot flash partition partition.img
AYUSH KUMAR said:
Hey copy the partition
Img in adb interface folder and try flashing partition by
Fastboot flash partition partition.img
Click to expand...
Click to collapse
Can you give me a detailed answer? I don't know where's the partition.img
Just google search Kraft-A6000_S061_160727_WCB0C57CA0 and download the zip firmware file, place it on the SD card, boot into twrp, wipe system, data, cache and dalvik cache. Flash the zip. See if this works.
andraantariksa said:
Can you give me a detailed answer? I don't know where's the partition.img
Click to expand...
Click to collapse
Bro have you downloaded qfil flash able firmware ??
---------- Post added at 04:01 PM ---------- Previous post was at 04:00 PM ----------
user0u said:
Just google search Kraft-A6000_S061_160727_WCB0C57CA0 and download the zip firmware file, place it on the SD card, boot into twrp, wipe system, data, cache and dalvik cache. Flash the zip. See if this works.
Click to expand...
Click to collapse
Bro it will not work because you can't mount system or data
If system is not mounting then you can't flash ROM !!
AYUSH KUMAR said:
Bro have you downloaded qfil flash able firmware ??
---------- Post added at 04:01 PM ---------- Previous post was at 04:00 PM ----------
Bro it will not work because you can't mount system or data
If system is not mounting then you can't flash ROM !!
Click to expand...
Click to collapse
You're right, I can't flash anything
I haven't tried QFIL (Well, I've tried it but QFIL not detecting my phone)
andraantariksa said:
You're right, I can't flash anything
I haven't tried QFIL (Well, I've tried it but QFIL not detecting my phone)
Click to expand...
Click to collapse
How are you connecting your phone ??
Is there any file name partition.img in your firmware folder
Check i f qualcomm drivers are installed !!
It seems there have been no improvements, therefore I think this widespread problem shall be the death of many of our devices.
This happened to me once. Since the error was failed to mount partition, I went to mount (in TWRP) and selected all the partitions available there and that solved the issue.