Looks like some people are breaking stuffs while trying to root and/or unlock bootloader.
The following is a TWRP backup of my clean system on the 19s ROM after the bootloader unlocking. Since we don't have a full stock image available, I think this is the only way we can go back to complete stock. This includes the stock recovery, bootloader and system. The data partition was formatted. So, restoring data from this will basically format your data partition.
https://drive.google.com/file/d/0B5xyvHc4wgEVWHFKMWZqLWEyTTg/view?usp=sharing
I have had no problem restoring my device to stock using this, but I take no responsibility what-so-ever. I hope you know what you are doing. If you don't know how to use this, this is probably not for you.
It's working!! I flash it on my Chinese phone
X720 everything's works perfect now I'm lost of all the Chinese crap.
Good work! When you update the phone please post again a backup ok?
Big thanks
Sent from my SM-G935F using XDA-Developers mobile app
So if I restore this in TWRP and then relock the bootloader via fastboot I am back to completely stock 19s?
Sent from my LEX727 using Tapatalk
mumboender said:
So if I restore this in TWRP and then relock the bootloader via fastboot I am back to completely stock 19s?
Click to expand...
Click to collapse
yes
That is awesome. I am on the fence on whether to return mine. At least this gives me the option since I unlocked and rooted it.
Sent from my LEX727 using Tapatalk
Quick question. Could I make a TWRP backup of my system with the x720 bootloader and the TWRP recovery and replace your boot.emmc.win, boot.emmc.win.md5, recovery.emmc.win , recovery.emmc.win.md5 with the ones from my backup to have an unlocked/TWRP/stock backup file?
Speaking of which, how did you make this backup? I guessing with the following steps:
- From a setup phone
- flip unlock switch
- boot botloader
- unlock bootloader
- boot TWRP
- wipe data
- create backup
??
Also it sounds like there is a way to make an update.zip from a backup. Who's brave enough to try this...
http://www.droidviews.com/create-flashable-zip-cwmtwrp-backup/
The problem I see with this method is there are multiple system.ext4.win files (system.ext4.win000, system.ext4.win001, system.ext4.win002).
Everythings works fine the only thing that is Missing is dual Sim option but i dont use that anyway
Sent from my LEX727 using XDA-Developers mobile app
mumboender said:
So if I restore this in TWRP and then relock the bootloader via fastboot I am back to completely stock 19s?
Sent from my LEX727 using Tapatalk
Click to expand...
Click to collapse
Not likely. Depends on how you unlocked. If you flashed the chinese ROM and only restore a TWRP backup, you aren't getting back the stock bootloader (you'll have the chinese one) nor other system firmware versions meant for the chinese market. There's a chance you will have mismatched firmwares that cause an upgrade failure.
Your phone isn't fully back to a US variant. It just looks like it is from the system.
I didn't use the Chinese ROM, unlocked using TWRP on the temporary unlocked bootloader.
Sent from my LEX727 using Tapatalk
when you performed this backup, was TWRP mounted as read/write? if so, we won't be able to install the official OTA updates
i ran into this problem on the S3 last night. i booted into TWRP, but chose to mount TWRP as read/write, made a full backup, then tried to install the OTA, and learned that OTA's won't install if they've detected that the /system partition has ever been mounted as read/write. it's basically the first option that shows up when you boot TWRP after hitting cancel on the decryption.
i foolishly mounted my Pro3 as read/write only as well, so i believe we won't be able to install future updates until we get full TWRP system images with read only mounted. hopefully someone can do that here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dajumper said:
Everythings works fine the only thing that is Missing is dual Sim option but i dont use that anyway
Sent from my LEX727 using XDA-Developers mobile app
Click to expand...
Click to collapse
A question please : Have you preserved your original IMEI after x727 TWRP backup flashing ?
Flashed it on my x720. Awesome, .19s is much faster then .18s. And it looks way better for the x727 instead of the ugly x720.
The x727 doesnt have the option for multi-sim?
Can anyone tell me does Android Pay work with this? It doesn't work on any of the X720 roms available but from what I understand the 727 was locked to make it so that Android Pay would work.
Can anybody tell me what is the difference between this rom and the x720 ones?
And also , will it work on X720? and are Leeco apps translated in it? If someone could make some screenshots it'll be great
Flashed it on my X720 too, but Sim Card not recognized...
Gesendet von meinem LEX720 mit Tapatalk
elkatronix said:
Flashed it on my X720 too, but Sim Card not recognized...
Gesendet von meinem LEX720 mit Tapatalk
Click to expand...
Click to collapse
Same problem here , too.
Also restore the boot, not only system. :> "For the x720"
secXces_debaki said:
Also restore the boot, not only system. :> "For the x720"
Click to expand...
Click to collapse
I try it but the same problem...Sim Card not recognized ...do you put Sim Card on the first or second slot?
Sent from my LEX720 using Tapatalk
The x727 only recognize the first Sim. Whyever?
I have it on the first slot.
Restored over twrp, system and boot, wipe everything beside internal storage, and restored it again.
Why 2 times? Just to be sure. ^^
The U.S model is a single-SIM device, so that might explain why the software is missing supports for the second SIM card.
Related
Today, I downloaded a Xperia S Lockscreen Mod and noticed that it caused a boot loop once flashed. To save this, I downloaded the fix permissions script, but still no change. Later on, I decided to back up the ROM, and then proceeded to flash 4.0.4 with Flashtool. Halfway flashing, I looked into the backup folder I created with CWM, only to find out it did not backup my entire ROM, but only mere parts of it. (All of my Nandroid Backups were about 1GB, but this one was 200-ish MB) Since it was too late, I just proceeded. For some random reason, I decided to flash 4.0.3, and now my Sony cannot even boot. (Just has this Warning symbol once past Sony screen)
Is there any way to draw out the phone data that is still in the phone? I do not want to lose all of my Contacts, SMS, Call Data etc.
PLEASE REPLY ASAP AND THANK IN ADVANCE!
YoBob said:
Today, I downloaded a Xperia S Lockscreen Mod and noticed that it caused a boot loop once flashed. To save this, I downloaded the fix permissions script, but still no change. Later on, I decided to back up the ROM, and then proceeded to flash 4.0.4 with Flashtool. Halfway flashing, I looked into the backup folder I created with CWM, only to find out it did not backup my entire ROM, but only mere parts of it. (All of my Nandroid Backups were about 1GB, but this one was 200-ish MB) Since it was too late, I just proceeded. For some random reason, I decided to flash 4.0.3, and now my Sony cannot even boot. (Just has this Warning symbol once past Sony screen)
Is there any way to draw out the phone data that is still in the phone? I do not want to lose all of my Contacts, SMS, Call Data etc.
PLEASE REPLY ASAP AND THANK IN ADVANCE!
Click to expand...
Click to collapse
Ok, firstly(and obviously) do not delete your backups as they contain your precious data.
You can use either SEUS or Flashtool to help you fix your phone.
Flashtool: Flash .ftf file
SEUS: Needs Locked BL, Stock Kernel for it to work
After you flash to stock Kernal and Firmware, you can root, unlock BL, flash CWM Kernel and Restore your backups from it.
Hope this helps
popthosegaskets said:
Ok, firstly(and obviously) do not delete your backups as they contain your precious data.
You can use either SEUS or Flashtool to help you fix your phone.
Flashtool: Flash .ftf file
SEUS: Needs Locked BL, Stock Kernel for it to work
After you flash to stock Kernal and Firmware, you can root, unlock BL, flash CWM Kernel and Restore your backups from it.
Hope this helps
Click to expand...
Click to collapse
Can I root and flash CWM when bricked? And also, the backup I made in the process wasn't done properly in the way that it did not backup everything, maybe because my SD Card was already running out of space. Im not sure how much it backed up, nor do I want to take the risk of wiping data prior to flashing.
Is there any other way of backing up my data when bricked?
And thank you for your help.
1. Yes, you can flash CWM while on fastboot. I suggest you flash stock ftf file, then flash kernel.
2. You can access CWM folder in sd card via PC to access your backups, but you cannot extract data from them.
This is the content you will see in your backup folder.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LT18i using xda app-developers app
popthosegaskets said:
1. Yes, you can flash CWM while on fastboot. I suggest you flash stock ftf file, then flash kernel.
2. You can access CWM folder in sd card via PC to access your backups, but you cannot extract data from them.
This is the content you will see in your backup folder.
Sent from my LT18i using xda app-developers app
Click to expand...
Click to collapse
Regarding step 1, how can I flash CWM if I lost root? Can you give me more detail?
Flash the ftf file, root your phone, then flash CWM.
Sent from my LT18i using xda app-developers app
popthosegaskets said:
Flash the ftf file, root your phone, then flash CWM.
Sent from my LT18i using xda app-developers app
Click to expand...
Click to collapse
Um except my phone can't even boot without wiping data. All it does is boot loop once flashed 4.0.4. Is there any way NOT to make it bootloop WITHOUT wiping my data?
YoBob said:
Um except my phone can't even boot without wiping data. All it does is boot loop once flashed 4.0.4. Is there any way NOT to make it bootloop WITHOUT wiping my data?
Click to expand...
Click to collapse
Dude i believe more or less your data is gone now. Listen to the above post and use Flashtool and flash the stock Sony FTF file for your phone. Then boot into stock rom and later install CWM (either with auto installer or by flashing a custom kernel with CWM) then try putting your backup.
Link to download flashtool? and instuction howto flash?
Pruikki said:
Link to download flashtool? and instuction howto flash?
Click to expand...
Click to collapse
..
XperienceD said:
The Flashtool, Updating, Unbricking & De-Branding:
PLEASE NOTE:
If you have Un-Locked your Bootloader DO NOT UPDATE Over The Air (O.T.A) or YOU WILL BRICK your Device. If you have Bricked then see THIS thread with how to Restore your Phone.
{RECOVER SOFT-brick}[2012 XPERIA's]Recover ALL 2012 XPERIAs from SOFT-brick
[Remote Support] Fully Repair Dead Xperias Arc/Neo/Play/X10/X8/W8/Mini/MiniPro ALL
The Flashtool is simply what it says on the tin, it's a tool that flashes Firmware to your device in a similar manner as SEUS or PC Companion does except the Flashtool requires .ftf files which can be downloaded from your devices General or Development forum. This is generally the preferred method for Repairing your Phone if SEUS or PC Companion aren't an option or you just prefer not to use them. You can also use the Flashtool to flash a Generic .ftf to your device which will remove any Operator Branding from your device.
This video by BlueChipJ explains the process of using the Flashtool...
...or you can use (specific Phones only) the Official Sony Flash Tool. See maxio1998's thread for more info - [TOOL]Official Sony Flash Tool | Unlocked Devices
Click to expand...
Click to collapse
it's up guys
https://developers.google.com/android/nexus/images#takjujzo54k
since I haven't gotten the OTA update yet can I just flash "system.img" in fastboot to update from 4.1.1. to 4.1.2. and call it a day ?
Nice! And so I'm tempted to switch to takju once again...
I probably will switch over the weekend if the yakju OTA hasn't come out by then.
Thanks for posting!
Interesting Google provided a windows batch file for flashing.
In other news my usb port is messed up so I'm going to have to wait for the OTA
Currently unlocked and on Yakju. If I flash to Takju, will I lose all the data?
I'm 99% sure that you will loose all user data.
NexusDro said:
Currently unlocked and on Yakju. If I flash to Takju, will I lose all the data?
Click to expand...
Click to collapse
Maybe, but maybe not.
Assuming you have all you apps and app data backuped up in /sdcard using Titanium Backup, do the following:
Flash the boot and system images only, reboot into CWM, wipe cache and dalvik cache, and then reboot.
If you end up with a bootloop or it doesn't boot, just reboot into CWM and wipe data, and it will reboot. Then restore you apps and app data via TB (after flashing a superuser zip of course).
EDIT: I've never seen any say they've tried it, so maybe you can help all of us out.
Thanks! Mine's not root so no titanium backup for me. Since I'm currently out of town until this weekend, I'll wait for the OTA and see what happens.
efrant said:
Maybe, but maybe not.
Assuming you have all you apps and app data backuped up in /sdcard using Titanium Backup, do the following:
Flash the boot and system images only, reboot into CWM, wipe cache and dalvik cache, and then reboot.
If you end up with a bootloop or it doesn't boot, just reboot into CWM and wipe data, and it will reboot. Then restore you apps and app data via TB (after flashing a superuser zip of course).
EDIT: I've never seen any say they've tried it, so maybe you can help all of us out.
Click to expand...
Click to collapse
Nonsense,
I was on yakju rooted with the bootloader unlocked, of course. Then I followed your AWESOME guide without backing up ANYTHING and it worked!
I only skipped step 10 (flash userdata.img) and rebooted just fine. It took a while because of the dalvik cache rebuild.
After that I booted in CWM (without flashing it) and applied the SuperUser .zip and gained root again.
Everything's fine. No data loos at all!
Cheers!
Interesting to note that they seem to have 4.1.2 completely superceding 4.1.1, that is to say, they're removing the 4.1.1 builds once a 4.1.2 build is up for a particular device.
osm0sis said:
Interesting to note that they seem to have 4.1.2 completely superceding 4.1.1, that is to say, they're removing the 4.1.1 builds once a 4.1.2 build is up for a particular device.
Click to expand...
Click to collapse
For the Nexus 7, it is a requirement since newer Nexus 7 variants will apparently not run on 4.1.1. So I think they are not going to keep the links up for 4.1.1 because of that.
Can anyone post the Build.prop form takju 4.1.2
3rdstring said:
Can anyone post the Build.prop form takju 4.1.2
Click to expand...
Click to collapse
El Daddy said:
Interesting Google provided a windows batch file for flashing.
In other news my usb port is messed up so I'm going to have to wait for the OTA
Click to expand...
Click to collapse
It's easy to make a batch file, I personally made one for my n7 and gnex.
Will the next nexus have a longer screen?
5 hours to download from Google. Anyone have a mirror?
No OTA's yet?
Sent from my Galaxy Nexus using xda app-developers app
el_charlie said:
Nonsense,
I was on yakju rooted with the bootloader unlocked, of course. Then I followed your AWESOME guide without backing up ANYTHING and it worked!
I only skipped step 10 (flash userdata.img) and rebooted just fine. It took a while because of the dalvik cache rebuild.
After that I booted in CWM (without flashing it) and applied the SuperUser .zip and gained root again.
Everything's fine. No data loos at all!
Cheers!
Click to expand...
Click to collapse
You dirty-flashed yakju to takju, and no problems? Congratulations to you and efrant!
segv11 said:
You dirty-flashed yakju to takju, and no problems? Congratulations to you and efrant!
Click to expand...
Click to collapse
Not a single one!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks to efrant for such amazing guide.
Cheers!
Sent from my Galaxy Nexus using xda premium
Sorry for the noob question but what tool did u guys use to flash some portions of the factory image? Mobile odin, odin or gnexus toolkit? Thank you
Can someone please provide a noob proof tutorial to flash an unlocked and rooted "yakju", thank you again.
Sent from my Nexus Prime JB 4.1.1
My S3 is setting backup recovery file dates that show as 1970, yet the system date/time seems to be correct. I found some older backup files stored on my laptop (moved from the phone long ago) that had correct dates--so this is something that apparently changed somewhere along the way (OS upgrade?).
Does anyone know of this problem cause and a fix?
If you're using TWRP 2.6.x then it is a known issue. From what I hear updating TWRP fixes that but a lot of people have said problems arise with creating or restoring backups with it. Probably the problems with KitKat and the storage changes. I just amend the date when I make backups.
pre4speed said:
If you're using TWRP 2.6.x then it is a known issue. From what I hear updating TWRP fixes that but a lot of people have said problems arise with creating or restoring backups with it. Probably the problems with KitKat and the storage changes. I just amend the date when I make backups.
Click to expand...
Click to collapse
I am on CWM 6.0.4.7. I hadn't thought about it being an issue with the recovery, but that makes sense; since the backup is done in recovery with the OS not running, and the only time in the phone comes from the network, then there may not even be a software call that can access current time when recovery is trying to make a backup.
But I did have some older ones that had a then-current date on them. ????
Now very puzzled.
Yeah that happened to me too. It got to a point where I couldn't even name them via ROM manager. I had to do the backup in recovery, reboot, then name it myself. Otherwise I never knew which were which.
ZehelSitchel said:
Yeah that happened to me too. It got to a point where I couldn't even name them via ROM manager. I had to do the backup in recovery, reboot, then name it myself. Otherwise I never knew which were which.
Click to expand...
Click to collapse
I *BELIEVE* it is because a time is not available to the backup code while in recovery (OS not running), but I don't see why, when the backup is commanded from within ROM Manager (OS is running), that the date/time could not be stored in a file to be used in the filename by the recovery code running the backup.
1970-01-01 is time 0 in the POSIX time system on linux. Its presence suggests that either the recovery app didn't define the system clock to make it available, or didn't give the file system commands permissions to use it.
The system clock can be available in recovery. I use Philz custom with CWM. Both the backup folders and files have correct dates and times.
You can choose to use TWRP format under Philz and the files are supposed to be available to TWRP, in the default folder. I don't know if that will fix the date issue. I'll try on my S3 and report back.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Proper date when using TWRP format under Philz - It's open source, so the TWRP team should look at what he does.
Here's a screen shot from xplore, looking at the backup folder,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Philz thread
http://forum.xda-developers.com/showthread.php?p=39433458
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Thank you for that reply--very helpful!
Quick question: does Philz recovery put boot-to-recovery entry in the long-press-power menu?
LATER:
Drilled through things starting at the link you provided. Apparently I am supposed to use the d2lte version for my ATT S3. But when I get to the (appropriate, I think) download page, there are 'tons' of files listed...
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
????
Also, for completeness, I am running rooted, but standard ATT ROM at 4.1.2; the 4.3 OTA update always fails to install.
Yes, you want d2lte version. Should work on any JB rom, including 4.1.2.
If you have option to boot to recovery from long press power button, then it will still be there and should work. That's how I do it, avoiding power down and button combo. Philz doesn't add that reboot to recovery option. It's an option on some roms, like cyanogen, or you can find a free app on Google play to do it.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
laughingT said:
Yes, you want d2lte version. Should work on any JB rom, including 4.1.2.
If you have option to boot to recovery from long press power button, then it will still be there and should work. That's how I do it, avoiding power down and button combo. Philz doesn't add that reboot to recovery option. It's an option on some roms, like cyanogen, or you can find a free app on Google play to do it.
Click to expand...
Click to collapse
I do not have it now--I thought the Recovery added it. I always enter recovery from within ROM Manager--don't even remember the key technique. Will doing it from ROM Manager still work if I go to Philz?
I don't know. You could check the thread in the link I posted above. If you search the thread, I expect you find the answer.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Just a quick question. I flashed a stock build then went to 5.0 with zero issues. I'm under the assumption this wiped your device as stated in the directions but for some reason I'm missing a ton of storage. Should have any 24gb of free space after a clean flash. I don't have Google+ photos synced or anything.
Anyone else see that?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FormeriPhoney said:
Just a quick question. I flashed a stock build then went to 5.0 with zero issues. I'm under the assumption this wiped your device as stated in the directions but for some reason I'm missing a ton of storage. Should have any 24gb of free space after a clean flash. I don't have Google+ photos synced or anything.
Anyone else see that?
Click to expand...
Click to collapse
Were you using factory images? Just curious. Stock recovery? Wipe data/factory reset. TWRP? Format data. Or... fastboot format userdata. That's the options that I remember hearing of but I've not had the problem myself. Any of those options will of course wipe your storage.
wantabe said:
Were you using factory images? Just curious. Stock recovery? Wipe data/factory reset. TWRP? Format data. Or... fastboot format userdata. That's the options that I remember hearing of but I've not had the problem myself. Any of those options will of course wipe your storage.
Click to expand...
Click to collapse
I actually used wugfresh toolkit bc I had a problem with adb for some reason.
I got some help from the nexus 7 community on google+ and it was as simple as just doing a factory reset. Lol. Showed up 26.9gb free after that.
Sometimes it is just the easiest stuff right under your nose ?
FormeriPhoney said:
I actually used wugfresh toolkit bc I had a problem with adb for some reason.
I got some help from the nexus 7 community on google+ and it was as simple as just doing a factory reset. Lol. Showed up 26.9gb free after that.
Sometimes it is just the easiest stuff right under your nose ?
Click to expand...
Click to collapse
Good deal!
I flashed a rom that I found here and I didn't check my storage, but ES file explorer showed a complete lack of sd card... I coulnd't take pictures or download files, but I could download apps..
jastonas said:
I flashed a rom that I found here and I didn't check my storage, but ES file explorer showed a complete lack of sd card... I coulnd't take pictures or download files, but I could download apps..
Click to expand...
Click to collapse
Try a factory reset.. Easy and hopefully the answer
FormeriPhoney said:
Try a factory reset.. Easy and hopefully the answer
Click to expand...
Click to collapse
I flashed the stock image using flashboot again..
Do we have root and twrp on the nexus 7 yet?
Yes. Go to the Android Development thread [http://forum.xda-developers.com/showthread.php?t=2856920 ], post 441. You need a modified boot image for root. You can fastboot flash twrp and fastboot flash the kernel. Or, there is a zip of the kernel. Or, you could use Wug's newly updated toolkit.
Sent from my Nexus 7 using Tapatalk
ritchea said:
Yes. Go to the Android Development thread [http://forum.xda-developers.com/showthread.php?t=2856920 ], post 441. You need a modified boot image for root. You can fastboot flash twrp and fastboot flash the kernel. Or, there is a zip of the kernel. Or, you could use Wug's newly updated toolkit.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yup.. As soon as I saw wug update the program I jumped on it. Rooted and twrp in less than 5 min.
[emoji106]
I simply want to flash a different custom rom from custom rom (crdroid) on my POCO F3, but I am unable to do that because of these persistent errors. Please advise me on how to resolve this so that I may successfully flash my rom using the step-by-step instructions. Thank you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[Removed]
cyanGalaxy said:
Don't directly dirty flash another Custom ROM, this will almost certainly brick your phone.
You must flash Stock ROM (Official MIUI ROM) inbetween switching to another Custom ROM. It should be done cleanly.
Click to expand...
Click to collapse
I wanna return to the stock rom. What should I do to properly flash stock ROM using TWRP recovery? I usually get those errors (device block required) when I try to flash a rom. Please help.
oyolzn said:
I wanna return to the stock rom. What should I do to properly flash stock ROM using TWRP recovery? I usually get those errors (device block required) when I try to flash a rom. Please help.
Click to expand...
Click to collapse
Sorry, I was mistaken, I think you are flashing Official MIUI, right?..
If you chose the Full Recovery ROM for MIUI, it should work.. I don't know why it's not working.
Have you tried wiping Dalvik Cache & Data?
(after flashing MIUI, you can then proceed flashing a different Custom ROM)
cyanGalaxy said:
Sorry, I was mistaken, I think you are flashing Official MIUI, right?..
If you chose the Full Recovery ROM for MIUI, it should work.. I don't know why it's not working.
Have you tried wiping Dalvik Cache & Data?
(after flashing MIUI, you can then proceed flashing a different Custom ROM)
Click to expand...
Click to collapse
Yes, I'm flashing the official MIUI. I have no idea why it isn't working. Even after wiping the data and dalvik cache, such problems continue to appear. Is there a way to fix such problems on TWRP? Would you kindly assist me? My device doesn't have an OS installed anyway.
oyolzn said:
Yes, I'm flashing the official MIUI. I have no idea why it isn't working. Even after wiping the data and dalvik cache, such problems continue to appear. Is there a way to fix such problems on TWRP? Would you kindly assist me? My device doesn't have an OS installed anyway.
Click to expand...
Click to collapse
Have you tried using TWRP skkk? That one supports Android 12's encryption
skkk/TWRP/A12 • AKR DL
dl.akr-developers.com
I got that link from here: https://forum.xda-developers.com/t/...p-3-6-0_11-v2-9-3_a11-alioth-skkk-is.4373463/
oyolzn said:
I simply want to flash a different custom rom from custom rom (crdroid) on my POCO F3, but I am unable to do that because of these persistent errors. Please advise me on how to resolve this so that I may successfully flash my rom using the step-by-step instructions. Thank you.View attachment 5664333
Click to expand...
Click to collapse
i used to get these but then i tried once to mount all partitions before flashing and i didnt get these comments
partitions encrypted, need to be formatted before reflashing ROM, better backup all your data if you can still access it, if not, then say goodbye to your files because you need to format it.
cyanGalaxy said:
Have you tried using TWRP skkk? That one supports Android 12's encryption
skkk/TWRP/A12 • AKR DL
dl.akr-developers.com
I got that link from here: https://forum.xda-developers.com/t/anybody-know-what-twrp-3-6-0_11-v2-9-3_a11-alioth-skkk-is.4373463
Click to expand...
Click to collapse
SamantaSync said:
partitions encrypted, need to be formatted before reflashing ROM, better backup all your data if you can still access it, if not, then say goodbye to your files because you need to format it.
Click to expand...
Click to collapse
How can I format partition? Given that the device is new, it's okay if my files are gone. I only want to install and get back the official ROM as I'm used to custom ROMs (crdoid) on my device. Is there a step-by-step guide for fixing that? Please help me so that I can continue to flash successfully. Even after formatting the data and entering "yes," those errors continue to appear. Data formatting is not successful.
3zozHashim said:
i used to get these but then i tried once to mount all partitions before flashing and i didnt get these comments
Click to expand...
Click to collapse
How can I mount all partition? What recovery are you using? Please help.
twrp
oyolzn said:
How can I format partition? Given that the device is new, it's okay if my files are gone. I only want to install and get back the official ROM as I'm used to custom ROMs (crdoid) on my device. Is there a step-by-step guide for fixing that? Please help me so that I can continue to flash successfully. Even after formatting the data and entering "yes," those errors continue to appear. Data formatting is not successf
Click to expand...
Click to collapse
oyolzn said:
I simply want to flash a different custom rom from custom rom (crdroid) on my POCO F3, but I am unable to do that because of these persistent errors. Please advise me on how to resolve this so that I may successfully flash my rom using the step-by-step instructions. Thank you
oyolzn said:
I simply want to flash a different custom rom from custom rom (crdroid) on my POCO F3, but I am unable to do that because of these persistent errors. Please advise me on how to resolve this so that I may successfully flash my rom using the step-by-step instructions. Thank you.View attachment 5664333
Click to expand...
Click to collapse
Fastboot boot twrp skk 3.6.0 after go to recovery format data , then u able to flash , I had this issue when I use 3.6.0 skk then it's fixed
Click to expand...
Click to collapse