Related
Ok thanks a head of time my tab is stuck on booting primary image kernel it had flex rom 4.0.4 and skrilaz cz v8 boot loader and when I search I don't find anything that really helps me . I had bricked it trying to figure it out but got it back to the stuck in boot loader stage my tab it can go to apx mode and I can use the recovery and it charges and I have tried 3 ICS roms and i'm still on the screen .
MODFAST said:
Ok thanks a head of time my tab is stuck on booting primary image kernel it had flex rom 4.0.4 and skrilaz cz v8 boot loader and when I search I don't find anything that really helps me . I had bricked it trying to figure it out but got it back to the stuck in boot loader stage my tab it can go to apx mode and I can use the recovery and it charges and I have tried 3 ICS roms and i'm still on the screen .
Click to expand...
Click to collapse
Make sure you are running the most recent CWM (1.7.2 or 1.7.3)
Boot to recovery, and this time, do all your wipes
Wipes Menu
a. wipe Data/factory reset
b. wipe cache
c. wipe Dalvik
Go to Mounts and storage
a. Format system
b. Format Flexrom
Install rom, and make sure it's a rom with an ICS kernel.
As a last chance if the above normal things don;t work,
you may have corrupted data somewhere, and in this case, go to Backup and Restore and toggle Data Media. NOTE: This will wipe your tab clean of fotos, music, etc. Everything.
Then do your wipes and formats.
MD
Moscow Desire said:
Make sure you are running the most recent CWM (1.7.2 or 1.7.3)
Boot to recovery, and this time, do all your wipes
Wipes Menu
a. wipe Data/factory reset
b. wipe cache
c. wipe Dalvik
Go to Mounts and storage
a. Format system
b. Format Flexrom
Install rom, and make sure it's a rom with an ICS kernel.
As a last chance if the above normal things don;t work,
you may have corrupted data somewhere, and in this case, go to Backup and Restore and toggle Data Media. NOTE: This will wipe your tab clean of fotos, music, etc. Everything.
Then do your wipes and formats.
MD
Click to expand...
Click to collapse
I have tried the suggested and I'm still on boot loader.
ROMS I used
FLEXREAPER-ReliX-GT_Rev1 ANDROID 4.0.3
RE-FLEXxx-ShellSHOCKRev1.1
Acer_AV041_A500_1.054.00_WW_GEN1-DEODEXED-FULLROOT
Also on CWM1.7.3 latest
Wiped everything twice and didn't see any change so should I try a stock Rom and just revert to non root ?
You can also wipe userdata from fastboot: "fastboot erase userdata". You may try using adb after a while and do logcat, from where you can see what's the issue.
Skrilax_CZ said:
You can also wipe userdata from fastboot: "fastboot erase userdata". You may try using adb after a while and do logcat, from where you can see what's the issue.
Click to expand...
Click to collapse
OK I can't seem to get my tab on fastboot mode and I haven't used adb to get a logcat so is there a thread that talks bout how to do that.
MODFAST said:
OK I can't seem to get my tab on fastboot mode and I haven't used adb to get a logcat so is there a thread that talks bout how to do that.
Click to expand...
Click to collapse
I'd try flashing the bl again, sounds strange u can't get to fastboot mode??
Sent from my GT-I9300 using Tapatalk 2
dibb_nz said:
I'd try flashing the bl again, sounds strange u can't get to fastboot mode??
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I must have messed up but now I have gotten on fastboot mode but don't see the setting to erase userdata
you type in command from PC.
open cmd prompt from where u have fastboot.exe
type: fastboot devices
u should see a ?
then type: fastboot erase userdata
it should then tell u userdata erased.
u can also flash recovery.img with fastboot and get yr cpuid....very useful
Sent from my GT-I9300 using Tapatalk 2
dibb_nz said:
you type in command from PC.
open cmd prompt from where u have fastboot.exe
type: fastboot devices
u should see a ?
then type: fastboot erase userdata
it should then tell u userdata erased.
u can also flash recovery.img with fastboot and get yr cpuid....very useful
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Okay I don't have fastboot.exe file where do I download that at ? I tried to find my device with cmd and looked for fastboot.exe and looked it up and only file I do have is fastboot from my root 3.2.1 folder.Thank for all the help
Sent my laptop [/QUOTE]
MODFAST said:
Okay I don't have fastboot.exe file where do I download that at ? I tried to find my device with cmd and looked for fastboot.exe and looked it up and only file I do have is fastboot from my root 3.2.1 folder.Thank for all the help
Sent my laptop
Click to expand...
Click to collapse
You have to have the Android SDK installed on your PC.
Then you will find it in Program Files (or Program Files (x86))/Android/Android-SDK/Platform-Tools/ There you will find fastboot.exe
MD
Moscow Desire said:
You have to have the Android SDK installed on your PC.
Then you will find it in Program Files (or Program Files (x86))/Android/Android-SDK/Platform-Tools/ There you will find fastboot.exe
MD
Click to expand...
Click to collapse
Okay I downloaded the SDK and got the fastboot.exe and downloaded the adb file to get it to run but, when I got to cmd I don't understand why it keeps say can't find pacific file or external command ..ect .I have my acer in fastboot mode and its reconized as a fastboot device on my laptop.
MODFAST said:
Okay I downloaded the SDK and got the fastboot.exe and downloaded the adb file to get it to run but, when I got to cmd I don't understand why it keeps say can't find pacific file or external command ..ect .I have my acer in fastboot mode and its reconized as a fastboot device on my laptop.
Click to expand...
Click to collapse
You probably got "java' is not recognized as an internal or external command."
You still need to install the Java dev kit. Go to Oracle, and get the Java Jdk7 and install it. (remember, android uses Java)
http://www.oracle.com/technetwork/java/javase/downloads/index.html
Then, after install, view this video to set the PATH, then do the same for CLASSPATH
http://www.youtube.com/watch?v=D13ZSPA1Ff0
You won't get that error anymore.
MD
Moscow Desire said:
You probably got "java' is not recognized as an internal or external command."
You still need to install the Java dev kit. Go to Oracle, and get the Java Jdk7 and install it. (remember, android uses Java)
http://www.oracle.com/technetwork/java/javase/downloads/index.html
Then, after install, view this video to set the PATH, then do the same for CLASSPATH
http://www.youtube.com/watch?v=D13ZSPA1Ff0
You won't get that error anymore.
MD
Click to expand...
Click to collapse
Okay I downloaded the java 7 and followed the process but still got errors so i went to sdk folder and did it over
I went by this video and it worked "http://www.youtube.com/watch?v=oaNM-lt_aHw"
After I got commands to work i typed fastboot erase userdata and i got on my tab "erasing uda partition then it said Done.
I used the cmd to reboot table to recovery and download a new ics rom.
It didnt work it went back to its ussal stuck on v8bootloader self. What do I do now ?
I'm in the exact same position right now. On ICS v8 bootloader, flashed latest re-flexxx rom, tablet was sluggish. Turned it off in order to restart it. Upon restart tablet froze @ "booting primary kernel." I tried everything I could as far as doing things in CWM (flashing different roms, none would get past booting primary kernel | tablet won't go into APX Mode) Tried flashing TWRP via CWM, now I can't even boot the recovery kernel.
Booted into fastboot, erased userdate. Sent fastboot flash recovery recovery.img (CWM). Said flashed SOS Partition successfully on tablet. Tried rebooting into recovery, same thing; freezes at booting primary kernel. I'm pretty sure this is the end of my A500 lol.
Hello everybody!
Last week installing cyainfire my device felt in bootloop..
I tryed all the ways possible but i' m sure someone of you will be better
I have destroyed everything on the nexus, also the recovery.. The only one working is the bootloader (obviously unlocked)
What i can do at this moment is: flashing a custom recovery TWRP on the device by toolkit and from there activating the ADB sideload. Trought cmd the working and useful commands are:
Code:
adb push rom.zip
adb sideload rom.zip
From the recovery i wasn' t able to flash the pushed zip...
I tryed several times with the sideload but the nexus was telling me that it couldn' t mount /system and /cache... So, it wasn' t working..
But finally i tryed wiping everything whit the commands:
Code:
fastboot erase system
fastboot erase cache
fastboot erase userdata
And formatting data by the TWRP..
(It is still saying me it cannot mount the /cache)
The ADB sideload of the device was working but anyway it fails flashing the sent zip..
What could be the problem? I have no more ideas...
Thanks a lot
p.s. english is not my first language
P.S.2: Solved on my own.. this time the sideload command worked.. sometimes i thing the linux kernel has its owns intelligence..
Hi,
I was at work Sunday night when the phone offers me an update, not wanting to lose my data I re-growth that has Tuesday morning during my last round (which takes me roughly 25/30 minutes ). So I run the update and go round when I come back I have the phone on the screen of blocked boot ...
Considering I'm looking since yesterday, I have already tried many tutorials that did not work.
I tried everything flashed like to start from zero but nothing worked. I have every time a message like: failed can't install image not signed OR dtb not found ...
I have access at fastboot and nothing else.
There's way to save this phone I for 3 months or it is good to wedge a table ?
Thx in advance
edit :
ok, i do this
http://www.asus-zenfone.com/2015/10/how-to-root-asus-zenfone-2-laser-ze500kl.html
and this
http://forum.xda-developers.com/showpost.php?p=66894780&postcount=5
and i have now acces to recovery mode
Edit 2 :
http://www.asuszenfoneblog.com/2015/04/how-to-flash-asus-zenfone-2-via-adb.html with the firware Version V13.10.7.1(Andriod M) https://www.asus.com/support/Download/39/1/0/20/KsY29RCpsJ2bea9O/32/
but after reboot i have the message : ERROR : Can't load invalid boot image !
i lose th recovery and i can't flash the boot ( remote dtb not found ) ...
edit 3 :
the phone has restarts with the original firmware but I have so manipulated that I do not know what I did
I remember using the following links : http://www.asus-zenfone.com/2015/09/how-to-flash-asus-zenfone-2-laser.html ans the stock rom for 550KL
when I reinstall the rom of origin, such would not boot and I had to boot the mod_boot.img picture (Flashtool boot mod_boot.img), which launches the phone and now more problem. It remains to remove the root which should be easier than the rest.
@Genux888 This link takes to ZE500KL's firmware downloads https://www.asus.com/support/Download/39/1/0/20/KsY29RCpsJ2bea9O/32/
Your phone model is ZE550KL but you first attempted to flash MM ROM of ZE500KL
Thats why you got error: invalid boot.img and you lost recovery.
I don't know where you got mod_boot.img from. Neverthless, here's the simplest fix-
1. Download ZE550KL's Stock_boot_recovery.zip
This zip contains stock signed recovery.img and boot.img. Extract it and copy both .img files to the folder where you have adb and fastboot files.
Download correct firmware for your ZE550KL of the correct SKU. You can find your SKU on your phone's box.
WW SKU : Download ZE550KL's firmware v1.17.40.1531 for WW SKU only
Let me know if your phone's SKU is not WW
Copy the firmware zip (UL-Z00L-WW-1.17.40.1531-user.zip) to your external sd card.
2. Connect your phone to computer and Reboot phone to fastboot mode.
3. Now run the following commands
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot oem reboot-recovery
3. Third command should reboot your phone to recovery mode.
Now, in recovery mode-
A) select "wipe cache partition" then select yes
B) select "apply update from sdcard" then select "UL-Z00L-WW-1.17.40.1531-user.zip" and finally select "yes"
stuck at verifying update package
MITHI-N said:
stuck at verifying update package
Click to expand...
Click to collapse
Reboot to fastboot mode (instructions in post#1) and execute this command
Code:
fastboot erase system
Then flash the ota from recovery.
sziraqui said:
Reboot to fastboot mode (instructions in post#1) and execute this command
Code:
fastboot erase system
Then flash the ota from recovery.
Click to expand...
Click to collapse
Hi can you put a link to OTA, I tried searching for it but could only get the full firmware from the asus website.
sziraqui said:
Reboot to fastboot mode (instructions in post#1) and execute this command
Code:
fastboot erase system
Then flash the ota from recovery.
Click to expand...
Click to collapse
Removed, putback battery & followed all steps, successfully installed 1531 rom
Then upgraded to Asus Marshmellow, Everything working.
But when I try to clear data & cache from new recovery I get couple of errors stating unable to mount /asdf & few other things
MITHI-N said:
Removed, putback battery & followed all steps, successfully installed 1531 rom
Then upgraded to Asus Marshmellow, Everything working.
But when I try to clear data & cache from new recovery I get couple of errors stating unable to mount /asdf & few other things
Click to expand...
Click to collapse
I did the following-
Input: "Wipe cache partition"
Output: E: unable to mount /asdf (invalid argument)
Input : "mount /system"
Input: "wipe cache partition"
Output: Cache wipe complete
E: unable to mount /asdf
E: Can't open /asdf/recovery/last_log
This shows that I am able to wipe cache after mounting /system (though it doesnt make sense)
I didn't wipe data as I don't want to setup my device again. You may try if wiping data works after mounting /system. Alternatively, you can flash stock 1.15's recovery (download from post #2)
and flash in fastboot mode using
Code:
fastboot flash recovery recovery.img
(assuming you recovery.img file is present in the folder where you have fastboot files)
And, here on XDA, we hit "thanks" good button if a post was helpful to us.
Sorry to reply so late but I managed to unlock my phone has put version 5.0, the update to 6.0, UNLOCK the boot, root the phone and install the TWRP may close 2 or 3 hours after my last post.
thank you.
i really like it when people post all the steps taken and links in their problem posts.
this is great.
(no, that is NOT sarcasm)
The best solution out there for zoold 550kl
This is the best answer for the rooted asus zenfone 2 550kl for upgrading to marshmellow stock .Thank you...
Help
@sziraqui My phone is in a bootloop and I honestly know pretty much nothing as to how to fix it.. I know it's the ZE551KL, but that's pretty much it. Is there any way youcan help me out? thanks in advance
Stock recovery for MM?
Anyone have stock recovery for MM upgrade from LP?
Problem Not Solved
I am Also facing same type of problem but the difference is :
- I am only able to enter fastboot mode only when i am connecting my phone to pc via datacable.
- After flashing recovery.img and boot.img also i am not be able to go to recovery mode..
Can someone please Help..
I've seen you've tried a lot.
I'd suggest you try this... As long as you can send your phone to fastboot and can pc/add your way through you'll be able to unbrick it. This takes a bit of time as you'll be dealing with two huge downloads (system.img and stock rom) but it should do the trick.
Follow the guide here:
https://www.asus.com/zentalk/thread-80274-1-1.html
---------- Post added at 12:59 AM ---------- Previous post was at 12:54 AM ----------
utkarshdev20 said:
- After flashing recovery.img and boot.img also i am not be able to go to recovery mode..
Can someone please Help..
Click to expand...
Click to collapse
The guide at https://www.asus.com/zentalk/thread-80274-1-1.html talks about flashing boot.img first then a huge (1.7GB) system.img second then recovery.img last.
So it could mean the boot.img and system.img needs to be dealt with first before you have any chances of getting your recovery to work.
Follow the steps closely, I've been able to fix a brick with it twice.
NO way to boot into Recovery or Fastboot!!!!!!!!!!!!!
Phone got bricked!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
When connected to PC(Windows), I only get 8 local disk partitons (ext4) asking to format!!!!!!!!!!!
And one with image partition(BOOT)
What to do now to regain access to either fastboot or to recovery!!!!!!!!!!!!!!!!!
PLEASE Reply!!!!!!!!!!!!!!!!!!
utkarshdev20 said:
I am Also facing same type of problem but the difference is :
- I am only able to enter fastboot mode only when i am connecting my phone to pc via datacable.
- After flashing recovery.img and boot.img also i am not be able to go to recovery mode..
Can someone please Help..
Click to expand...
Click to collapse
I can help you but first i neef some info about your phone..how it got bricked?was your phone rooted?
Hey guys,
I have a problem with a bricked xiaomi redmi 2 prime.
After a bootloop i tried to fix the problem with a system reset. But this does not work
After i booted into recovery and wiped all data, the phone reboot but than nothing happend. So i tried to flash the rom with the mi flash tool, but there i get the error "remote: failed to write partition".
So i went over to the adb and fastboot programms, with fastboot i erased system, userdata, recovery, boot and then i flashed the images of this elements back on the phone (fastboot flash sayed that flashing went successfully)
Then the phone reboot, nothing happend and i can´t get into recovery mode, also adb doesn´t recognoze the phone anymore
Have you any idea what i can do to fix the phone, or can i put it into the trash?
Thanks for your help
Stop experimenting.
Does fastboot work? Do a full flash with miflash(erasing all storage)(firmware should be of your model itself)
If fastboot doesnt work,try putting in the charger with battery in,if there is any vibration,you have a chance of reviving your r2
#fingerscrossed
Ezio95 said:
Hey guys,
I have a problem with a bricked xiaomi redmi 2 prime.
After a bootloop i tried to fix the problem with a system reset. But this does not work
After i booted into recovery and wiped all data, the phone reboot but than nothing happend. So i tried to flash the rom with the mi flash tool, but there i get the error "remote: failed to write partition".
So i went over to the adb and fastboot programms, with fastboot i erased system, userdata, recovery, boot and then i flashed the images of this elements back on the phone (fastboot flash sayed that flashing went successfully)
Then the phone reboot, nothing happend and i can´t get into recovery mode, also adb doesn´t recognoze the phone anymore
Have you any idea what i can do to fix the phone, or can i put it into the trash?
Thanks for your help
Click to expand...
Click to collapse
Yup actually download the latest version of miui fastboot files..paste them in the fastboot folder... Dont bother erasing you phn again(as it does erase at the time of writing new files...)And most importantly flashing only 3 files is more than enough. Flash them in the order boot.img, system.img, recovery.img and thats it. If your problem is actually not booting into fastboot then....press the volume down button and insert your usb while keeping it pressed.
Hey guys,
thanks for the answers. I tryed to flash only thees 3 files but it doesn´t change anything. fastboot works without trouble so far.
I tried multiple times the xiaomi flashing tool but this only throws errors -.-'
I will try again and keep you by the actual progress ^^
Ezio95 said:
Hey guys,
thanks for the answers. I tryed to flash only thees 3 files but it doesn´t change anything. fastboot works without trouble so far.
I tried multiple times the xiaomi flashing tool but this only throws errors -.-'
I will try again and keep you by the actual progress ^^
Click to expand...
Click to collapse
If you can get the fastboot to work, you can flash recovery on your phone for good or temporarily to flash zips.
How to do it?
1.Get into fastboot on phone
2.Install minimal adb and fastboot in your computer
3.Run adb and install drivers
4.Connect your phone which should be in fastboot to computer
5.Check for devices by using "fastboot devices", if a device is listed, proceed
6.Download a custom recovery, rename the recovery img to something easy than using the full name and copy the img into the folder where minimal adb and fastboot is installed
7.Type in "fastboot flash recovery <name you gave to recovery img>.img" (img for the image format) to flash recovery permanently
OR
7.Type in "fastboot boot <recovery name>.img" to use it temporarily, this method will erase the recovery on reboot so flash whatever you want before rebooting if you're following this method.
8.Flash in your ROM zip, try stock and custom ROMs, see if you can get your phone to work
GOOD LUCK
Same error with my yureka plus (error "remote: failed to write partition"). I'm planning to buy redmi 2 prime.. . Scared if this will happen to redmi 2 prime
Hello,
Many people report, that their TWRP/PBRP is black and they can't install custom ROM or flash stock ROM by recovery.
Problem occurs in devices with Jdi display.
It is recommended to flash Oreo, then recovery work, but if you want use Android Pie you must be on this stock firmware (I tried Oreo and flash Havoc (Pie) = bootloop).
We need:
Unlocked bootloader
Turned on android debugging
ADB (minimum 1.4.3)
TWRP/PBRP (.img file)
ROM, GAPPS,...
YOUR DATA/PHOTOS/DOWNLOADS WILL BE REMOVED, SO MAKE A BACKUP!
Let's get started:
1. FLASHING ROM
/the phone is on/
1. Use cmd and type: adb reboot-bootloader
<phone will turn on in fastboot mode>
2. Type: fastboot set_active b
Then: fastboot boot <your_recovery.img>, e.g. fastboot boot twrp.img
<phone will reboot, the screen will be black>
<wait to Windows new device sound>
3. Type: adb shell
twrp wipe cache
twrp wipe dalvik
twrp wipe system
twrp wipe data <- NOW YOUR DATA WILL BE REMOVED, SO MAKE A BACKUP BEFORE!
twrp sideload
adb sideload <location_of_your_ROM.zip>, e.g. adb sideload C:\Havoc.zip
When the installation is completed you will see "Total xfer X.XXx".
2. FLASHING GAPPS
Now: adb reboot-bootloader
<phone will turn on in fastboot mode>
fastboot set_active a
fastboot boot <your_recovery.img>, e.g. fastboot boot twrp.img
<phone will reboot, the screen will be black>
<wait to Windows new device sound>
adb shell
twrp wipe cache
twrp wipe dalvik
twrp sideload
adb sideload <location_of_your_GApps.zip>, e.g. adb sideload C:\GApps.zip
When the installation is completed you will see "Total xfer X.XXx".
3. FLASHING PATCHED BOOT IMAGE (MAGISK + ROOT)
adb reboot-bootloader
fastboot flash boot <your_patched_boot.img>, e.g. fastboot flash patched_boot.img
fastboot reboot
<phone will start, the first start may take some time>
It's instruction for performing these three steps sequentially.
System will be installed on slot B, the Gapps and patched boot on slot A.
Now you can enjoy custom ROM
Greetings
Flash999 said:
Hello,
Many people report, that their TWRP/PBRP is black and they can't install custom ROM or flash stock ROM by recovery.
Problem occurs in devices with Jdi display.
It is recommended to flash Oreo, then recovery work, but if you want use Android Pie you must be on this stock firmware (I tried Oreo and flash Havoc (Pie) = bootloop).
We need:
Unlocked bootloader
Turned on android debugging
ADB (minimum 1.4.3)
TWRP/PBRP (.img file)
ROM, GAPPS,...
YOUR DATA/PHOTOS/DOWNLOADS WILL BE REMOVED, SO MAKE A BACKUP!
Let's get started:
1. FLASHING ROM
/the phone is on/
1. Use cmd and type: adb reboot-bootloader
<phone will turn on in fastboot mode>
2. Type: fastboot set_active b
Then: fastboot boot <your_recovery.img>, e.g. fastboot boot twrp.img
<phone will reboot, the screen will be black>
<wait to Windows new device sound>
3. Type: adb shell
twrp wipe cache
twrp wipe dalvik
twrp wipe system
twrp wipe data <- NOW YOUR DATA WILL BE REMOVED, SO MAKE A BACKUP BEFORE!
twrp sideload
adb sideload <location_of_your_ROM.zip>, e.g. adb sideload C:\Havoc.zip
When the installation is completed you will see "Total xfer X.XXx".
2. FLASHING GAPPS
Now: adb reboot-bootloader
<phone will turn on in fastboot mode>
fastboot set_active a
fastboot boot <your_recovery.img>, e.g. fastboot boot twrp.img
<phone will reboot, the screen will be black>
<wait to Windows new device sound>
adb shell
twrp wipe cache
twrp wipe dalvik
twrp sideload
adb sideload <location_of_your_GApps.zip>, e.g. adb sideload C:\GApps.zip
When the installation is completed you will see "Total xfer X.XXx".
3. FLASHING PATCHED BOOT IMAGE (MAGISK + ROOT)
adb reboot-bootloader
fastboot flash boot <your_patched_boot.img>, e.g. fastboot flash patched_boot.img
fastboot reboot
<phone will start, the first start may take some time>
It's instruction for performing these three steps sequentially.
System will be installed on slot B, the Gapps and patched boot on slot A.
Now you can enjoy custom ROM
Greetings
Click to expand...
Click to collapse
Work well.. buuuut.... i think tha hard drive of phone is encrypted... and inwritable, so... works! but is not functional
Wormboymx said:
Work well.. buuuut.... i think tha hard drive of phone is encrypted... and inwritable, so... works! but is not functional
Click to expand...
Click to collapse
The data partition is encrypted. If you want to access this partition you have to format it by TWRP. When you start system with forced encryption, the data will be again encrypted (or use custom ROM without encryption or install script to disable it on stock software).
Flash999 said:
The data partition is encrypted. If you want to access this partition you have to format it by TWRP. When you start system with forced encryption, the data will be again encrypted (or use custom ROM without encryption or install script to disable it on stock software).
Click to expand...
Click to collapse
Ok, can you help me with that? I think with you excellent guide maybe is missing one step to avoid this.
Thanks!
Wormboymx said:
Ok, can you help me with that? I think with you excellent guide maybe is missing one step to avoid this.
Thanks!
Click to expand...
Click to collapse
I had a similar problem while using twrp to copy files to the phone storage, try this command before doing anything:
fastboot -w
Note: This wipes all data.
This made the phone storage accessible.
mma_1494 said:
I had a similar problem while using twrp to copy files to the phone storage, try this command before doing anything:
fastboot -w
Note: This wipes all data.
This made the phone storage accessible.
Click to expand...
Click to collapse
Doesn´t work too =(
"fastboot -w
wiping userdata...
CreateProcess failed: El sistema no puede encontrar el archivo especificado. (2)
error: Cannot generate image for userdata"
i Will back to stock rom Pie...
P.D. the encryption is when finishi whole process in the installed custom rom the hard drive doesn't work e.g... Open the camera and system say "Don't have sd card to save the files"
where will get patched_boot.img for mi a2 10.0.2 or 10.0.4
where will get patched_boot.img for mi a2 10.0.2 or 10.0.4
asad0181 said:
where will get patched_boot.img for mi a2 10.0.2 or 10.0.4
Click to expand...
Click to collapse
On this Youtube channel https://www.youtube.com/channel/UCuEtuySiR1DDYCRerutqvnA/videos
You can get some files...
Hello! How do I know if my device has a Jdi display panel? If it does have, do I need to follow this guide every time I flash or update a rom?
chrisdlc119 said:
Hello! How do I know if my device has a Jdi display panel? If it does have, do I need to follow this guide every time I flash or update a rom?
Click to expand...
Click to collapse
Try to boot TWRP on Pie, if you see TWRP GUI mean you don't have Jdi display. You don't have to flash anything, only boot by fastboot.
It depends of your ROM and system updater, I follow the guide to flash new version and all is working ok.
Flash999 said:
Try to boot TWRP on Pie, if you see TWRP GUI mean you don't have Jdi display. You don't have to flash anything, only boot by fastboot.
It depends of your ROM and system updater, I follow the guide to flash new version and all is working ok.
Click to expand...
Click to collapse
I think my display is tianman (ss atached). Is that right? Do you know if any display is affected with burning effect? It's just that I had a RN5 and I changed from MIUI to a custom ROM and one day the display just got the burning effect
Thanks for your reply.
Wormboymx said:
Doesn´t work too =(
"fastboot -w
wiping userdata...
CreateProcess failed: El sistema no puede encontrar el archivo especificado. (2)
error: Cannot generate image for userdata"
i Will back to stock rom Pie...
Click to expand...
Click to collapse
I'm getting the same error when doing fastboot -w, and the ROM I flashed (Resurrection Remix) is stuck on startup splash screen.
Any idea what can cause this, and how I can recover?
mma_1494 said:
I had a similar problem while using twrp to copy files to the phone storage, try this command before doing anything:
fastboot -w
Note: This wipes all data.
This made the phone storage accessible.
Click to expand...
Click to collapse
Thanks! Now I could install Havoc and have access to my files!
Op you should include ,,fastboot -w" in your guide.
Finally i can boot PitchBlack recovery without Blackscreen in JDI panels::
Boot this recovery file: https://sourceforge.net/projects/pitchblack-twrp/files/jasmine_sprout/
Only one difference between the guide of this Thread....
I can´t change the partitions in PitchBlack recovery... i used the command in the op to change the partitions.... NOW i can flashed the Resurection remix rom in my phone
hlg1 said:
I'm getting the same error when doing fastboot -w, and the ROM I flashed (Resurrection Remix) is stuck on startup splash screen.
Any idea what can cause this, and how I can recover?
Click to expand...
Click to collapse
So, I was able to recover from this by using Xiaomi Flash Tool (v20170425) to flash the V10.0.7.0 stock rom. That got me back to a working stock Android.
I then retried the steps from this guide (except Gapps and patched boot), and this time I was able to get my Resurrection Remix started. However, the userdata file structure looks like rubbish, and none of the apps can write to or read from it. I tried to do a factory reset (from within custom rom) to fix this, but then the phone turned off and would not boot to custom rom again. fastboot -w still doesn't work.
Any ideas how to make the userdata partition great again?
hlg1 said:
So, I was able to recover from this by using Xiaomi Flash Tool (v20170425) to flash the V10.0.7.0 stock rom. That got me back to a working stock Android.
I then retried the steps from this guide (except Gapps and patched boot), and this time I was able to get my Resurrection Remix started. However, the userdata file structure looks like rubbish, and none of the apps can write to or read from it. I tried to do a factory reset (from within custom rom) to fix this, but then the phone turned off and would not boot to custom rom again. fastboot -w still doesn't work.
Any ideas how to make the userdata partition great again?
Click to expand...
Click to collapse
I made it work by doing the first 2 steps from the OP and then after booting into system the first time I booted into bootloader and then used fastboot -w. I did this with Havoc OS though so it might not work for everyone.
When I wanted root and didn't know how to get a patched boot image for my ROM, I just followed the steps to access TWRP through ADB again and then wiped cache and dalvik, afterwards I used the sideload command to flash Magisk on my phone.
hlg1 said:
Any ideas how to make the userdata partition great again?
Click to expand...
Click to collapse
I eventually figured out that all my problems occurred because I was using old versions of ADB and fastboot. After updating to latest platform-tools (currently r28.0.2) I was able to run fastboot -w without problems. And once that worked I was able to set up a fully working system following the steps of this guide.
Thanks for a very useful guide, it saved my day!
i got failed command write failed. any suggestion?
I was also having the black screen problem
Can i flash twrp recovery while keeping the stock rom? If can sombody please help me
Sarath_sh said:
I was also having the black screen problem
Can i flash twrp recovery while keeping the stock rom? If can sombody please help me
Click to expand...
Click to collapse
I'm not entirely sure I understand your question, but please note that by following the OP instructions you never flash TWRP, you just boot right into it from RAM. So should be no problem to do that while keeping stock ROM.