Related
First of all,
Sometimes we facing BOOTLOOP, but we rarely make a backup so DATA in that backup already out to date.
And i found a method which can FIX BOOTLOOP WITHOUT RESTORING OLD BACKUP !
CAUTION !
THIS METHOD ONLY FOR ANYONE WHO FACING BOOTLOOP AFTER INSTALLING APPS, MODS, ETC
AND THAT APP IS NOT IMPORTANT FOR YOUR ROM
Things you will need
PC or Laptop
USB Cable (For connecting SD-CARD)
SD-CARD Reader (If your CWM Recovery can't mount SD-CARD)
WinRAR or WinZip
Notepad++
Patience!
Click to expand...
Click to collapse
So, lets begin..
STEP 1
If you facing bootloop after installing apps, mods, etc.
YOU MUST REMEMBER THE NAME AND LOCATION OF APPS/MODS YOU'VE PREVIOUSLY INSTALLED
Click to expand...
Click to collapse
STEP 2
Download my CWM zip HERE
Click to expand...
Click to collapse
STEP 3
In PC, after download, extract zip, open META-INF > com > google > android
Open updater-script with Notepad++
Click to expand...
Click to collapse
STEP 4
Edit this line
Code:
delete("/system/app/Home.apk","/system/etc/permissions/com.sonyericsson.uxpres.xml");
with name and location of apps/mods you've previously installed
Ex.
Code:
[CENTER]delete("/system/app/Crap.apk");[/CENTER]
And if you installed more than 1 app, you can insert another name and location in 1 line
Ex.
Code:
delete("/system/app/Crap.apk","/system/etc/permissions/com.bluesky.nxp-resolution.xml");
Click to expand...
Click to collapse
STEP 5
Save your modified updater-script and zipped the META-INF and system folder
Click to expand...
Click to collapse
STEP 6
Put your modified zip to your SD-CARD with mount sdcard option in CWM (with USB Cable) or using SD-CARD Reader
Click to expand...
Click to collapse
STEP 7
Flash It !
DONE !
Click to expand...
Click to collapse
Thanks, its is a lot easier to do with adb file manager thingy software I found online, connecting to pc via usb gives full access to phone file system partitions with root access, just deleting the files with it also works. :thumbup:
Why are SMARTphones soo... Freaking Dumb?
Or via adb
Connect phone/tablet to pc
In adb type:
adb delete("/system/app/Whatever.apk")
Done...
Disadv: USB Debugging must be enabled...
You sir are awesome, I flashed a zip that caused my Xperia U to bootloop and I couldn't delete the file I flahed via ADB! This is a simple yet amazing script, thanks for avoiding me to wipe data
Bert98 said:
You sir are awesome, I flashed a zip that caused my Xperia U to bootloop and I couldn't delete the file I flahed via ADB! This is a simple yet amazing script, thanks for avoiding me to wipe data
Click to expand...
Click to collapse
You're welcome
Before I tried the tutorial you or even try out all of the tutorials available on the internet, please help me to conclude my problem.
My device
(IPRO SENSEI FI)
(OS : KITKAT)
(ROOTED"Using kingoroot but I change to supersu") (ORIGINAL ROM NO CUSTOM)
(STOCK RECOVERY)
(NO HAVE ORIGINAL BACKUP OR Etc. T_T )
If you need more information Ask me.
My problem is Bootloop "Or you have another name, because I do not understand", just stop on logo but it still can go into recovery mode.
The story before the events bootloop or whatever name this problem, So as I recall before this incident I edit files and install Tweaks build.prop with applications My pimp and try other features, it works, but when I restart my device. You know what happened. when just stopped in my logo I does not do anything just to wait so that I fell asleep and when I woke up I realized this a bootloop Or what ? I do not know his name.
At that time I was just doing the usual way way., list.
(Wipe data / Factory reset)
(Wipe cache partition)
(reboot system now)
but no change
(Restore user data)
(backup user data)
(Reboot again)
Still same
(Apply update from ADB - I do not have a pc)
(Apply update from sdcard - No have ORIGINAL ROM, BACKUP ROM, CUSTOM ROM Etc.)
(Apply update from cache - I do not understand what this)
Just information There is writing on my recovery mode "Android System Recovery <3e> ALPS.KK1.MP7.V1" I do not know what this is but I show in case you need it.
I think your reading if this type of problem?
Is it still could be improved?
Installing custom rom whether other devices can fix this? What is this due to file damage build.prop?
How to fix it?
Can you tell tutorial to solve this problem?
If you told me to look for tutorials on the internet what keywords for this problem?
What is correct I asked here or I OOT?
What do I need to make this thread or just my neighbor asking questions like this course in every thread that said key bootloop?
You do not have to answer all of them just answer that you know or your own statement to me, I am newbie please guidance, Sorry in advance, and thanks afterward
hey the link isn't working anymore? can you please reupload?
Do you have to get into recovery? as i have no recovery on my phone Xperia z3
After tinkering with the tablet and trying my best to restore it I finally was able last night to restore it to a clean install using this method. I'm sure there may be other ways to do it as well but this worked for me and was painless.
1. Make sure the tablet is rooted/unencrypted using Vampirefo's guide:
http://forum.xda-developers.com/android/development/root-nextbook-ares-8-twrp-recovery-t3133165
2. Make a backup of your System, Boot, etc. of your current boot-looped ROM with TWRP.
3. With TWRP's file manager, go into the internal storage and delete all the files within the backup folder.
4. Download this backup:
https://onedrive.live.com/?id=19085CD12562E567%21931&cid=19085CD12562E567&group=0&parId=19085CD12562E567%21925&authkey=%21AHmuVovnpuzX0tI&action=locate
5. Extract the files from the zip and copy them over to the backup folder on the internal storage.
6. Go to Restore on TWRP and dance.
After many attempts of trying to restore from an external SD card and from just creating my own TWRP backup folder, TWRP just wouldn't see the backup until I copied and replaced. I'm glad it worked and I hope it helps anyone else who needs a restore.
Credit goes to jmreyesiii for providing the backup files and vampirefo for the rooting.
PhantomOSX said:
After tinkering with the tablet and trying my best to restore it I finally was able last night to restore it to a clean install using this method. I'm sure there may be other ways to do it as well but this worked for me and was painless.
Credit goes to jmreyesiii for providing the backup files and vampirefo for the rooting.
Click to expand...
Click to collapse
An absolutely great post! You need a special thanks because this ability to recover from catastrophe likely will encourage others to move forward with more daring mods. I feel much more secure in playing with a few ideas knowing you have the base Rom and recovery spelled out and that it actually worked (Yes, I knew how, but knowing it worked for sure is huge!)
Thanks,
Freddy999
Now if only some kind hearted dev would release a ROM....
Actually, after you root and decrypt it, and fix the cpu governor and such, and get rid of the google apps that you don't use, with the exception of the lollipop HW overlay flaw it is not a bad ROM to start with. I wiped most of the Google stuff and put in Nova launcher. Now the device is quite manageable and very fast without much further help. Here is a pretty good summary of the device for anyone who has the tools to build a ROM: http://specdevice.com/showspec.php?id=ee2d-39de-0033-c5870033c587 with the exception I can not find that the FM radio exists in the device although the hardware seems to say it is there..........
what do you mean cpu governor?
adamx said:
what do you mean cpu governor?
Click to expand...
Click to collapse
Playstore: No frills CPU control
set it ondemand, noop
You might want to get also CPU spy reloaded to see the effect/
The backup file expired (or something) on OneDrive. Would you mind re-upping it somewhere? Thanks!
PhantomOSX said:
After tinkering with the tablet and trying my best to restore it I finally was able last night to restore it to a clean install using this method. I'm sure there may be other ways to do it as well but this worked for me and was painless.
1. Make sure the tablet is rooted/unencrypted using Vampirefo's guide:
http://forum.xda-developers.com/android/development/root-nextbook-ares-8-twrp-recovery-t3133165
2. Make a backup of your System, Boot, etc. of your current boot-looped ROM with TWRP.
3. With TWRP's file manager, go into the internal storage and delete all the files within the backup folder.
4. Download this backup:
https://onedrive.live.com/?id=19085CD12562E567%21931&cid=19085CD12562E567&group=0&parId=19085CD12562E567%21925&authkey=%21AHmuVovnpuzX0tI&action=locate
5. Extract the files from the zip and copy them over to the backup folder on the internal storage.
6. Go to Restore on TWRP and dance.
After many attempts of trying to restore from an external SD card and from just creating my own TWRP backup folder, TWRP just wouldn't see the backup until I copied and replaced. I'm glad it worked and I hope it helps anyone else who needs a restore.
Credit goes to jmreyesiii for providing the backup files and vampirefo for the rooting.
Click to expand...
Click to collapse
Yes the link to the backup is dead, can OP or anyone else upload another? I wiped the internal storage and now android has no home or back buttons so I cant get out of apps
Uploaded to MEGA https://mega.nz/#!1J4VwDxL!ZvRkBlvD7m-ldc5qQxA_xDWfUiu6WDdJa3nAMvDfhZY
stevemp said:
Uploaded to MEGA https://mega.nz/#!1J4VwDxL!ZvRkBlvD7m-ldc5qQxA_xDWfUiu6WDdJa3nAMvDfhZY
Click to expand...
Click to collapse
Thanks!
stevemp said:
Uploaded to MEGA https://mega.nz/#!1J4VwDxL!ZvRkBlvD7m-ldc5qQxA_xDWfUiu6WDdJa3nAMvDfhZY
Click to expand...
Click to collapse
Thanks Steve you're a true bro
THANK YOU!!!!!!!!!
I rooted and removed the encryption from my ARES 8 but then when messing with an (official) flashing tool I ended up formatting my system partition., So I had NO OS at all., But I did have TWRP., And now thanks to your post I have a living breathing working tablet again., By all your gods (or none at all if that's your thing) I Bless you! Thank you X Infinity! :good::good::good::good::good:
-Eric.
P.S. I got it to work from my SD card but I did have to make a backup with TWRP first, then pop the SD card into the PC delete all the files from the folder and copy your files into the folder that TWRP had created. Otherwise it didn't show up at all... Anyway Thanks again! :victory:
PhantomOSX said:
After tinkering with the tablet and trying my best to restore it I finally was able last night to restore it to a clean install using this method. I'm sure there may be other ways to do it as well but this worked for me and was painless.
1. Make sure the tablet is rooted/unencrypted using Vampirefo's guide:
http://forum.xda-developers.com/android/development/root-nextbook-ares-8-twrp-recovery-t3133165
2. Make a backup of your System, Boot, etc. of your current boot-looped ROM with TWRP.
3. With TWRP's file manager, go into the internal storage and delete all the files within the backup folder.
4. Download this backup:
https://onedrive.live.com/?id=19085CD12562E567%21931&cid=19085CD12562E567&group=0&parId=19085CD12562E567%21925&authkey=%21AHmuVovnpuzX0tI&action=locate
5. Extract the files from the zip and copy them over to the backup folder on the internal storage.
6. Go to Restore on TWRP and dance.
After many attempts of trying to restore from an external SD card and from just creating my own TWRP backup folder, TWRP just wouldn't see the backup until I copied and replaced. I'm glad it worked and I hope it helps anyone else who needs a restore.
Credit goes to jmreyesiii for providing the backup files and vampirefo for the rooting.
Click to expand...
Click to collapse
It's says root only on Linux I have windows xp does anyone know how I can root this on this type of computer thank u
Here is a question, we bought one for the grandson.. How come when you open up the play store, and choose apps, it does not show any that came with the tablet itself, kind of like you see when you go to play store on a smartphone..
really need some help
ericzollman said:
I rooted and removed the encryption from my ARES 8 but then when messing with an (official) flashing tool I ended up formatting my system partition., So I had NO OS at all., But I did have TWRP., And now thanks to your post I have a living breathing working tablet again., By all your gods (or none at all if that's your thing) I Bless you! Thank you X Infinity! :good::good::good::good::good:
-Eric.
P.S. I got it to work from my SD card but I did have to make a backup with TWRP first, then pop the SD card into the PC delete all the files from the folder and copy your files into the folder that TWRP had created. Otherwise it didn't show up at all... Anyway Thanks again! :victory:
Click to expand...
Click to collapse
i am having the same basic problem, i flashed twrp and supersu not sure what i did wrong or if it rooted succesfuly, i do have twrp but wont boot past recovery. twrp says it cant mount data and i cant back up., and have no os. how can i fix this ?
im new to this whole thing so please give me step by step if you can and any links or downloads you can, please help :crying: this tablet is how i comunicate w my daughter... in colorado. i need it up and running
I partitioned my Ares 8 and now it is stuck awaiting fastboot command. Any ideas?
Can someone help me? Why does mine fail when restoring system?
My ares 8 is stuck in DNX mode and will not enter recovery, and is pretty hosed. I need a scatterfile and rom so I can flash it and use it for something besides a paperweight. Thanks 1000 times in advance!
Ahhh, after several hours of reading, I managed to get recovery back, but cannot seem to flash a rom successfully, and also my backup - says it was successful but when I reboot, it goes straight to DnX mode and I have to use a batch file to get back to recovery. But progress has been made and hopefully by today I will have it back up and running an OS
Hi, i have Nextbook Ares 8 after rooing i can't boot the device it has an error says "Your device is unable to start because the Android OS image has failed to verify" please help me to fix this problem.
My device
(IPRO SENSEI FI)
(OS : KITKAT)
(ROOTED"Using kingoroot but I change to supersu") (ORIGINAL ROM NO CUSTOM)
(STOCK RECOVERY)
(NO HAVE ORIGINAL BACKUP OR Etc. T_T )
If you need more information Ask me.
My problem is Bootloop "Or you have another name, because I do not understand", just stop on logo but it still can go into recovery mode.
The story before the events bootloop or whatever name this problem, So as I recall before this incident I edit files and install Tweaks build.prop with applications My pimp and try other features, it works, but when I restart my device. You know what happened. when just stopped in my logo I does not do anything just to wait so that I fell asleep and when I woke up I realized this a bootloop Or what ? I do not know his name.
At that time I was just doing the usual way way., list.
(Wipe data / Factory reset)
(Wipe cache partition)
(reboot system now)
but no change
(Restore user data)
(backup user data)
(Reboot again)
Still same
(Apply update from ADB - I do not have a pc)
(Apply update from sdcard - No have ORIGINAL ROM, BACKUP ROM, CUSTOM ROM Etc.)
(Apply update from cache - I do not understand what this)
Just information There is writing on my recovery mode "Android System Recovery <3e> ALPS.KK1.MP7.V1" I do not know what this is but I show in case you need it.
Just info :
"I have submitted my problem is on the web and social media owned IPRO but no response, I also have to ask in the thread "is concerned about this issue but no response. I do not know if I really make this thread in the forum Q & A if any anyone please notifications where should I post this thread, I hope anyone can help me here, if no input on how to make this a better thread again please write your comment"
I think your reading if this type of problem?
Is it still could be improved?
Installing custom rom whether other devices can fix this? What is this due to file damage build.prop?
How to fix it?
Can you tell tutorial to solve this problem?
If you told me to look for tutorials on the internet what keywords for this problem?
What is correct I asked here or I OOT?
What do I need to make this thread or just my neighbor asking questions like this course in every thread that said key bootloop?
You do not have to answer all of them just answer that you know or your own statement to me, I am newbie please guidance, Sorry in advance, and thanks afterward
Nano.nano said:
My device
(IPRO SENSEI FI)
(OS : KITKAT)
(ROOTED"Using kingoroot but I change to supersu") (ORIGINAL ROM NO CUSTOM)
(STOCK RECOVERY)
(NO HAVE ORIGINAL BACKUP OR Etc. T_T )
If you need more information Ask me.
My problem is Bootloop "Or you have another name, because I do not understand", just stop on logo but it still can go into recovery mode.
The story before the events bootloop or whatever name this problem, So as I recall before this incident I edit files and install Tweaks build.prop with applications My pimp and try other features, it works, but when I restart my device. You know what happened. when just stopped in my logo I does not do anything just to wait so that I fell asleep and when I woke up I realized this a bootloop Or what ? I do not know his name.
At that time I was just doing the usual way way., list.
(Wipe data / Factory reset)
(Wipe cache partition)
(reboot system now)
but no change
(Restore user data)
(backup user data)
(Reboot again)
Still same
(Apply update from ADB - I do not have a pc)
(Apply update from sdcard - No have ORIGINAL ROM, BACKUP ROM, CUSTOM ROM Etc.)
(Apply update from cache - I do not understand what this)
Just information There is writing on my recovery mode "Android System Recovery <3e> ALPS.KK1.MP7.V1" I do not know what this is but I show in case you need it.
Just info :
"I have submitted my problem is on the web and social media owned IPRO but no response, I also have to ask in the thread "is concerned about this issue but no response. I do not know if I really make this thread in the forum Q & A if any anyone please notifications where should I post this thread, I hope anyone can help me here, if no input on how to make this a better thread again please write your comment"
I think your reading if this type of problem?
Is it still could be improved?
Installing custom rom whether other devices can fix this? What is this due to file damage build.prop?
How to fix it?
Can you tell tutorial to solve this problem?
If you told me to look for tutorials on the internet what keywords for this problem?
What is correct I asked here or I OOT?
What do I need to make this thread or just my neighbor asking questions like this course in every thread that said key bootloop?
You do not have to answer all of them just answer that you know or your own statement to me, I am newbie please guidance, Sorry in advance, and thanks afterward
Click to expand...
Click to collapse
I edit files and install Tweaks build.prop
Click to expand...
Click to collapse
more than likely, it is not booting because you made some bad edits to the build prop. i see this happen a lot.
you will need to find a stock firmware for your device and install it back to fix the problem.
use search terms like "(your device name) return to stock" to try and locate the files.
bweN diorD said:
more than likely, it is not booting because you made some bad edits to the build prop. i see this happen a lot.
you will need to find a stock firmware for your device and install it back to fix the problem.
use search terms like "(your device name) return to stock" to try and locate the files.
Click to expand...
Click to collapse
Thanks for your suggestions and answers, Before I made this thread I have searched from internet Stock firmware or stockrom for my device but I never found it, Is there any other way than to install stock rom or firmware to fix my device, or install a custom rom firmware or install other devices can be made in alternative
Nano.nano said:
Thanks for your suggestions and answers, Before I made this thread I have searched from internet Stock firmware or stockrom for my device but I never found it, Is there any other way than to install stock rom or firmware to fix my device, or install a custom rom firmware or install other devices can be made in alternative
Click to expand...
Click to collapse
you can try searching for a custom rom, that should fix it.
other than that, with no stock firmware, i dont see any way you could fix it.
no, you cant use files from another device, unless it specifically says its ok for your device (very rare, but happens occasionally)
bweN diorD said:
you can try searching for a custom rom, that should fix it.
other than that, with no stock firmware, i dont see any way you could fix it.
no, you cant use files from another device, unless it specifically says its ok for your device (very rare, but happens occasionally)
Click to expand...
Click to collapse
Thank you for your prompt response.
Similarity such as what should I look for when taking custom rom or files from other devices?
Nano.nano said:
Thank you for your prompt response.
Similarity such as what should I look for when taking custom rom or files from other devices?
Click to expand...
Click to collapse
look for it to say directly, it can be used on your device. thats the only way.
bweN diorD said:
because you made some bad edits to the build prop.
Click to expand...
Click to collapse
So there will be plenty of experiments,
CMIIW.
If this error in build.prop can I fix it with this way?:
-Take the backup file build.prop.bak with ADB
-Then Edit it by removing the code that previously I input
-And I input back into the system folder in my device with ADB
-And delete files that are in init.d
What a way as it could to improve my device, because I think if it's just damage build.prop file.
And if I use a custom rom whether he would change the system information such as kernel, android version, and whether he will change the code in the file build.prop and What it will also transform the tweaks in the init.d folder or even add to the pile? I think if a custom rom working to add code or tweaks both in build.prop or init.d I think it will worsen, CMIIW, because I think if true custom rom works like that then it is not a good solution
Nano.nano said:
So there will be plenty of experiments,
CMIIW.
If this error in build.prop can I fix it with this way?:
-Take the backup file build.prop.bak with ADB
-Then Edit it by removing the code that previously I input
-And I input back into the system folder in my device with ADB
-And delete files that are in init.d
What a way as it could to improve my device, because I think if it's just damage build.prop file.
And if I use a custom rom whether he would change the system information such as kernel, android version, and whether he will change the code in the file build.prop and What it will also transform the tweaks in the init.d folder or even add to the pile? I think if a custom rom working to add code or tweaks both in build.prop or init.d I think it will worsen, CMIIW, because I think if true custom rom works like that then it is not a good solution
Click to expand...
Click to collapse
1. i have no idea what CMIIW means
2. yes, if you have an original copy of the build prop or can remove edits from the current one, and can replace with adb, that would be good.
3. i would try fixing one thing at a time to see what actually caused the issue. init may or may not need to be fixed.
4. custom rom would clean and replace the entire system including kernel, so it should fix the issue. however, this is your choice, its not a bad option, just a different one.
bweN diorD said:
1. i have no idea what CMIIW means
2. yes, if you have an original copy of the build prop or can remove edits from the current one, and can replace with adb, that would be good.
3. i would try fixing one thing at a time to see what actually caused the issue. init may or may not need to be fixed.
4. custom rom would clean and replace the entire system including kernel, so it should fix the issue. however, this is your choice, its not a bad option, just a different one.
Click to expand...
Click to collapse
CMIIW is Correct Me If I'm Wrong.
Finally, I have two ways for the try, the title and content of this thread may be changed if it is successful.
Thank you for helping me
Thank you for patiently explained
Now I know what to do,
thank you for your participation
thank you very much :good:
no problem
FIRST UNLOCK BOOTLOADER AND FLASH TWRP
2ND install " disable force encryption.zip after that . for video guide go here
and for file go here
3RD DO FACTORY RESET DONT DELETE SYSTEM AND VENDOR
4TH MOUNT SYSTEM AND FLASH ANY GSI IMAGE YOUR CHOICE TO SYSTEM IMAGE PARTIONDONT FLASH ZIP, EXTRACT .IMG FILE AND FLASH
FOR SEMI GSI YOU HAVE TO MOUNT VENDOR THEN FLASH 1,2,3 ZIP
FOR PROOF WATCH THIS VIDEO
Wow man! Someone "ACTUALLY" did it!
I'll try when my f1 arrives
the top corners curves and the margin being small is just killing me :/
But nice work dude
How did you manage to unlock so fast?
1emrys1 said:
How did you manage to unlock so fast?
Click to expand...
Click to collapse
Yeah, how
sankhauaa said:
FIRST UNLOCK BOOTLOADER AND FLASH TWRP
2ND install " disable force encryption.zip after that . for video guide go here
and for file go here
3RD DO FACTORY RESET DONT DELETE SYSTEM AND VENDOR
4TH MOUNT SYSTEM AND FLASH ANY GSI IMAGE YOUR CHOICE TO SYSTEM IMAGE PARTIONDONT FLASH ZIP, EXTRACT .IMG FILE AND FLASH
FOR SEMI GSI YOU HAVE TO MOUNT VENDOR THEN FLASH 1,2,3 ZIP
FOR PROOF WATCH THIS VIDEO
Click to expand...
Click to collapse
How's the experience using a GSI on this phone? What works and what doesn't? Camera usable?
ffh2303 said:
How's the experience using a GSI on this phone? What works and what doesn't? Camera usable?
Click to expand...
Click to collapse
Open camera is working fine.
Almost all working but all GSI have little bug and u have to fixed it manually
Jio volte not working in some gsi
1emrys1 said:
How did you manage to unlock so fast?
Click to expand...
Click to collapse
Ok lets unlock your device within a second
Dont update your phone before this process
First backup your some data like sms call history to mi cloud with sync on ,(see pic in attachment)
Now enable developer option
In this setting u have to check 4 option.dont forget 4 option
Check devoloper option
Check miui unlock(wait mi server read your device)
Check two types of usb debugging
Now download some photo from miui cloud that u just uploaded see sync on and find my device on
Now use mi unlock tool v2.2.406 or other versions u can try
Hope this time u can unlock .dont forget dont update your phone before unlock
Notch support and Jio Volte support for phh treble based ROMs
Can someone make a flashable zip to add notch support to phh treble based ROMs like how it is for mi 8 and can someone make flashable zip to add Jio Volte support for phh treble ROMs any help would be appreciated!
Have a nice day!
I've got mine unlocked fast because I am an old user of xiaomi and i've unlocked my old phone(also xiaomi phone).
Otherwise u've to wait for 720hrs.
Might clear out abit confusion.
sankhauaa said:
FIRST UNLOCK BOOTLOADER AND FLASH TWRP
2ND install " disable force encryption.zip after that . for video guide go here
and for file go here
3RD DO FACTORY RESET DONT DELETE SYSTEM AND VENDOR
4TH MOUNT SYSTEM AND FLASH ANY GSI IMAGE YOUR CHOICE TO SYSTEM IMAGE PARTIONDONT FLASH ZIP, EXTRACT .IMG FILE AND FLASH
FOR SEMI GSI YOU HAVE TO MOUNT VENDOR THEN FLASH 1,2,3 ZIP
FOR PROOF WATCH THIS VIDEO
Click to expand...
Click to collapse
do you flash A or B GSI?
thank you
abihakim said:
do you flash A or B GSI?
thank you
Click to expand...
Click to collapse
A gsi
It shows 57hours waiting time before unlock. I'm on miui version 9.6.18.0.
How can I unlock for sure?
sankhauaa said:
FIRST UNLOCK BOOTLOADER AND FLASH TWRP
2ND install " disable force encryption.zip after that . for video guide go here
and for file go here
3RD DO FACTORY RESET DONT DELETE SYSTEM AND VENDOR
4TH MOUNT SYSTEM AND FLASH ANY GSI IMAGE YOUR CHOICE TO SYSTEM IMAGE PARTIONDONT FLASH ZIP, EXTRACT .IMG FILE AND FLASH
FOR SEMI GSI YOU HAVE TO MOUNT VENDOR THEN FLASH 1,2,3 ZIP
FOR PROOF WATCH THIS VIDEO
Click to expand...
Click to collapse
Hi, I'm quite new here and while I have a general understanding of what you say here, I'm not sure I could follow those instructions without bricking my device by overlooking something or just basic newbie stupidity... Could you make a more detailed guide, please?
PocoSteve said:
Hi, I'm quite new here and while I have a general understanding of what you say here, I'm not sure I could follow those instructions without bricking my device by overlooking something or just basic newbie stupidity... Could you make a more detailed guide, please?
Click to expand...
Click to collapse
after unlock ur device flash twrp then post here i will help you
Pranay nagavolu said:
It shows 57hours waiting time before unlock. I'm on miui version 9.6.18.0.
How can I unlock for sure?
Click to expand...
Click to collapse
you r lucky then not 72 only 57
sankhauaa said:
you r lucky then not 72 only 57
Click to expand...
Click to collapse
Lol
Should we disable force encryption if we want to flash Magisk ?
Hi,
Any place where GSI ROMs are listed ?
That would also be a nice addition to XDA I think
Regards.
I created a script that'll ease Custom ROM installation on A/B devices. The script is generic and will work w/ any rom, device.
General flash instructions:
-Flash OxygenOS
-Flash your Custom ROM of choice
-Flash Finalize.zip
-Boot to System
Download finalize script from here
#######################################
For the intellectuals: This script copies firmware to both slots, clears dalvik-cache and deletes the useless India partition.
Hope this saved you guys some headache while flashing ROMs.
Good job
Sent from my OnePlus6 using XDA Labs
Links off
Link not found.
anhenrique said:
Links off
Click to expand...
Click to collapse
kaziupal said:
Link not found.
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=4349826312261712574
New script in the OP, look there again
I used this same zip on my Motorola G7 Power device. It worked well and is no doubt a life saver. Does anyone know how this is different than finalize zip? I guess I could take a look inside both of them and try to determine what the differences are that way....
There's Finalize.zip I found and I think it is easier. Bacause all you have to do is flash the zip file after installing OOS and ROM with built-in TWRP, then format data and reboot to system. No reboot to recovery in between and save you time.
tiga016 said:
There's Finalize.zip I found and I think it is easier. Bacause all you have to do is flash the zip file after installing OOS and ROM with built-in TWRP, then format data and reboot to system. No reboot to recovery in between and save you time.
Click to expand...
Click to collapse
Link ?
lazye53 said:
Link ?
Click to expand...
Click to collapse
Finalize zip: https://androidfilehost.com/?fid=8889791610682890605
Finalize also deletes India partition.
Flash OOS, flash rom, flash finalize, format data, reboot system.
For some info on finalize see op on Pixen here: https://forum.xda-developers.com/on...ross-device-development/rom-pixen-os-t3969005
Edit
PokemonTotalWar said:
https://androidfilehost.com/?fid=4349826312261712574
Click to expand...
Click to collapse
Stahp
Prakyy said:
Stahp
Click to expand...
Click to collapse
Did you take it down for a reason? It's still accessible through Lineage's website, and people are asking for it. Ask a mod to lock your thread if you don't want any more posts on it, brother
anhenrique said:
Links off
Click to expand...
Click to collapse
Updated w/ AFH link
PokemonTotalWar said:
Did you take it down for a reason? It's still accessible through Lineage's website, and people are asking for it. Ask a mod to lock your thread if you don't want any more posts on it, brother
Click to expand...
Click to collapse
I said stop because you are posting incorrect file. Anyways, I also made a script called "Finalize.zip" which is the one I suggest people use and I've updated the thread to reflect the same.
Didn't check on XDA for a while cuz it wasn't on my mind, really.
Prakyy said:
I said stop because you are posting incorrect file. Anyways, I also made a script called "Finalize.zip" which is the one I suggest people use and I've updated the thread to reflect the same.
Didn't check on XDA for a while cuz it wasn't on my mind, really.
Click to expand...
Click to collapse
Ah, alright. Not trying to be rude, just didn't get the idea from your previous response. Now that Finalize is up on the main post, I'll go ahead and edit my comment to say so
flash713 said:
I used this same zip on my Motorola G7 Power device. It worked well and is no doubt a life saver. Does anyone know how this is different than finalize zip? I guess I could take a look inside both of them and try to determine what the differences are that way....
Click to expand...
Click to collapse
tiga016 said:
There's Finalize.zip I found and I think it is easier. Bacause all you have to do is flash the zip file after installing OOS and ROM with built-in TWRP, then format data and reboot to system. No reboot to recovery in between and save you time.
Click to expand...
Click to collapse
Yes I made the finalize thingy as well lol.
And PiXeN uses that in the official flash instructions so yeah, it works and is definitely the one I recommend you use.
Also, updated the OP.
Prakyy said:
I created a script that'll ease Custom ROM installation on A/B devices. The script is generic and will work w/ any rom, device.
General flash instructions:
-Flash OxygenOS
-Flash your Custom ROM of choice
-Flash Finalize.zip
-Boot to System
Download finalize script from here
#######################################
For the intellectuals: This script copies firmware to both slots, clears dalvik-cache and deletes the useless India partition.
Hope this saved you guys some headache while flashing ROMs.
Click to expand...
Click to collapse
Dude! This ist Genius! Thank you so swirling much!
Prakyy said:
Download finalize script from here
Click to expand...
Click to collapse
using this with no issue at all.
this is what XDA Developers was originally meant for.
thank you very much for this share!
Thank you so much for this. It has made all the flashing hassles much convenient. Works very well on the 6T. I have tried it on couple of different ROMs, no problems yet.
Thank u mister for created this zip fils and script inside in it :good: