Google has no answer for me.
Every time I enter into the recovery and push the message button I get this ERROR: 2.
Everything works fine, its latest TWRP 3.0.2.
Could you tell me something about this error message 2?
What is 'postrecoveryboot.sh'?
How can I get this red message off / without error?
thanx in advance
How do I edit my boot script?
MichaBit said:
Google has no answer for me.
Every time I enter into the recovery and push the message button I get this ERROR: 2.
Everything works fine, its latest TWRP 3.0.2.
Could you tell me something about this error message 2?
What is 'postrecoveryboot.sh'?
How can I get this red message off / without error?
thanx in advance
Click to expand...
Click to collapse
Hi,
I have the same problem. Also on TWRP 3.0.2. and everything seems to work.
Can't find anything about this 'postrecoveryboot.sh' Error 2.
Did you find a solution in the meantime?
Thanks for any help in advance.
Arninho said:
Did you find a solution in the meantime?
Click to expand...
Click to collapse
No, unfortunately not.
If XDA has no solution, who else?
I have the same problem, this is inside the file
Code:
#!/sbin/sh
# Include device-specific vars
source /sbin/bootrec-device
# Turn the LED off
echo 0 > ${BOOTREC_LED_RED}
echo 0 > ${BOOTREC_LED_GREEN}
echo 0 > ${BOOTREC_LED_BLUE}
that error is because this file bootrec-device located at sbin folder always missing when reboot system or recovery
I have try many way
-flash stock rom with flashtool
-flash rom via recovery
-wipe via adb and fastboot
-chmod this file bootrec-device to read only
-remove this file postrecoveryboot.sh just come back after reboot recovery
all that way doesn't work
my Xperia unable to boot right know :crying:
maybe i'll try search what's file that create this??? postrecoveryboot.sh
where's boot script locate???
any help would be apreciated
InAMovies said:
my Xperia unable to boot right know :crying:
Click to expand...
Click to collapse
Thanks for that much information. :good:
A possible 'emergency solution' so that your device reboots again could be attached link.
What really surprised me, no one else has this ERROR: 2, and if not, why not?
http://www.flashtool.net/index.php
You can fix this 'postrecoveryboot.sh' Error 2 with a lower version twrp
I use twrp 2.8.7 which has been uploaded by someone from here androidfilehost.com/?fid=24052804347811669
flash with "fastboot flash boot boot.img" only if you UB, on LB try downgrade your twrp version
and then via file manager, just chmod the file bootrec-device located at sbin folder with read only access
my phone can only be booted only with rom existenz, and it was frequently rebooted and my battery status is unclear, sometimes 65% during the initial boot, and then only a 5% reboot afterwards
I have flash using flashtool with many based rom from 10.5.1.A, 10.6.1.A, 10.7.1.A latest, but it still does not make my phone work just to show sony screen flickered and died with the indicator is still red
all the problems occurred after I had this problem 'postrecoveryboot.sh' Error 2
I still do not know how to turn off the script, when I delete the file after reboot definitely go back there
hoping my phone can be normal again sometime
InAMovies said:
I still do not know how to turn off the script, when I delete the file after reboot definitely go back there
Click to expand...
Click to collapse
Could the cause for the error be a kind of provider branding?
So deeper implemented than the usual firmware.
My device was delivered via German Telekom.
[B]Solution![/B]
After installing Multirom v33 the error message is gone!
Dont ask why, both recoverys, the new one into the FOTA partition from attached link und the older, normal one 3.0.2.0 are error-free! :good:
https://forum.xda-developers.com/xperia-z/orig-development/mod-multirom-v33x-xperia-z-t3432385
I have installed the Modified recovery FOTA, before this error happen all working fine any custom rom working
but after this error, i can boot into recovery and install rom then reboot got bootloop, charger just show blip screen logo
just wanna try your idea with the Multirom v33 non modified
MichaBit said:
Google has no answer for me.
Every time I enter into the recovery and push the message button I get this ERROR: 2.
Everything works fine, its latest TWRP 3.0.2.
Could you tell me something about this error message 2?
What is 'postrecoveryboot.sh'?
How can I get this red message off / without error?
thanx in advance
Click to expand...
Click to collapse
Can You be so Kind to tell me how to flash in the correct way the latest version of TWRP with no error? Thank You very much!!
Ricky_Karmator said:
Can You be so Kind to tell me how to flash in the correct way the latest version of TWRP with no error? Thank You very much!!
Click to expand...
Click to collapse
Download latest recovery 'twrp-3.0.2-0-yuga.img' from link 1.
Put it to your Phone, turn of, push volume + and insert USB-cable for flashmode.
Blue LED-light appears.
Type -fastboot flash boot boot.img
-fastboot reboot
in ADB-connection CMD on your PC --> thats all.
Optional you can use the Tool in link 2.
*Flashing recovery successfully*
https://dl.twrp.me/yuga/
https://twrp.me/app/
MichaBit said:
Download latest recovery 'twrp-3.0.2-0-yuga.img' from link 1.
Put it to your Phone, turn of, push volume + and insert USB-cable for flashmode.
Blue LED-light appears.
Type -fastboot flash boot boot.img
-fastboot reboot
in ADB-connection CMD on your PC --> thats all.
Optional you can use the Tool in link 2.
*Flashing recovery successfully*
https://dl.twrp.me/yuga/
https://twrp.me/app/
Click to expand...
Click to collapse
I wa sure to copy the .img file in "platform-tools" folder in my PC and with cmd type "-fastboot flash boot boot.img" and not to have the file inside the internal memory of my Xperia Z. Obviously i think to rename "Twrp-3.0.blablabla" into boot.img
Ricky_Karmator said:
I wa sure to copy the .img file in "platform-tools" folder in my PC and with cmd type "-fastboot flash boot boot.img" and not to have the file inside the internal memory of my Xperia Z. Obviously i think to rename "Twrp-3.0.blablabla" into boot.img
Click to expand...
Click to collapse
Yes, very correct, copy and rename the file into 'boot.img' to your ADB-folder and flash it. :angel:
Finally with some free time i unlocked and flash the latest TWRP on my old Xperia Z. And yes i've got the same error "ERROR: 2". But everything works from backup to restore and flash Custom ROM. So i think we can nevermind about that
I have the same.
Sometimes my phone randomly reboot, and seems to be some app cause this reboots.
It was happend more and more often. And suddenly couple days ago my phone start to bootloop (just endlesly booting at xperia logo).
I have F5121 stock 8.0 Oreo and done all like in this manual https://forum.xda-developers.com/t/...els-latest-34-4-a-2-118-25-sept-2018.3594502/
So I was have rooted kenrnel twrp 3.2.3.0+DRM-Fix +magisk +FCS_1.3 +debloat script.
Almost 2 years of no problems and this surprise.
When I load to twrp and press menu button i see this:
Updating partition details...
...done
Unable to mount storage
So I was trying do backup of all partitions and after that I go in in wipe menu => advanced wipe => checkbox cache partition => fix patition
than I try to fix all patitions - it doesn't help.
So I do this:
wipe menu => advanced wipe => checkbox data partition => change to exFAT filesystem then => change back to EXT4 filesystem and restore data from backup. And do system/data partitions
and try to restore my backup - and it don't work.
EVEN my older backups don't works - I always become bootloop on xperia logo.
When I download twrp backup to PC and unpack cache.ext4.win\recovery I see file with name last_log.
Thats how last strings of file last_log look like:
~
ro.bootimage.build.date.utc=1533015130
ro.bootimage.build.fingerprint=Sony/omni_suzu/suzu:8.1.0/OPM4.171019.021.R1/4:eng/test-keys
ro.bootloader=s1
ro.debuggable=1
ro.property_service.version=2
init.svc.adbd=running
init.svc.ueventd=running
init.svc.recovery=running
init.svc.ldconfigtxt=stopped
init.svc.set_permissive=stopped
twrp.crash_counter=0
keyguard.no_require_sim=true
tombstoned.max_tombstone_count=50
Running boot script...
I:/sbin/postrecoveryboot.sh process ended with RC=0
Done.
I would like to hear some ideas why that may happen (Unable to mount storage). Coz i lost part of my data and don't wanna have the same experience again and again in future.
Related
"Cyanogendmod.Org / Install CM for z3c / Unlock Your Xperia Z3 Compact" <--- That's the URL somehow.
Followed this instruction. Got myself the 12.1 .zip and .img.
I get error installaing the .zip and the .img isn't even an option:
The old rom is infinitly loading in that blue/purple wave line.
I then turn the phone off by holding down the power button until the phone restarts.
My history:
>Pressing up and down on the button rockers.
>Cyanogen Recovery starts.
>I choose "Wipe data/factory reset".
>I choose "Apply update".
(Apply from ADB doesn't work as it seems as ADB has no access for USB debugging. That's why install it from an external SD)
>Install "cm-12.1-20160918-NIGHTLY-z3c.zip" or its copy that I named "update.zip".
Error message:
[CAN'T POST PICTURE BECAUSE XDA HAS VERY FUNNY MEME RULES XDDD]
Private message maybe...? Can I send you guys URL pics via PM?
How can I get out of this loop?
If you want to go back to stock, use flashtool and flash whatever version you want (FTF method), I had an issue with flashing CM too, it said this is for aries but this device is z3c etc. Is this your problem?
marshalpear said:
If you want to go back to stock, use flashtool and flash whatever version you want (FTF method), I had an issue with flashing CM too, it said this is for aries but this device is z3c etc. Is this your problem?
Click to expand...
Click to collapse
I definitly want CyanogenMod 12.1 on my Z3C. Is it still possible?
I hope you can decypher the URL h t t p : / / t i n y u r l . c o m / j 6 4 u 8 u a
Few things you can do:
1- Download the ROM again, might be corrupted download.
2- Flash Lollipop FTF(not necessary), Flash TWRP recovery, boot into recovery, (If it asks, swipe to allow modifications to system), wipe everything (system,cache,dalvik,data), flash the ROM through TWRP recovery.
3- If it gives the error that I talked about in my first message, let me know.
marshalpear said:
Few things you can do:
1- Download the ROM again, might be corrupted download.
2- Flash Lollipop FTF(not necessary), Flash TWRP recovery, boot into recovery, (If it asks, swipe to allow modifications to system), wipe everything (system,cache,dalvik,data), flash the ROM through TWRP recovery.
3- If it gives the error that I talked about in my first message, let me know.
Click to expand...
Click to collapse
I tried #1 but I'm already stuck with the "SONY XPERIA" blackscreen at the very beginning when booting the smartphone. I suppose it's because of the failed installation and the not choosing of "Wipe clean/factory reset".
I hope that still doesn't count as bricking. I let the accumulator run dry and reload the battery and try to get into the Cyanogenmod Recovery again. Right now nothing is possible. =/
I hope that doesn't count as bricking. If so: These special OTG USB thingies fix a lot I heard, should I get myself one?
SYLVER SECOND said:
I tried #1 but I'm already stuck with the "SONY XPERIA" blackscreen at the very beginning when booting the smartphone. I suppose it's because of the failed installation and the not choosing of "Wipe clean/factory reset".
I hope that still doesn't count as bricking. I let the accumulator run dry and reload the battery and try to get into the Cyanogenmod Recovery again. Right now nothing is possible. =/
I hope that doesn't count as bricking. If so: These special OTG USB thingies fix a lot I heard, should I get myself one?
Click to expand...
Click to collapse
If you are on CM recovery, then there is the problem. AFAIK you can't flash anything through that, so you have to push TWRP on your device using fastboot and then flash AOSP/CM rom you want.
SYLVER SECOND said:
I tried #1 but I'm already stuck with the "SONY XPERIA" blackscreen at the very beginning when booting the smartphone. I suppose it's because of the failed installation and the not choosing of "Wipe clean/factory reset".
I hope that still doesn't count as bricking. I let the accumulator run dry and reload the battery and try to get into the Cyanogenmod Recovery again. Right now nothing is possible. =/
I hope that doesn't count as bricking. If so: These special OTG USB thingies fix a lot I heard, should I get myself one?
Click to expand...
Click to collapse
That's called a soft-brick. You should install the ADB drivers for your phone on your PC and then download TWRP for your phone (.img file) and rename the TWRP you downloaded to recovery.img .
You should put the recovery.img into the folder where your ADB drivers are installed, then Shift + RClick on that folder then select Open Command Window Here. Connect your phone in fastboot mode to your PC (Keep Vol. Up button then plug in your device). Type the following commands:
fastboot flash boot recovery.img
fastboot reboot
If you've done it all correctly, your phone should boot into TWRP recovery. From there you should go to wipe-advanced wipe and wipe your Cache,Dalvik Cache, System, Boot. DO NOT REBOOT NOW. You should go back to main menu and choose install, then choose the ROM you want to install. It should flash it if you don't have a corrupted file. After flashing, you can safely reboot your phone, don't forget to flash GApps if you want Google features on your Cyanogen, hope I helped!
More info about my error:
h t t p : / / t i n y u r l . c o m / z b e v y u 2
Each version of step #3 doesn't work. Still trying to figure out how to get TWRP...
marshalpear said:
That's called a soft-brick. You should install the ADB drivers for your phone on your PC and then download TWRP for your phone (.img file) and rename the TWRP you downloaded to recovery.img .
You should put the recovery.img into the folder where your ADB drivers are installed, then Shift + RClick on that folder then select Open Command Window Here. Connect your phone in fastboot mode to your PC (Keep Vol. Up button then plug in your device). Type the following commands:
fastboot flash boot recovery.img
fastboot reboot
If you've done it all correctly, your phone should boot into TWRP recovery. From there you should go to wipe-advanced wipe and wipe your Cache,Dalvik Cache, System, Boot. DO NOT REBOOT NOW. You should go back to main menu and choose install, then choose the ROM you want to install. It should flash it if you don't have a corrupted file. After flashing, you can safely reboot your phone, don't forget to flash GApps if you want Google features on your Cyanogen, hope I helped!
Click to expand...
Click to collapse
K, 90% of this works. I got the TWRP "app" and I cleaned the cache and all that, but I had to reboot. You see:
To transfer new media I need to remove my external SD from the z3c to my old LG. The LG is connected with my PC and is therefore a kind of card-reader. I tried 2 different nightly thingies.
I still get extraction errors, see:
h t t p : / / t i n y u r l . c o m / h j j d 4 o b
I downloaded 2 different nightlies 6 times already. I dunno. Somethings off here.
Also: For what is the recovery.img? Should I install it afterwards?
I have to restart the phone in order to replug the SD card and get recognigzed by the TWRP.
I did everything from this:
http://forum.xda-developers.com/showthread.php?t=2522762
Because of Error 7.
Now I get Error 6.....
SYLVER SECOND said:
K, 90% of this works. I got the TWRP "app" and I cleaned the cache and all that, but I had to reboot. You see:
To transfer new media I need to remove my external SD from the z3c to my old LG. The LG is connected with my PC and is therefore a kind of card-reader. I tried 2 different nightly thingies.
I still get extraction errors, see:
h t t p : / / t i n y u r l . c o m / h j j d 4 o b
I downloaded 2 different nightlies 6 times already. I dunno. Somethings off here.
Also: For what is the recovery.img? Should I install it afterwards?
I have to restart the phone in order to replug the SD card and get recognigzed by the TWRP.
I did everything from this:
http://forum.xda-developers.com/showthread.php?t=2522762
Because of Error 7.
Now I get Error 6.....
Click to expand...
Click to collapse
OK, your problem is that you messed up your system, so wiping it is not gonna solve this issue. You need to download a stock firmware file (an FTF file) and flash it through Flashtool, because your device name seems to be "." which is why you were getting "error 7". As for the recovery.img, you will use it to flash TWRP recovery on your phone. TWRP app doesn't work correctly if you don't flash it to your recovery partition so do as follows:
1- Download Flashtool, install the drivers of your device for Flashtool (you can search it on xda forums), download an FTF file, any of them should do, but as you will install CM 12.1, I recommend a Lollipop FTF.
2- Flash the firmware through Flashtool. This will turn your phone into a stock one. Unlock your bootloader if you haven't already, which I believe you have.
3- Flash the TWRP recovery through fastboot (follow my earlier instructions)
4- After you open TWRP recovery do the wipes, note that you can still connect your phone to your computer for file transfers in TWRP Recovery.
5- Install the CM zip file through recovery
IF YOU GET ERROR 7 SAYING :this package is for device: D5803, D5833, z3c; this device is aries.
7- Open the CM 12.1 zip file on your computer and proceed to META-INF/com/google/android directory.
8- In that folder you should see "updater-script", extract it to somewhere and open it with Notepad.
9- Once you open it press Ctrl + H to change some of the lines.
10- Write "D5833" without the quotation marks in the first space and write "aries" without the quotation marks into the second space and click replace all.
(This will change all "D5833" to "aries" in the file therefore making it usable for your device) Save the file and put it into the directory of where you found it, replace it with the original.
11- Now put the edited .zip file into your phone storage, and flash it through recovery. It should work. :good:
marshalpear said:
3- Flash the TWRP recovery through fastboot (follow my earlier instructions)
Click to expand...
Click to collapse
I think he shouldn't flash TWRP on boot partition, as you wrote. That might cause further issues. I am flashing my recovery through fastboot without problems using next command:
fastboot flash recovery recovery.img
Cirra92 said:
I think he shouldn't flash TWRP on boot partition, as you wrote. That might cause further issues. I am flashing my recovery through fastboot without problems using next command:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
It won't matter. Because when he flashes the CM, it'll flash the CM Recovery along with it.
marshalpear said:
It won't matter. Because when he flashes the CM, it'll flash the CM Recovery along with it.
Click to expand...
Click to collapse
Yea I know, but before that, he needs to have a working TWRP on right partition to be able to even flash any rom.
Cirra92 said:
Yea I know, but before that, he needs to have a working TWRP on right partition to be able to even flash any rom.
Click to expand...
Click to collapse
That's why I wrote those steps for him/her to follow. If you flash TWRP to boot partition, when you boot the phone, it will go straight into TWRP. If you flash it to recovery partition, you'll have to boot it manually.
marshalpear said:
That's why I wrote those steps for him/her to follow. If you flash TWRP to boot partition, when you boot the phone, it will go straight into TWRP. If you flash it to recovery partition, you'll have to boot it manually.
Click to expand...
Click to collapse
Logical step, didn't think about it that way, I assumed OP knew how to enter recovery
"1- Download Flashtool, install the drivers of your device for Flashtool (you can search it on xda forums), download an FTF file, any of them should do, but as you will install CM 12.1, I recommend a Lollipop FTF.
2- Flash the firmware through Flashtool. This will turn your phone into a stock one. Unlock your bootloader if you haven't already, which I believe you have.
3- Flash the TWRP recovery through fastboot (follow my earlier instructions)
4- After you open TWRP recovery do the wipes, note that you can still connect your phone to your computer for file transfers in TWRP Recovery.
5- Install the CM zip file through recovery
IF YOU GET ERROR 7 SAYING :this package is for device: D5803, D5833, z3c; this device is aries.
7- Open the CM 12.1 zip file on your computer and proceed to META-INF/com/google/android directory.
8- In that folder you should see "updater-script", extract it to somewhere and open it with Notepad.
9- Once you open it press Ctrl + H to change some of the lines.
10- Write "D5833" without the quotation marks in the first space and write "aries" without the quotation marks into the second space and click replace all.
(This will change all "D5833" to "aries" in the file therefore making it usable for your device) Save the file and put it into the directory of where you found it, replace it with the original.
11- Now put the edited .zip file into your phone storage, and flash it through recovery. It should work."
K, so I guess I'm finished with #1 and #2. Sorry, had a ****-ton of chores to do. Before I progress, I wanted to send you guys
this pic:
https://img3.picload.org/image/rdricord/unbenannt.png
Is the root access necessary, or can I progress?
That's the sites I've used, if anybody wonders why something is the way it is right now:
http://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
http://forum.xda-developers.com/showpost.php?p=66275965&postcount=2029
http://forum.xda-developers.com/showpost.php?p=60001557&postcount=829
Von "Sony Mobile Flasher by Androxyde":
"23/023/2016 22:23:52 - INFO - Root access denied
23/024/2016 22:24:07 - ERROR - Illegal key size or default parameters
23/024/2016 22:24:12 - ERROR - Illegal key size or default parameters
23/024/2016 22:24:13 - WARN - Please check your Phone and 'ALLOW' Superuseraccess!
23/024/2016 22:24:14 - INFO - Root access denied"
FlashTool says the firmware has been flashed so I don't understand what are you trying to do after that? After flashing the FTF file you should flash TWRP through "FASTBOOT". Then follow the instructions.
K, did everything you said. Read everything five-times. Replaced "D5833" to "aries" and all that stuff. Still getting ERROR 7.
The phone is still in TWRP Recovery from FASTBOOT / BOOTLOAD because I "constantly" charge it to stay in recovery. If I had found this Mount option earlier... kinda feel stupid for that. So I still get ERROR 7. I copied the modified .zip to internal storage and SD card to see if I get the same error twice. And yeah.
Exact error message in red letters:
"Updater process ended with ERROR: 7
Error installing zip file ' /external-sd/cm-12.1-20160918-NIGHTLY-z3c.zip'
Updating partition details...
... done"
So I forethought and cleaned the cache and need somewhat new instructions.
Also:
I suppose with "Advanced Wipe" and your instructions you meant this points, right?:
http://tinyurl.com/jc5rv3a
SYLVER SECOND said:
K, did everything you said. Read everything five-times. Replaced "D5833" to "aries" and all that stuff. Still getting ERROR 7.
The phone is still in TWRP Recovery from FASTBOOT / BOOTLOAD because I "constantly" charge it to stay in recovery. If I had found this Mount option earlier... kinda feel stupid for that. So I still get ERROR 7. I copied the modified .zip to internal storage and SD card to see if I get the same error twice. And yeah.
Exact error message in red letters:
"Updater process ended with ERROR: 7
Error installing zip file ' /external-sd/cm-12.1-20160918-NIGHTLY-z3c.zip'
Updating partition details...
... done"
So I forethought and cleaned the cache and need somewhat new instructions.
Also:
I suppose with "Advanced Wipe" and your instructions you meant this points, right?:
http://tinyurl.com/jc5rv3a
Click to expand...
Click to collapse
OK, so try flashing TWRP to recovery partition to get you out of TWRP after you boot by writing these commands in the ADB:,
fastboot flash recovery recovery.img
fastboot reboot recovery
This will flash the TWRP to recovery partition and will boot you into TWRP. As you do this you won't have a go at the recovery again but for this time. You can reach the TWRP by pressing the Vol. Down button when the phone vibrates at the boot. Also if you want to force shutdown your phone you can use Vol. Up + Power Button combination for a few secs.
marshalpear said:
OK, so try flashing TWRP to recovery partition to get you out of TWRP after you boot by writing these commands in the ADB:,
fastboot flash recovery recovery.img
fastboot reboot recovery
This will flash the TWRP to recovery partition and will boot you into TWRP. As you do this you won't have a go at the recovery again but for this time. You can reach the TWRP by pressing the Vol. Down button when the phone vibrates at the boot. Also if you want to force shutdown your phone you can use Vol. Up + Power Button combination for a few secs.
Click to expand...
Click to collapse
K, cool feature. Got it all set up now, but back to the main subject:
Is it even possible to install CyanogenMod 12.1 on Sony Z3C?
I must note: I use linux. I only used Windows because SPFT Linux version gave me a chip mismatch error I couldn't fix easily.
1: Please read. It explains what problems might arise. Especially post #6 and #13.
2: There are 2 versions of the scatter file. The MT6735 version is what I used successfully. The MT6737Tmod version is what comes from post #6 & #13.
3: Please use each scatter file to Readback your boot and recovery partitions first, renaming as fit, so you can have a backup BEFORE ANYTHING. Then test unpacking them to see if everything went correctly. Then readback every partition in the scatter file so you don't have to depend on the stock ROM for a backup. I didn't and it led me to take this route.
3: Seem to be a difference in the naming of the scatter file and sizes of system, cache, and userdata inside from the stock ROM and what works..
4: DO NOT choose Format+Download until you know which scatter file works, unless you want to chance a Hard Brick.
5: Wiping the dalvik and cache in stock recovery before flashing TWRP seems to be the best thing to do to avoid boot loops or a hung boot.
THIS ROOT PROCESS WAS DONE OVER THREE DAYS OF CAR WORK, DRIVING, FAMILY, AND COMPUTER WORK. MOST OF THE TIME SPENT WAS THIS MORNING TRYING TO GO TO SLEEP. DIDN'T HAVE TIME TO DOCUMENT AND TAKE PICTURES. THIS WRITE-UP IS FROM WHAT I REMEMBER DURING THIS PROCESS. IF I CAN REMEMBER SOME VAGUE DETAIL THAT YOU NEED, GOOD. IF NOT, DON'T STRESS ME. THE HARD PART IS DONE. A GOOGLE SEARCH OF SOME OF THESE PROGRAMS WILL GET QUICKER RESULTS IF YOU DON'T HAVE THEM. THE MAIN THING NEEDED FROM MY RESEARCH WAS THE SCATTER FILE. LINKS FOR SCATTER FILE AND RECOVERY IMAGE ARE BELOW.
Looking for a way to root first day getting this phone in February. Read this post last Tuesday about MT67xx rooting, thanks lsemprini. Spent two days finding which versions of the programs work with this phone, already had the ROMs, drivers, and tools. Dove right in.
I downloaded the ROM from needrom. Scatter file was unusable. Wrong chip error. Phone reads MT6735 scatter file read MT6737. Did a manual diff. Used SP Flash Tool v5.1524 to flash, formatted instead of downloading by mistake, cord got pulled, Hard brick. Fought with Windows7 to get drivers to recognize a hard brick. Still don't know how I did it but it read then flashed. Looked like another hard brick but SPFT would recognize it for the Memory Test. I just held power+vol_down with just charging block power to get it to come on. Sometimes just one of the buttons was enough to get it to power on and start a bootloop. Took two minutes sometimes. Flashing the wrong recovery led to bootloops. Starting SP Flash Tool and plugging in the USB to the phone as soon as it powers off during a loop will let the preloader "register" and the images to be flashed. Flashing from a stock ROM will lead to IMEI being erased. Used SN Write Tool v1.1716 to write the IMEI numbers. Got them from the side of the box. The MD1_DB and AP_DB files needed are in the stock rom.
Ported TWRP, credit to jemmini for the post https://forum.xda-developers.com/vivo-xl/development/recovery-t3311601. Used that recovery as a base. Ported according to the myriad of guides that I have been reading over the past few days. None of them worked as instructed, had to modify trial and error style. Finally got TWRP to read the internal partitions AND remain after a reboot. A lot was going on when I did this. Not sure if I formatted before, I remember flashing a lot of because of something. I mounted the system just in case & flashed SuperSu from chainfire's website, no formatting afterwards. Rebooted and installed SuperUser and BusyBox. I tried adb and fastboot. They work but not for everything. Hooked phone up to computer with debugging enabled.
Code:
adb root
gives a shell, no errors unlike before. Edit: ADB won't let me start as root anymore.
Needed files
Blu Vivo XL2 TWRP 3 Recovery
MT6735 Scatter File
MT6737T Scatter File
BLU Vivo XL2 V0070UU Stock ROM if you don't have a backup of your partition images.
Step 1
Install Minimal ADB and Fastboot and USB VCOM drivers.
Download SP Flash Tool, SN Write Tool, scatter file, and twrp3.0 to a working folder.
Download SuperSu zip & SuperUser apk then put them on your SD Card.
Install SD card into phone.
Step 1.A For Full ROM Flash and IMEI Write
Download Stock ROM and extract to working folder.
Move twrp3.0 to ROM folder.
Step 2
Install SP Flash Tool and SN Write Tool and run.
Step 3 To flash TWRP only
Reboot phone to recovery then wipe cache and dalvik. Can't remember if it is a dalvik option in the stock recovery now.
Power off phone. Make sure it is not plugged up to the computer.
IN SP Flash Tool:
Load scatter file that works from working folder.
Make sure download only is selected in drop down menu.
Check only the recovery partition box and click the name of the recovery file on the same line.
Browse to TWRP recovery image and select.
Click the Download button with the green arrow.
Plug phone into computer and wait until window with OK pops up. Success.
Step 3.B OPTIONAL
Select format and flash all using stock ROM or images backed up from your phone.
Stock ROM must be extracted and custom recover put into same folder and renamed to "recovery.img" to make
everything automatically load.
Click the Download button with the green arrow.
Plug phone into computer and wait until window with OK pops up. Success
Step 4 Only needed when formating+downloading ROM
With phone still powered off and unplugged, write IMEI numbers using SN Write Tool.
Step 4.A
Click System Config.
Select IMEI in Write Option Area.
Make sure IMEI Checksum and Dual IMEI are checked.
Load MD1_DB and AP_DB files from ROM folder.
Click Load Modem DB from DUT box.
Click Save.
Step 4.B
Click Start.
Input your IMEI numbers from box.
Click OK. Success
Step 5
Boot to recovery.
Swipe to make permanent.
Wipe dalvik and cache.
Flash SuperSu..
Reboot.
Install SuperUser apk and BusyBox of your choice.
Step 5.A
If SuperUser apk or any app that ask for root permission cannot get it, reboot to recovery.
Mount system partition: Shouldn't matter but it worked for me.
Flash SuperSu zip again.
Reboot.
Install SuperUser apk and BusyBox of your choice.
ENJOY
When i connect the device after clicking download, it says "CHIP TYPE NOT match!"
mind you the device is off, i tried to troubleshoot but still getting the same error.
any help would be appreciated
UPDATE: Im thinking it has to be the scatter file, but im not sure.
UPDATE: I got it to work, after flashing superSU, my phone wont boot past the initial white Blu start screen.
[QUOTEUPDATE: I got it to work, after flashing superSU, my phone wont boot past the initial white Blu start screen.[/QUOTE]
Try powering it off, booting to recovery and then wiping dalvik and cache.
The longest it took to get past that logo was 15 minutes. It is either encrypting or decrypting. Didn't get any type of messages until after root, and those were optimizing messages. Only one came through before rooting when I interrupted the boot process and that was about encrypting the phone. Phone was encrypted before root, now it is decrypted. Could have something to do with that. Try wiping the cache and dalvik after flashing. I actually flashed it three times in a row. The third was after mounting storage then flashing the SuperSu zip. Once you see the next logo with the colorful circles and hear the sound it might be another wait. That is where it let me know it was optimizing.
I must note: Please use scatter file to Readback your partitions so you can have a backup BEFORE ANYTHING. I didn't and it led me to take this route.
=smith901;72841007][QUOTEUPDATE: I got it to work, after flashing superSU, my phone wont boot past the initial white Blu start screen.
Click to expand...
Click to collapse
Try powering it off, booting to recovery and then wiping dalvik and cache.
The longest it took to get past that logo was 15 minutes. It is either encrypting or decrypting. Didn't get any type of messages until after root, and those were optimizing messages. Only one came through before rooting when I interrupted the boot process and that was about encrypting the phone. Phone was encrypted before root, now it is decrypted. Could have something to do with that. Try wiping the cache and dalvik after flashing. I actually flashed it three times in a row. The third was after mounting storage then flashing the SuperSu zip. Once you see the next logo with the colorful circles and hear the sound it might be another wait. That is where it let me know it was optimizing.
I must note: Please use scatter file to Readback your partitions so you can have a backup BEFORE ANYTHING. I didn't and it led me to take this route.[/QUOTE]
chip type not match. pls help
---------- Post added at 10:46 AM ---------- Previous post was at 10:41 AM ----------
ANJIII said:
chip type not match. pls help
Click to expand...
Click to collapse
what version of stock rom did you use? there are 3 versions in needrom; v7, v11, and v12. i use v11 cause of automatic update
ANJIII said:
chip type not match. pls help
---------- Post added at 10:46 AM ---------- Previous post was at 10:41 AM ----------
what version of stock rom did you use? there are 3 versions in needrom; v7, v11, and v12. i use v11 cause of automatic update
Click to expand...
Click to collapse
i solved my own problem hahaha. just rename the file to mt6737t instead of mt6735. also edit the platform in scatter file. change it to mt6737t too then install your supersu with the use of twrp then wipe dalvic then its done
ANJIII said:
i solved my own problem hahaha. just rename the file to mt6737t instead of mt6735. also edit the platform in scatter file. change it to mt6737t too then install your supersu with the use of twrp then wipe dalvic then its done
Click to expand...
Click to collapse
Good. I had to name it that because of the chip mismatch error. It was from the V7 ROM. The other two are updates. I also messed up big time along the way. My phone always read MT6735 but it does have MT6737T in different files. I always wondered about that. I got it to work without buying another phone.
It seem that the phone boot logo never goes away. What should I do now?
Alexis96312 said:
It seem that the phone boot logo never goes away. What should I do now?
Click to expand...
Click to collapse
Hope you Readback your original recovery and other partitions. I didn't and worked hard to get it back. When I just flashed the recovery and something went wrong, it reverted back to the stock recovery.
Try doing this:
1. Start SPFT with the reçovery you want to flash.
2. Hold down the power button. AS SOON AS IT VIBRATES, PLUG THE USB CORD IN.
3. Hopefully you timed it right and it will flash and boot.
Sometimes it took 15 minutes to get past the boot logo.
Here what I did so far
1. Format using SP Flash Tool
2. Download /// By Using Scatter-Loading Files (MT6737T_Android_scatter.txt {From Rom}) Which it check all the boxes AUTO ///// It works but I didn't change the recovery.img like TWRP.img
Download it
It works normal.
___________________________________
But I want TRWP.img to be my recovery for root (SuperSU)
I try SP Flash Tool to change the recovery img to TRWP.img /// Using Scatter-Loading Files (MT6737T_Android_scatter.txt {From Rom}) I UNCHECK ALL BUT RECOVERY.IMG
Before this happen I didn't factory reset or Format anything yet.
It work to Recovery.img but THE BLU LOGO IS STILL LONG
I feel like it not working
Help Help Help ME
Please
Alexis96312 said:
Here what I did so far
1. Format using SP Flash Tool
2. Download /// By Using Scatter-Loading Files (MT6737T_Android_scatter.txt {From Rom}) Which it check all the boxes AUTO ///// It works but I didn't change the recovery.img like TWRP.img
Download it
It works normal.
___________________________________
But I want TRWP.img to be my recovery for root (SuperSU)
I try SP Flash Tool to change the recovery img to TRWP.img /// Using Scatter-Loading Files (MT6737T_Android_scatter.txt {From Rom}) I UNCHECK ALL BUT RECOVERY.IMG
Before this happen I didn't factory reset or Format anything yet.
It work to Recovery.img but THE BLU LOGO IS STILL LONG
I feel like it not working
Help Help Help ME
Please
Click to expand...
Click to collapse
Try flashing stock ROM, wipe data in stock recovery, then flashing TWRP, wipe dalvik.
If that don't work, wipe data then flash stock ROM with TWRP recovery, wipe dalvik.
The scatter file from the stock ROM gave me problems. Had to modify mine.
Don't forget to restore your IMEI afterwards since you formatted+flashed.
I will try
---------- Post added at 08:33 PM ---------- Previous post was at 08:23 PM ----------
I did try it but it seem not to do anything
Can you be so kind to upload the mod Scatter File Please
Alexis96312 said:
I will try
---------- Post added at 08:33 PM ---------- Previous post was at 08:23 PM ----------
I did try it but it seem not to do anything
Can you be so kind to upload the mod Scatter File Please
Click to expand...
Click to collapse
The one I attatched on the first post #1 is my modified scatter file. The mods included changing the size to the system, cache, and userdata. Just compared all three. The stock MT6737T scatter file and the V12 ota scatter are the same. The one I changed, MT6735, have the file name, platform name, and partition changes. I don't know why I had to modify it., especially the size parts. It all worked when I did that. I basically gave up on it because of a hard brick. Then I remembered reading MT6735 in some file a few months back while roaming the file system. Made the changes and was back in business. Maybe you need the stock scatter file, here it is.
It's what the end result of this post @ANJIII did minus the size changes..
He just did the name changes and it worked for him. Ya'll seem 180° from where I was.
The second one is from the V12 OTA update. It is very minimal, must be all that is needed for a scatter file. Not really sure tho. Hope it is just scatter file issues.
As long as SPFT is reading your phone, it's still a chance on it all working out. That is how I viewed it.
@andromedaXVIII Don't know if you got it working. This might be a potential solution.
Unable to find partition for path '/sdcard'
Unable to find partition for path '/sdcard'
Unable to find partition for path '/sdcard'
Updating partition details...
Failed to mount '/protect_f'(Invalid argument)
Failed to mount '/protect_s'(Invalid argument)
Failed to mount '/nvdata' (Invalid argument)
...done
Full SELinux support is persent,
MTP Enable
Wiping Dalvik Cache Directories...
--Dalvik Cache Directories Wipe Complete!
Formatting Cache using make_ext4fs..
Updating partition details...
Failed to mount '/protect_f'(Invalid argument)
Failed to mount '/protect_s'(Invalid argument)
Failed to mount '/nvdata' (Invalid argument)
..done
Is this good or bad? This is in Twrp recovery
Alexis96312 said:
Unable to find partition for path '/sdcard'
Is this good or bad? This is in Twrp recovery
Click to expand...
Click to collapse
I take it TWRP flashed successfully, it is having a problem reading those four partitons. Possibly encryption is stopping you. Try flashing this in TWRP before anything else to remove the encryption.
I didn't get any errors. I know the userdata partition was different in the scatter files. That could be the reason for /sdcard not being recognized. Must be a difference in the layout of phones, not really sure. My protect_s, protect_f, and nvdata partitions and /sdcard all mount fine, pictures attached. I am able to do a backup in TWRP. I have been playing around with porting different ROMs and came across an issue similar to this. Had to change some lines in updater-script.
I checked fstab.mt6735 file in the stock recovery, the modded twrp3 recovery, and stock boot recovery to make sure I didn't make any typos or leave anything out. They all have the same lines. Had to do this:
Code:
("ext4", "EMMC", "/dev/block/mmcblk0p5", "/system")
in the updater-script I was working on. I got ahead of myself flashing a ROM and was stuck on the 1st logo screen. Held power+vol_down to get it unstuck. Yes I was all calling myself kind of names like I'm sure some people have done following this guide.
Which scatter file you used? Did you do a readback in SPFT with the WORKING scatter file and mount one of those images to check if you can read and write the files. I mounted system.img from the stock ROM to make sure I could read and write the files before I started with flashing. I'm thinking there is are internal differences in the XL2s. You might have to reflash using the stock ROM with TWRP as the recovery with the Format+Download option since you got TWRP installed.
Once I get through playing around with trying to flash this ROM, I will restore and try to find all the partition mappings and update TWRP to work with the format from the updater-script and see if that work. Will let you know what happened.
Alexis96312 said:
Unable to find partition for path '/sdcard'
Unable to find partition for path '/sdcard'
Unable to find partition for path '/sdcard'
Updating partition details...
Failed to mount '/protect_f'(Invalid argument)
Failed to mount '/protect_s'(Invalid argument)
Failed to mount '/nvdata' (Invalid argument)
...done
Full SELinux support is persent,
MTP Enable
Wiping Dalvik Cache Directories...
--Dalvik Cache Directories Wipe Complete!
Formatting Cache using make_ext4fs..
Updating partition details...
Failed to mount '/protect_f'(Invalid argument)
Failed to mount '/protect_s'(Invalid argument)
Failed to mount '/nvdata' (Invalid argument)
..done
Is this good or bad? This is in Twrp recovery
Click to expand...
Click to collapse
can you send us your vivo xl2 specs because there are two versions of xl2, V0070UU and V0070EE. Mine is V0070UU. I just did some renaming and editing in the scatter file of MT6735 and it bootloop once after I installed the twrp. I restarted my phone during the bootloop by holding the power button. After that, I opened the twrp to install the supersu then wipe dalvic cache. You may now boot up the phone and it took 10-15mins to use it because the system shows that it optimizes 205 apps(in my case, maybe because I have installed numerous apps). After that my phone is usefull again and I installed V4A because that's the only reason why I wanted to root this phone.
Here is all the information I have pulled so far from the phone. Have a screenshot attached from About device in settings. The attached zip file is all the information I could think to pull using adb . The attached file is my partitionlayout. I just ran cat against every file to see what it would give me and redirected the output. Using adb while the phone is in recovery let me pull and read the files I couldn't while the phone was booted.
@Alexis96312, try to run this command in terminal to get your partition map:
Code:
adb shell "su -c 'ls -l /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/'" > someFileName.txt
I have mine listed in the zip file as partitionLayout.txt It will list which names go to what device in /dev and save it in your current directory. The file can be used to get the correct partition layout on your phone. Post the results and I will repack the recovery to see if it will work for you. You can do it also with Carliv Image Kitchen, it has a menu :good:. You will have to modify the fstab files in the ramdisk folder of the extracted image to what the partition map specifies. I went thru all of them to be sure when I first ported TWRP.
@ANJIII is correct about the different versions, nice catch. I forgot about that. I assumed you had the V0070UU version like mine, fault on me for not asking. Mine specifically says BLU_V0070UU_V07_GENERIC 25-11-2016 09:46. I'm thinking the GENERIC part comes from me having to flash the stock ROM. I think it had BLU_V0070UU_V07 with user/keys before I bricked it and had to flash the stock ROM. Got three extra apps that I instantly removed. Seems like the stock ROM function the same as before bricking flashing stock.
ScreenShot
ANJIII said:
can you send us your vivo xl2 specs because there are two versions of xl2, V0070UU and V0070EE. Mine is V0070UU. I just did some renaming and editing in the scatter file of MT6735 and it bootloop once after I installed the twrp. I restarted my phone during the bootloop by holding the power button. After that, I opened the twrp to install the supersu then wipe dalvic cache. You may now boot up the phone and it took 10-15mins to use it because the system shows that it optimizes 205 apps(in my case, maybe because I have installed numerous apps). After that my phone is usefull again and I installed V4A because that's the only reason why I wanted to root this phone.
Click to expand...
Click to collapse
Answer in pictures
ADB USB
It seem that the computer can't find it what now
Do I need to install the ADB driver again?
I'm trying to do it on stock recovery
Do I have to do it on TWRP recovery?
Alexis96312 said:
It seem that the computer can't find it what now
Do I need to install the ADB driver again
Click to expand...
Click to collapse
It look like the pid:vid aren't recognized correctly. Usually a reboot will help.
Are you connect using adb while in recovery? If so, see if Windows will install new drivers for you. My Linux box read mine as a Samsung at one point. Try running the ls part of the command in TWRP terminal.
This is where I fought with windows when the cord got pulled during flashing. I never got an error like the 2 at the top, always like the bottom one. I kept adding legacy hardware in device manager until one of them worked. The Linux version of SPFT always give a chip mismatch error. Wish it worked so I won't have to boot to Windows.
I kept doing format+download and and plugging the phone in until Windows recognized it because it was in a bootloop when that happened. You need the preloader to be recognized.
Both stock ROMs are on needrom.com. I downloaded the UU version, the EE version is what you might need. I'll pm you a link to my backups from TWRP to see if they will work for you. Same thing happened to me playing with the new ROM. Restoring my boot and system got it back working.
Disable forced encryption of data partition. Get little better performance and internal sd + data mounting in TWRP
Things needed:
Unlocked Max pro with TWRP flashed
Instructions:
1. Download the decrypt.zip and move/copy to sdcard/otg drive
2. Flash in recovery
3. Format /data
4. Reboot
If it fails to boot (bootloop?) flash latest magisk and reboot.
res
First,
We get better performance after flashing this ?
Is this affect to the battery ? Drains or something ?
Greetings
gusbalaa said:
First,
We get better performance after flashing this ?
Is this affect to the battery ? Drains or something ?
Greetings
Click to expand...
Click to collapse
Differences should be minor as max pro has good cpu, but I can't test as i don't have it.
ahhhhhhhhhhhhhhhhhhhhhhh THANKS SIR
i so damn happy !! thanks fix all twrp + root and happy
Hey.....Am still getting bootloop......plz help.
Akky_karan said:
Hey.....Am still getting bootloop......plz help.
Click to expand...
Click to collapse
SD 636 already has hardware acceleration for encryption and decryption so no major effecrts.
Flash decrypt from twrp?
Can i flash decrypt from twrp? Because i already installed twrp on my device.
Sorry for my bad English
unlock.bat file not working
i understand the whole process i click on the unlock.bat file cmd appers and dissapears and nothing happens phone doesnt reboot after some time i reboot my phone manually still no changes in my phone starts normally. am i missing something. do i have to enable usb debugging mode or what?
plz hel
hi
so if i want to leave data partition encrypted, will twrp not be able to mount it?
what about rwrp?
can i just not enter a password when getting into recovery to let recovery read it
if i dont flash this zip, just flash twrp boot into it cancle the password prompt and swipe to modify system and dont change anything in options or flash magisk and reboot into stock does the twrp get replased by stock recovery cause it hapend to me and i am totally confeused on what to do next
it says
E: could not extract 'META-INF/com/google/android/update-binary'
Error installing zip file './external_sd/decrypt.zip'
Hi!!
Can you please also make a force encrypt, in case we want to revert back to encryption?
Thanks.
cant download th decrypt file
cant download th decrypt file
How to unlock unofficially in Ubuntu?
Sudeep Duhoon said:
Disable forced encryption of data partition. Get little better performance and internal sd + data mounting in TWRP
Things needed:
Unlocked Max pro with TWRP flashed
Instructions:
1. Download the decrypt.zip and move/copy to sdcard/otg drive
2. Flash in recovery
3. Format /data
4. Reboot
If it fails to boot (bootloop?) flash latest magisk and reboot.
Click to expand...
Click to collapse
Will this zip wipe everything?
"To start android enter password" (or so, my device not english)
What is the password?
tagilbo said:
"To start android enter password" (or so, my device not english)
What is the password?
Click to expand...
Click to collapse
Your lockscreen code
Prakashgolwalkar said:
i understand the whole process i click on the unlock.bat file cmd appers and dissapears and nothing happens phone doesnt reboot after some time i reboot my phone manually still no changes in my phone starts normally. am i missing something. do i have to enable usb debugging mode or what?
plz hel
Click to expand...
Click to collapse
open cmd and cd to the path containing unlockXXX files and just type unlock .
Hey,
in magisk is "preserve force encryption" shoud be clicked?
Thanks
I was trying to flash the Ozip to restore the stock rom using TWRP and after that boom
damaged boot/recovery that msg
i still can go inside twrp and the fastboot mode
what i did notice is that the file folder name changed to system_root and it was just system bevor
is there any fix for it i am using the CN Version
(how-to unbrick your realme device) fastboot needed fix inside.
I Went totally nuts last night when i bricked my phone so i did figure out my self how to unblock the phone.
First you need to BE ABLE TO ENTER FASTBOOT it won't work without it and you need working TWRP.
First you need to go to TWRP and go to mount and unmount everything and disable MTP.
Then go to Advanced and select Terminal
type in LS make sure there is 2 Folders one called system and one called system_root
make sure that the system folder is empty if empty type in rm -r system
and rename the system_root folder to system using mv system_root system
after that boot into Fastboot mode and Flash your Rom for your Device using the Fastboot Tool
Hope that works for you guys.
System wiped/corrupted. Flash the chinese fastboot rom to fix it via fastboot
The real mistake is when your device brick with locked bootloader, all the other cases are solvable.
HTCDevil said:
The real mistake is when your device brick with locked bootloader, all the other cases are solvable.
Click to expand...
Click to collapse
Yep once you lock you doomed
Funny is my bootloader still unlock and my fingerprint works fine on the stock rom
Sent from my RMX1931 using Tapatalk
natedogg20050 said:
Yep once you lock you doomed
Funny is my bootloader still unlock and my fingerprint works fine on the stock rom
Click to expand...
Click to collapse
That's interesting, i thought it works only if you relock bootloader and then update fw
HTCDevil said:
That's interesting, i thought it works only if you relock bootloader and then update fw
Click to expand...
Click to collapse
Worked perfectly fine even on the old 0.8 firmware
Sent from my RMX1931 using Tapatalk
Can you make a small video please showing this steps? After that terminal thing I didn't understand anything
talalahmed said:
Can you make a small video please showing this steps? After that terminal thing I didn't understand anything
Click to expand...
Click to collapse
I will is your device broken
Sent from my RMX1931 using Tapatalk
What to do when 2 Folders one called system and one called system_root are missing? cant access data in MTP when in TWRP from PC to send the rom file.
natedogg20050 said:
I Went totally nuts last night when i bricked my phone so i did figure out my self how to unblock the phone.
First you need to BE ABLE TO ENTER FASTBOOT it won't work without it and you need working TWRP.
First you need to go to TWRP and go to mount and unmount everything and disable MTP.
Then go to Advanced and select Terminal
type in LS make sure there is 2 Folders one called system and one called system_root
make sure that the system folder is empty if empty type in rm -r system
and rename the system_root folder to system using mv system_root system
after that boot into Fastboot mode and Flash your Rom for your Device using the Fastboot Tool
Hope that works for you guys.
Click to expand...
Click to collapse
hack-os said:
What to do when 2 Folders one called system and one called system_root are missing? cant access data in MTP when in TWRP from PC to send the rom file.
Click to expand...
Click to collapse
Can you enter twrp?
Sent from my RMX1931 using Tapatalk
natedogg20050 said:
I will is your device broken
Click to expand...
Click to collapse
Thanks,I fixed it but not with your steps,it turns out using the Chinese twrp fixed everything for me
Solved.! (For me) CN
I unlocked the bootloader according to the guide [Guide] Guides for x2 Pro[Locking/unlocking bootloader, tweaks and more]. And flashed TWRP successfully. MY MAIN MISTAKE -> DIDN'T MAKE A BACKUP AT THIS POINT.
Then I flash canary debug magisk and open gapps micro (culprit for brick). Then tried to reboot but stuck in yellow Realme screen. Then went back to recovery tried "Facrory reset", "Format data", flash latest CN ozip, even fastboot flash and guide by natedogg20050 with no luck. But Lineage OS unofficial by karthick mostwanted worked with magisk 20.3. :good:
For one final time I tried to get back the stock(since Lineage is still in alpha ATM), after seeing this post by exadeci. Did a "format data" following fastboot flash with chinese images, SUCCESS...!!! :victory: And even updated with ozips from CN site worked.. Finger print works too.
Still in update process to latest .15 . Plan to install magisk.(hopefully canary debug).
Will update this after latest upgrade + magisk install.
don't worry we can
first reboot to recovery
then go to wipe
and wipe sytem,catche,davik catche and data
then download the stock os for realme software
download link(please select your mobile) in realme software website
and flash the recovery
wipe catche and data
and you are back to stock os
enjoy
natedogg20050 said:
I Went totally nuts last night when i bricked my phone so i did figure out my self how to unblock the phone.
First you need to BE ABLE TO ENTER FASTBOOT it won't work without it and you need working TWRP.
First you need to go to TWRP and go to mount and unmount everything and disable MTP.
Then go to Advanced and select Terminal
type in LS make sure there is 2 Folders one called system and one called system_root
make sure that the system folder is empty if empty type in rm -r system
and rename the system_root folder to system using mv system_root system
after that boot into Fastboot mode and Flash your Rom for your Device using the Fastboot Tool
Hope that works for you guys.
Click to expand...
Click to collapse
after do that my phone boot only in TWRP but i can't see anything.
if I connect the phone to the computer it is empty and if I want to transfer something on it gives me an error.
can you help me ?
SOLVED: i formatted by TWRP.
When I type LS in terminal it gives a long list. There is a "system" and a "system_root".
When I try to open "system" with cd system command, it says, no such file or directory. When I enter "cd system_root" it goes into this Folder. But using "ls" command within this Folder it just shows nothing. Am I doing something wrong?
Any idea?
P.S. Yes I can enter fastboot, and TWRP is working.
natedogg20050 said:
I Went totally nuts last night when i bricked my phone so i did figure out my self how to unblock the phone.
First you need to BE ABLE TO ENTER FASTBOOT it won't work without it and you need working TWRP.
First you need to go to TWRP and go to mount and unmount everything and disable MTP.
Then go to Advanced and select Terminal
type in LS make sure there is 2 Folders one called system and one called system_root
make sure that the system folder is empty if empty type in rm -r system
and rename the system_root folder to system using mv system_root system
after that boot into Fastboot mode and Flash your Rom for your Device using the Fastboot Tool
Hope that works for you guys.
Click to expand...
Click to collapse
Sir Backe said:
When I type LS in terminal it gives a long list. There is a "system" and a "system_root".
When I try to open "system" with cd system command, it says, no such file or directory. When I enter "cd system_root" it goes into this Folder. But using "ls" command within this Folder it just shows nothing. Am I doing something wrong?
Any idea?
P.S. Yes I can enter fastboot, and TWRP is working.
Click to expand...
Click to collapse
did you figure it out ?
natedogg20050 said:
did you figure it out ?
Click to expand...
Click to collapse
Thanks for asking! Yes, I did, but in a different way. It was a long way, running from stuck in yellow realme boot logo to bootloops already on the white realme start logo. Finally I got back a running system, which I don't trust anymore now. My configuration is:
- unlocked bootloader
- TWRP 3.3.1.13
- Magisk canary debug 8ca5a048 (20405)
- Magis Manager 72f6770d (278)
- Andorid 10, C24
I was already at this point 2 days ago. Then Magisk Manager announced an update. Stupid as I am, I just klicked install, and arrived at the same point. Stuck in yellow boot logo, and the whole operation started from beginning. Now I am at the same point again as above, and Magisk Manager announces again an update for itself. But I don't trust it anymore, and I don't know what to do. Just leave it? Or making a nandroid backup first? But will it be sufficiant to backup boot partition, system image and data when the crash comes again? I don't know what to do.
HTCDevil said:
The real mistake is when your device brick with locked bootloader, all the other cases are solvable.
Click to expand...
Click to collapse
My Phone cannot boot and cannot go to recovery mode. What should I do? Please help:crying:
allan1998PH said:
My Phone cannot boot and cannot go to recovery mode. What should I do? Please help:crying:
Click to expand...
Click to collapse
If you have unlocked bootloader you could go in fastboot mode and flash twrp, then format data
I am just new to this flashing custom roms or firmware and twrp also. And dumb enough to not back it up.
I wanted to install arrow os in my phone. When I was about to wipe data, cache and dalvik, I accidentally checked metadata also and wiped. Then problems created more problems.
problems right now:
I cant put a file in my storage
Internal Storage is just blank on my pc
No OS
TWRP on both slots
please help me i really needed help and knowledge about it
I hope the attachment helps
EDIT--
Solutions to my problems:
WHEN you softbrick your phone and you only have fastboot and nothing else
Thanks to this guy..
SOLUTION: download your original firmware but choose the fastboot one and not recovery after download just unzip. Double click flash_all.bat and its back to square one.
WHEN you dont know how to flash or the file you have is .img
SOLUTION: find a guide in xda because apparently you can install a .img file in "fastbootd" mode
the guides here: https://forum.xda-developers.com/t/...sues-all-without-any-custom-recovery.4337099/
COMMENT: not the usual thats what on top of youtube search.
WHEN you see errors in twrp/orangefox recovery you might get panic and search for solution.
COMMENT: try to find and use a solution that doesnt delete something first. In my experience it got bricked even more.
Thanks to the people who commented back on my post and helping me get to know what to do next.
Try putting the stock ROM on a SD card or usb (if you have a dongle).
georg3_ said:
Try putting the stock ROM on a SD card or usb (if you have a dongle).
Click to expand...
Click to collapse
SD card that you put on beside the sim? if yes
Do I download stock ROM in official website? Cus I dont have 1 right now
then flashing it there by using twrp? is that how its gonna run? because i really dont wanna assume and create another problem
Try flashing this stock ROM (global) from a SD card, in TWRP. It's a recovery package, so you can install it as any zip.
Also, can you boot into fastboot/bootloader from TWRP?
Plus, where did you get the ArrowOS image? There are no builds, official or not.
georg3_ said:
Plus, where did you get the ArrowOS image? There are no builds, official or not.
Click to expand...
Click to collapse
I found it here
It is made my myst33d and it is a beta build
im getting a sd card right now to test it out
And yes I still can go to fastboot/bootloader from twrp
I cant seem to find my file in twrp... even in file manager
the file is int .tgz must I change it to .zip?
raikiro1 said:
I cant seem to find my file in twrp... even in file manager
Click to expand...
Click to collapse
Is the twrp detecting your sd card？try click on the Install image and change to install zip
can you sideload?
I can now see it, I think I reflashed twrp, now I can, but I cant install because of failed to mount system_root and I have done change file system of data to Ext4. when it resets it comes back to f2fs
edit: change file system of data to Ext4 failed
edit2: thank you guys really for commenting back and helping me
is no verity affecting it? cus I am not able to install it now
you should format data and put the arrow build in it, maybe it will work
J6idot said:
you should format data and put the arrow build in it, maybe it will work
Click to expand...
Click to collapse
I have changed the data to Ext4, fomarted, wiped again the data,dalvik and cache
I have a Redmi Note 10S Rosemary from xiaomiupdater but I still cannot install the rom cus there is a error " Error installing zip file /sdcard1/thefile."
I tried to install no verity opt encrypt but failed and says updater process ended with ERROR: 1
Error installing zip file "sdcard1/thefile"
raikiro1 said:
I cant seem to find my file in twrp... even in file manager
the file is int .tgz must I change it to .zip?
Click to expand...
Click to collapse
Must change it to zip.
EDIT: Extract the file, there's a zip or img inside.
raikiro1 said:
I have changed the data to Ext4, fomarted, wiped again the data,dalvik and cache
I have a Redmi Note 10S Rosemary from xiaomiupdater but I still cannot install the rom cus there is a error " Error installing zip file /sdcard1/thefile."
I tried to install no verity opt encrypt but failed and says updater process ended with ERROR: 1
Error installing zip file "sdcard1/thefile"
Click to expand...
Click to collapse
Try to sideload it, maybe it'll work.
georg3_ said:
Must change it to zip.
Click to expand...
Click to collapse
Should have said "extract the file, there's a zip or img inside", don't change the file extension.
Update: I found the guide how to sideload ... just change the Ext4 to F2fs
[Tutorial] TWRP ADB Sideloading
Alternative solution: OTG usb flash drive - With one of these, you can store a ROM zip safely, and still format ‘userdata’ to f2fs or EXT4. TWRP ADB Sideloading Requirements: Mac | Linux | Windows PC / Laptop and TWRP Custom Recovery Moto G...
forum.xda-developers.com
and I was able to sideload it and then got MIUI finally
what worried me is there were still errors like system_root, vendor and product... and its running fine now I guess but im back on track to make it to arrow OS.... I hope no mistakes this time like deleting metadata.
Thank you all who replied to this post , I really do. Thank you
raikiro1 said:
Update: I found the guide how to sideload ... just change the Ext4 to F2fs
[Tutorial] TWRP ADB Sideloading
Alternative solution: OTG usb flash drive - With one of these, you can store a ROM zip safely, and still format ‘userdata’ to f2fs or EXT4. TWRP ADB Sideloading Requirements: Mac | Linux | Windows PC / Laptop and TWRP Custom Recovery Moto G...
forum.xda-developers.com
and I was able to sideload it and then got MIUI finally
what worried me is there were still errors like system_root, vendor and product... and its running fine now I guess but im back on track to make it to arrow OS.... I hope no mistakes this time like deleting metadata.
Thank you all who replied to this post , I really do. Thank you
Click to expand...
Click to collapse
no problem next time installing, stick to sideloading, less room for error
I cant seem to install TWRP recovery again it justs bootloop .. I dont know why anybody knows?
Whenever I fastboot boot twrp3.6.1-rosemary it fails, says too many links, and when I fastboot reboot recovery it boot loops
flashboot flash boot twrprosemary says okay in slot A and I even put it to B and flash it there sadly
the problem might be because its A12 ... just an update
raikiro1 said:
I cant seem to install TWRP recovery again it justs bootloop .. I dont know why anybody knows?
Whenever I fastboot boot twrp3.6.1-rosemary it fails, says too many links, and when I fastboot reboot recovery it boot loops
flashboot flash boot twrprosemary says okay in slot A and I even put it to B and flash it there sadly
the problem might be because its A12 ... just an update
Click to expand...
Click to collapse
A12 shouldn't be a problem.
Probably you should flash another vbmeta.img.
OR
I don't know if there is an .img twrp around, but if there is you can:
Code:
fastboot boot {recovery.img}
and then [Advanced]>[Install Recovery Ramdisk].
raikiro1 said:
I cant seem to install TWRP recovery again it justs bootloop .. I dont know why anybody knows?
Whenever I fastboot boot twrp3.6.1-rosemary it fails, says too many links, and when I fastboot reboot recovery it boot loops
flashboot flash boot twrprosemary says okay in slot A and I even put it to B and flash it there sadly
the problem might be because its A12 ... just an update
Click to expand...
Click to collapse
what vbmeta are you using?