Hi friends, I'm desperate here. I have a Zenfone 2 32gb. I tried performing the ROOT of a tutorial on youtube. I'm desperate here, I have many important things in his internal memory, that smarphone is my company's work! It has several important annotations and important documents.
Could someone help me get the bootloop.
I do not have TwRP. Would there be any way to back up the data? Is there any way I can access files from internal memory by Fastboot, or some way I can back it up? If anyone helps, it will save my life!
Thank you
lipsy25 said:
Hi friends, I'm desperate here. I have a Zenfone 2 32gb. I tried performing the ROOT of a tutorial on youtube. I'm desperate here, I have many important things in his internal memory, that smarphone is my company's work! It has several important annotations and important documents.
Could someone help me get the bootloop.
I do not have TwRP. Would there be any way to back up the data? Is there any way I can access files from internal memory by Fastboot, or some way I can back it up? If anyone helps, it will save my life!
Thank you
Click to expand...
Click to collapse
What 'IFWI Version ' does it state you have in bootloader screen?
timbernot said:
What 'IFWI Version ' does it state you have in bootloader screen?
Click to expand...
Click to collapse
Hii IFWI Version: 0094.1069
lipsy25 said:
Hii IFWI Version: 0094.1069
Click to expand...
Click to collapse
you are in temp bootloader after flashing in xFSTK.
Unfortunately , nothing is usually saved unless you saved it to sd before flashing in xFSTK.
The good news is you now need to flash raw file with AFT .. Watch my unbrick video from 2:17 mins in for AFT flash, it's a two part flash ..must be followed correctly to correct serial number..imei and recovery issues
timbernot said:
you are in temp bootloader after flashing in xFSTK.
Unfortunately , nothing is usually saved unless you saved it to sd before flashing in xFSTK.
The good news is you now need to flash raw file with AFT .. Watch my unbrick video from 2:17 mins in for AFT flash, it's a two part flash ..must be followed correctly to correct serial number..imei and recovery issues
Click to expand...
Click to collapse
Thanks for the attention, friend, I could pass the link from your tutorial
Thank you
Related
I made this debrick image from epg2 6.0.1 firmware.
Download link https://mega.nz/#!Occ0hbxT!WaScVzQ2CPb9GxUD2Kqy2GKwm8jv1Z7YSbxwE_SpEzA
How does the actual "debricking" process work? Is it a case where you are fooling the phone into believing that it is updating to a newer bootloader or modem?
with no info on this i wouldnt flash anything.
monkeyass408 said:
with no info on this i wouldnt flash anything.
Click to expand...
Click to collapse
It worked on my phone since I have the EPG2 firmware. I just did it today.
Kevindroid said:
It worked on my phone since I have the EPG2 firmware. I just did it today.
Click to expand...
Click to collapse
Can you have a guide for other noobs like me ? when will i need this img and how does it save my phone ?
tuilalnvinh said:
Can you have a guide for other noobs like me ? when will i need this img and how does it save my phone ?
Click to expand...
Click to collapse
Here! Just following Trex888 instruction, it's post #4!
http://forum.xda-developers.com/note-4-tmobile/help/hardbricked-note-4-help-t3448834
what steps should I follow? You could use any memory? pleace help me
When My Note 4 Hard bricked I Followed the instructions in this post, it also used a Debrick img from Trex888 (thanks for the img you saved me) so you might want to grab the new img from here and follow the steps in the post linked below.
http://forum.xda-developers.com/note-4-tmobile/help/galaxy-note-4-n910t-fixed-hard-bricked-t3466547
Gobling Ganf said:
what steps should I follow? You could use any memory? please help me
Click to expand...
Click to collapse
my pc detects note 4 brick as qhsusb_bulk can do the same procedure?
Gobling Ganf said:
my pc detects note 4 brick as qhsusb_bulk can do the same procedure?
Click to expand...
Click to collapse
Yes your device is bricked.
Follow instructions carefully and be patient.
Download qualcomm usb drivers
Download debrick.image
Download win32 disk imager software
And write debrick image to fully formated microsd card using win32 disk imager
Put micro sd card in phone and try boot normally
If doesn't boot try hold power button for few seconds
If doesn't work try whole procedure again.
Once came back to life flash stock firmware in odin VERY IMPORTANT
You messed up device so be patient to bring back to life
Hi, upload the link again, you can
this link always falls but the other does not.
thanks bro.
or someone who has it please share it with me.
Ok guys bare with me. This is my first Thread. So it may look a little different then the others :laugh:
At least Your honor 7x will no longer be a paper weight
I posted last week that I do Indeed have a good TWRP Honor 7x BND-L24 USA Variant. Since then I have been getting hammered with requests for it. So being the great guy that I am, I have come to the rescue. NO MORE PAPER WEIGHT :laugh: I have also included TWRP 3.1.1. You will Find Direct download links below.
I have heard that Huawei will be releasing the firmware by end of next week. Go to play store and download Huawei Firmware
Finder(FF) To keep checking for it. Once there you can download it through Huawei FF.
When I did the backup TWRP gave me error 255 with the data.img but it did still back it up. I have the boot.img, system.img and data.img. data.img (data.img untested but should work)
If it does not I have a post here https://forum.xda-developers.com/showthread.php?p=75735265#post75735265 that explains how to use just the boot.img and system.img to recover your phone. IGNORE that it is for the 6x. It does indeed work with the 7x
If your phone is bricked and do not have twrp
1.Turn off phone
2. hold volume down while plugging in usb cable from your pc or laptop. That will put you in fastboot.
Tutorial here https://www.xda-developers.com/how-to-root-honor-7x/ on how to download and install ADB tools.
3.. Download TWRP 3.1.1 for honor 7x here https://drive.google.com/open?id=1dzP5ie7vQEn_dGfZHI383bt2sFxwtcTb
For people with TWRP installed
1. Download My TWRP backup here https://drive.google.com/open?id=1Udc4thELESZ4n_nXYmx6loQtTkjHOqSy
2. Extract the zip file to your ext, sdcard.
3. Boot phone into twrp.(Bricked phones hold volume up and press power to launch twrp assuming it is installed.
4. Select restore in twrp menu then choose sd card then the backup folder.
5. Flash the boot system and data img files
6 Reboot.
NO more paper weight :good:
Oh if anyone has twrp 3.2x that works with this with 7x BND-L24 do share please
Well hope this was not to bad :laugh:
Hit that thanks button. Yea that one under my post on the right :laugh:
Hope this has helped
Thank you
lowspeed said:
Thank you
Click to expand...
Click to collapse
No problem. Least I can do. This site has helped me out a lot
Paper weights suck :laugh:
Didn't work. I got to the "booting now" screen and was stuck there forever. I had to restore my old System and Boot partitions to get back to normal.
Didn't Work for me. goes tot the erecovery page.
Is this the only know method to get back to stock. i tried to uninstalled exposed and somehow eneded up stuck in the erecovery boot loop? very lost any help would be greatly appreciated.
Didn't work, on BND-L34 which is the same model as BND-L24 and it says your device is booting now and never boots.
tomjfmu said:
Didn't work, on BND-L34 which is the same model as BND-L24 and it says your device is booting now and never boots.
Click to expand...
Click to collapse
sad days. do you happen to know of any other alternatives? should i made a backup in TWRP before i rooted and did anything?
This does not work. Restoring data leads to error 255 and restoring just boot and system leads to an unbootable system. Also, the link provided does not help one bit. Can you please try to explain here? Thanks.
dukethedj said:
This does not work. Restoring data leads to error 255 and restoring just boot and system leads to an unbootable system. Also, the link provided does not help one bit. Can you please try to explain here? Thanks.
Click to expand...
Click to collapse
Yes please would love some insight on this. thanks in advance.
forgotenxlegacyx said:
Is this the only know method to get back to stock. i tried to uninstalled exposed and somehow eneded up stuck in the erecovery boot loop? very lost any help would be greatly appreciated.
Click to expand...
Click to collapse
As long as you flash the boot.img first it will wok I tested it myself on my wifes and daughters phone and it worked Perfectly. i did not go into detail to do it correctly because there are tutorial's on here that explain how to flash those files
BiggDipper said:
As long as you flash the boot.img first it will wok I tested it myself on my wifes and daughters phone and it worked Perfectly. i did not go into detail to do it correctly because there are tutorial's on here that explain how to flash those files
Click to expand...
Click to collapse
Would you mind linking a thread on how that is done? sorry for my ignorance
forgotenxlegacyx said:
sad days. do you happen to know of any other alternatives? should i made a backup in TWRP before i rooted and did anything?
Click to expand...
Click to collapse
i have an idea, maybe you can make a backup not just including the system, data, and boot but other stuff. Because I accidentally wiped everything, and I changed the vender to a10/tl10, and that bricked the phone even more. And the data img doesn't work. You can fix it with this https://forum.xda-developers.com/oneplus-5/help/error-255-twrp-t3739468. If someone has a working bnd-l24 or bnd-l34 can you give me everything in the backup?
BiggDipper said:
As long as you flash the boot.img first it will wok I tested it myself on my wifes and daughters phone and it worked Perfectly. i did not go into detail to do it correctly because there are tutorial's on here that explain how to flash those files
Click to expand...
Click to collapse
So you first do that then you do the rest?
Tried again. Getting the 255 error when flashing the Data
Yeah, error 255 is boot looping me too.
does it works well?
Thanks!
RoxRedEye said:
Thanks!
Click to expand...
Click to collapse
You were able to get it to work?
I want to get behind and support this, so much, .But the OP is not registered user, so cant even verify their reputation.
I am late to this device and thread, but my phone will arrive tmw.
I would like to know if this is the only current available restore method for BND-L24?
Well, I f*cked up.
Fastboot works, I can flash stock rom via Xiaomi Flash. Flashing completes without any problems. A notification about encypting phone shows up, at 3% it jumps to 100% and resumes boot. Now after each boot, phone freezes at "input your sim pin" and reboots. Over and over again. What can I try, please help :
edited
twister26 said:
There is an reward for whoever helps me solve this issue
Click to expand...
Click to collapse
u try put your sim on other phone and remove the pin from them , maybe the boot skip that part and dont get freeze
dfranco51207 said:
u try put your sim on other phone and remove the pin from them , maybe the boot skip that part and dont get freeze
Click to expand...
Click to collapse
no luck, removed sim and now it reboots as soon as android one text is displayed
I've also tried wiping cache in default recovery, no luck
twister26 said:
no luck, removed sim and now it reboots as soon as android one text is displayed
I've also tried wiping cache in default recovery, no luck
Click to expand...
Click to collapse
Try to format data in twrp or stock recovery.
If it does not work flash an android 8.0 or Nougat ROM. Do not lock the bootloader.
Let me guess. From Pie to Oreo or Nougat?
Mercoory said:
Let me guess. From Pie to Oreo or Nougat?
Click to expand...
Click to collapse
yes, exactly is there a thread already open somewhere here and i missed? last time TWRP was working, I even got a message "your system has been destroyed" or something like that.
sipollo said:
Try to format data in twrp or stock recovery.
If it does not work flash an android 8.0 or Nougat ROM. Do not lock the bootloader.
Click to expand...
Click to collapse
will try!
https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
ccalixtro said:
https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
Click to expand...
Click to collapse
will give it a read, it it works, I'll PM you and you'll give me your paypal address. Fair is fair.
can't unlock OEM, because I can't boot up to developer tools. great, just great. will try to fix that first.
if you can boot to fastboot try to flash stock pie 10.0.4.0 with miflash, after that your device should be able to boot, than unlock OEM and bootloader and downgrade to what version you want
fdc77 said:
if you can boot to fastboot try to flash stock pie 10.0.4.0 with miflash, after that your device should be able to boot, than unlock OEM and bootloader and downgrade to what version you want
Click to expand...
Click to collapse
I can get to fastboot yeah, but MiFlash tool says that remote oem unlock is not allowed. So I'll probably have to open it up for EDL. Reboot to edl isn't working. Thanks for the advice tho.
twister26 said:
I can get to fastboot yeah, but MiFlash tool says that remote oem unlock is not allowed. So I'll probably have to open it up for EDL. Reboot to edl isn't working. Thanks for the advice tho.
Click to expand...
Click to collapse
i had a problem like yours, but i have flashed stock rom in non EDL mode and everything had start to work apart LTE band missing that i restored with qualcomm's tools
which stock rom have you try to flash? are you downgrading from oreo? bootloop on android one logo after downgrading is a common issue due to ARB (anti rollback protection)
twister26 said:
Whoever saves my precious Mi A1 gets 10$ on his paypal.
Click to expand...
Click to collapse
This is ****
This is not XDA spirit
You can get help without to pay
Please cancel the reward, do it. For all the people on this community.
tropbel said:
This is ****
This is not XDA spirit
You can get help without to pay
Please cancel the reward, do it. For all the people on this community.
Click to expand...
Click to collapse
reward is cancelled from this point on i will reward the one who helped me so far tho. still working on solving the problem so winner has not been decided yet.
you don't understand.
There are no winners and no loosers.
You are free to donate to anyone you want, but your post boost and encourages a bad attitude.
If people start to solve only paid problems, the spirit of the community will be destroyed.
The problem is with the Pie specific partition table
I write the whole guide from memory, so it can differ a bit.... I skipped some steps ( erasing, reboot, fastboot mode, TWRP loading via fastboot, OEM unlock )
From previous writings I think you can know the skipped steps.
Keep in mind: It is dangerous, you can loose your IMEI ( it will only work again with Pie - or there are some writings at forum how can you manually change it. ).
Steps:
1 - Backup with TWRP (fastboot) efs,persist,modem & make copy to your computer and or to your cloud provider.
2 - Create a new folder in Internal Storage -> TWRP -> BACKUP -> With a new date directory ( the backup already made one, make a new folder, with different date )
3 - Download someone's older TWRP backup from xda (I cheated, I copied the following links ) :
(I'm still a new user, so can't directly write url's )
Mediafire : https COLON SLASH SLASH bit.ly SLASH 2QU5NtC
Mirror: Google Drive : https COLON SLASH SLASH bit.ly SLASH 2UN1DTo
4 - Unpack, and copy EFS to the folder created 2 point
5 - Fastboot TWRP -> Restore EFS
6 - Flash the Official latest firmware from en.miui.com ( If you want to make sure go with EDL mode )
7 - Now, the IMEI & Mac addresses are missing. Don't panic! Download update with System Updates.
8 - When you are on Pie again, restore your first TWRP (fastboot) persist partition
9 - One more System restore
At this time, you will have IMEI & Mac addressees, and hopefully a working phone.
Hope this helps. The same thing happened with me 2 weeks ago. This is how I solves it.
Thank you, I solved it yesterday. Hopefully this post will come in handy for other people!
I'm going over this guide https://forum.xda-developers.com/lg-v35/development/bootloader-unlock-root-instruction-t4052145 and at some point it reads:
There are a couple warnings. The first is that AT&T does not release flashable roms. There is no going back unless of course you take the time to make a backup of the rom itself.
Click to expand...
Click to collapse
I'm new to LG Android and don't know exactly what is considered a twrp-less rom backup here. Is it the "partition extraction" the same guide goes on to describe? If not, can someone please tell me how to do it or point me in the right direction?
It is pretty straightforward:
1. Install and configure QPST and QFIL as per the guide on your PC.
2. Plugin your phone and enter 9008 as per guide.
3. Dump your partitions using QFIL (you will need about 60 GB of free space)
Thanks vlad48!
vlad48 said:
3. Dump your partitions using QFIL (you will need about 60 GB of free space)
Click to expand...
Click to collapse
That's a lot of space! To backup the rom do I really need to back up all of the partitions? Seems like that is including userdata or otherwise more than just the rom :S
rpgdev said:
Thanks vlad48!
That's a lot of space! To backup the rom do I really need to back up all of the partitions? Seems like that is including userdata or otherwise more than just the rom :S
Click to expand...
Click to collapse
hi!
did you ever complete your full partition backup?
Thanks!
cloud1250000 said:
hi!
did you ever complete your full partition backup?
Thanks!
Click to expand...
Click to collapse
Nah, I just went ahead and got rid of the AT&T rom. Haven't needed it and don't miss it.
A word of caution for others, even if you do backup with QFIL, it is hit and miss and flashing partitions from QFil backup can give you errors. Sometimes changing .bin extension of the partition data to .img can help but in my experience most times even after successful flash you may not be able to boot successfully from either slot. I couldn't recover to AT&T Android 10 from my backup and had to flash Korean Android 10 because once you go up to Android 10, you can't downgrade to Pie or Oreo.
Android# said:
because once you go up to Android 10, you can't downgrade to Pie or Oreo.
Click to expand...
Click to collapse
Sheeeeeeeeeit. I didn't know that thank you for posting that. Guess Android 10 isn't so good then? What was your experience? Feel free to pm.
Hi,
Problem: After Update & Root Errors
Now it shows internal SD memory says now it only has 5gb instead of 32 (28~GB)
it had had normal size before.
WTF...?
I maybe messed with some wrong file before on flash, but I really wonder, how to solve this problem..
Damn every phone has its own difficulties, rooted so many phones, but this the process is always somehow unique...
And where is the proper TWRP file for the A20e latest android 9 version?
DBT-A202FXXU3ASL4-20200120200600
Please someone link it for me. The one I found doesn't seem to work..
lol, you need to know it was because of the wrong VBmeta file.
I wondern why the manuals can't be clearer sometimes.
Just like the TWRP tutorial - somehow you need to have the right vbmeta in Hand, but nothing more about this and where to get the proper one.
Whatever, it helped to relock Bootloader and to make a clean install with CSC (not HOME_CSC), then the files and sizes got right again.
Also re-partition helps in this case.
Anyway it's really frustrating to root these days, but at least we still can do this.
Without root many things would suck alot... i would not buy a phone without the possibility of it.
hmmm I wonder if this is why I'm experiencing problems with my recently rooted a20e and no choice for internal storage.
||||| said:
lol, you need to know it was because of the wrong VBmeta file.
I wondern why the manuals can't be clearer sometimes.
Just like the TWRP tutorial - somehow you need to have the right vbmeta in Hand, but nothing more about this and where to get the proper one.
Whatever, it helped to relock Bootloader and to make a clean install with CSC (not HOME_CSC), then the files and sizes got right again.
Also re-partition helps in this case.
Anyway it's really frustrating to root these days, but at least we still can do this.
Without root many things would suck alot... i would not buy a phone without the possibility of it.
Click to expand...
Click to collapse
@moogle
The vbmeta.img is included in the TWRP.tar
https://forum.xda-developers.com/ga...overy-twrp-3-4-0-0-galaxy-a20e-a202f-t4141767
This is the Android 10 version
You need to upgrade first
physwizz said:
@moogle
The vbmeta.img is included in the TWRP.tar
https://forum.xda-developers.com/ga...overy-twrp-3-4-0-0-galaxy-a20e-a202f-t4141767
This is the Android 10 version
You need to upgrade first
Click to expand...
Click to collapse
This is the tutorial I was following, I unlocked, flashed TWRP and rooted successfully but SD card storage seems to be operating strangely.
What do you recommend to diagnose / fix?
moogle said:
This is the tutorial I was following, I unlocked, flashed TWRP and rooted successfully but SD card storage seems to be operating strangely.
What do you recommend to diagnose / fix?
Click to expand...
Click to collapse
Stock or GSI
physwizz said:
Stock or GSI
Click to expand...
Click to collapse
I cannot seem to get a GSI installed successfully, many of the tutorials say to use an AB partition GSI but the treble partition check says the SM-A202F/DS isn't an AB partition device.
It says:
"Your device does not support Seamless System Upgrades and is detected to have an A-only system partition."
moogle said:
I cannot seem to get a GSI installed successfully, many of the tutorials say to use an AB partition GSI but the treble partition check says the SM-A202F/DS isn't an AB partition device.
It says:
"Your device does not support Seamless System Upgrades and is detected to have an A-only system partition."
Click to expand...
Click to collapse
A205 is fake ab ( a plus SAR)
Send pm to a202 users
did you mean to write a202?
moogle said:
did you mean to write a202?
Click to expand...
Click to collapse
ask @Xyn XDotnest or @Wire1122
Send a personal message
I don't have a202
I have a205yn
||||| said:
lol, you need to know it was because of the wrong VBmeta file.
I wondern why the manuals can't be clearer sometimes.
Just like the TWRP tutorial - somehow you need to have the right vbmeta in Hand, but nothing more about this and where to get the proper one.
Whatever, it helped to relock Bootloader and to make a clean install with CSC (not HOME_CSC), then the files and sizes got right again.
Also re-partition helps in this case.
Anyway it's really frustrating to root these days, but at least we still can do this.
Without root many things would suck alot... i would not buy a phone without the possibility of it.
Click to expand...
Click to collapse
Which model of the a20e did you have?