Hello guys,I tried to root my Honor 7A with no success and now I'm in a bootloop situation.
I first unlocked bootloader succesfully with dc-unlocker2client. Then I installed this TWRP version 0.4 with adb fastboot:
https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447
I couldn't get other TWRP to work.Finally in TWRP I tried to install Magicsk (several versions-18,17,16) but it came up with error 1.
I've dowloaded stock rom AUM-L29C185CUSTC185D1B140 from official site, extracted ABOOT.img, tried to flash it but no success,something wrong with partition, but I cant recall exactly.Then I accidentally did this: fastboot flash ramdisk ABOOT.img .Bootloop!!
I tried to flash extracted ramdisk,kernel,recovery_ramdisk again but still the same issue.I did 2 factory resets in stock recovery but the problem persists.
Please can anyone help?Is my phone wasted??
Anyone please?
michael976 said:
Anyone please?
Click to expand...
Click to collapse
I'm able to be in fastboot mode with adb.Someone to point to the right steps of flashing the stock rom to unbrick the phone please?Merry Christmas to all!
Problem solved!Admin can close the thread!
How did you solved this problem please can you tell me
How you solve it? I GOT SAME SITUATION NOW
Died thread? How u solve it?
Related
Hi,
i was on exodus and recently moved to oos 3.1.4 after flashing he new bootloader and then the debloated rom that i found here for OOS3.1.4.After that i cud boot into the modified twrp but when i faced freezes i thought of going back to fully stoock.However even after flashing OOS3.1.4 stock i am unable to see OOS recovery.When i move into \bootloader mode i end up with just a one plus symbol.
i tried flashing OPX recovery using adb and fastboot but to no avail.I then tried flashing modified twrp.That worked but no matter what i do i can neither install OPX recovery nor can i use the mega unbrick guide as my phone shows up as relink USB.....
Could somebody please guide me?
sand87ch said:
Hi,
i was on exodus and recently moved to oos 3.1.4 after flashing he new bootloader and then the debloated rom that i found here for OOS3.1.4.After that i cud boot into the modified twrp but when i faced freezes i thought of going back to fully stoock.However even after flashing OOS3.1.4 stock i am unable to see OOS recovery.When i move into \bootloader mode i end up with just a one plus symbol.
i tried flashing OPX recovery using adb and fastboot but to no avail.I then tried flashing modified twrp.That worked but no matter what i do i can neither install OPX recovery nor can i use the mega unbrick guide as my phone shows up as relink USB.....
Could somebody please guide me?
Click to expand...
Click to collapse
Go through the mm bootloader update threads and you will find your answer.
Thing is I have now installed OS 2.2.x.still the recovery is missing
Exodusche said:
Go through the mm bootloader update threads and you will find your answer.
Click to expand...
Click to collapse
Do u mean the mega unbrick guide?
sand87ch said:
Do u mean the mega unbrick guide?
Click to expand...
Click to collapse
No don't think you need that just issue with how you updated your bootloader. Go through similar threads as yours and you will find your answer.
havent found an answer.Thats because very thread speaks of installing twrp modified etc.i already said i am able to do that.What i am unable is that even after flashing OOS3.1.4 without root i am not able to see oos recovery.also flashing oos recovery seperately doesnt fix it.it just then gives me the one +logo on vol down+power...until i flash twrp bluspark again.how to return my phn to factory condition?can somebody who has faced this help me?
This is now resolved.the mega unbrick guide is good but there's a catch.smtimes u don't get the qusb_bulk.i have seen one for one plus two to fix the RELINK_USB issue but that too never worked.what finally worked was one written for mui for Xiaomi in particular and for devices in general.
Brothers!!!!!!
Need help for my YU yuphoria... I got a OTA update for lineage 14.1. Downloaded and tried to install via TWRP. But got stuck with TWRP recovery. While click the reboot after installing the Rom, the phone is rebooting again into TWRP. For solving this, i tried with two methods as follows:
1) Tried to run command in TWRP Terminal. But after typing the command, dont know where is the enter button to run this!!!!!!!
2) Also tried to flash a rom through by Qualcomm Flash tool. But failed to this also, because download mode not working!!!!
Need help in an URGENT BASIS!!!!!!!!!!!!!!!!DONT KNOW WHAT TO DO!!!!!!!!!!! PLZZZZZZ
Saravanan Yumasher said:
Brothers!!!!!!
Need help for my YU yuphoria...
<Snip>
Click to expand...
Click to collapse
Why don't you just try flashing a custom rom when you've twrp?
Saravanan Yumasher said:
Brothers!!!!!!
Need help for my YU yuphoria... I got a OTA update for lineage 14.1. Downloaded and tried to install via TWRP. But got stuck with TWRP recovery. While click the reboot after installing the Rom, the phone is rebooting again into TWRP. For solving this, i tried with two methods as follows:
1) Tried to run command in TWRP Terminal. But after typing the command, dont know where is the enter button to run this!!!!!!!
2) Also tried to flash a rom through by Qualcomm Flash tool. But failed to this also, because download mode not working!!!!
Need help in an URGENT BASIS!!!!!!!!!!!!!!!!DONT KNOW WHAT TO DO!!!!!!!!!!! PLZZZZZZ
Click to expand...
Click to collapse
Why don't you try flashing a new ROM like sachin said? Also, did you make sure you didn't download a corrupted file?
Also, I think the enter button of TWRP keyboard is the checkmark in blue...
Saravanan Yumasher said:
Brothers!!!!!!
Need help for my YU yuphoria... I got a OTA update for lineage 14.1. Downloaded and tried to install via TWRP. But got stuck with TWRP recovery. While click the reboot after installing the Rom, the phone is rebooting again into TWRP. For solving this, i tried with two methods as follows:
1) Tried to run command in TWRP Terminal. But after typing the command, dont know where is the enter button to run this!!!!!!!
2) Also tried to flash a rom through by Qualcomm Flash tool. But failed to this also, because download mode not working!!!!
Need help in an URGENT BASIS!!!!!!!!!!!!!!!!DONT KNOW WHAT TO DO!!!!!!!!!!! PLZZZZZZ
Click to expand...
Click to collapse
Is your problem solved? You should reply...
DarkAlpha.Sete said:
Is your problem solved? You should reply...
Click to expand...
Click to collapse
sorry for not replying bro......
Thank you so much for your help.... your solution worked out for me... :good:
Hi,
As descripted in the title I can not restore my Honor 9 Anymore... I don't know what I did wrong but when I flash a new recovery or so in Fastboot I get the error "partion length error")
Any idea how I can fix this?
I have access to:
- TWRP Oreo (ADB not working)
- Fastboot Mode
- E-Recovery.
Do You used this command?:
fastboot flash recovery_ramdisk "name of your recovery"
4r44444 said:
Hi,
As descripted in the title I can not restore my Honor 9 Anymore... I don't know what I did wrong but when I flash a new recovery or so in Fastboot I get the error "partion length error")
Any idea how I can fix this?
I have access to:
- TWRP Oreo (ADB not working)
- Fastboot Mode
- E-Recovery.
Click to expand...
Click to collapse
Hello, I'm in Italy too I have the same problem are on oreo B360 C432 and 'I have only erecovery and bootloader flapped. IF you solved, please tell me how you did it. thank you
The same problem, with b 183 I was updating to b360, but after updating my phone just stands in Huawei eRecovery. I'm trying eRecovery and I can not find anything. 2 days I'm trying stock rom via sd card (dload) and nothing. I read the entire xda website and they do not help me. so please help me. my phone is locked and FRP locked. Essentially, I had this update through FF and after that the phone just stopped in eRecovery mode, and nothing has helped me for 2 days, my eyes are like the owl
comibumbar said:
The same problem, with b 183 I was updating to b360, but after updating my phone just stands in Huawei eRecovery. I'm trying eRecovery and I can not find anything. 2 days I'm trying stock rom via sd card (dload) and nothing. I read the entire xda website and they do not help me. so please help me. my phone is locked and FRP locked. Essentially, I had this update through FF and after that the phone just stopped in eRecovery mode, and nothing has helped me for 2 days, my eyes are like the owl
Click to expand...
Click to collapse
I've just solved with DC PHOENIX. What is fundamental is to put the same firmware before the brick. You can do it yourself using the appropriate section.
I got into this problem and fixed it.
I downloaded treble os and flashed it in fastboot then used adb commands to restore mine
superuser590 said:
I got into this problem and fixed it.
I downloaded treble os and flashed it in fastboot then used adb commands to restore mine
Click to expand...
Click to collapse
Can you explain it to me? I'm in the same situation right now.
themagicalmage22 said:
Can you explain it to me? I'm in the same situation right now.
Click to expand...
Click to collapse
Did you fix it or do you still need help?
Hello XDA!
I am writing this thread to ask for help rooting my Samsung Galaxy J2 Pro.
I attempted to use apps such as: Framaroot, Kingroot, etc.. but so far none of them have worked and I have not been able to find a working guide on the internet of how to root my phone.
I also tried installing an unofficial version of TWRP for my phone but everytime I tried to boot into the recovery it would say "No Command" and then boot into the original recovery.
Is anyone able to help me root my phone? Can it even be done?
Any help is sincerely appreciated. Thanks!
Phone Specifications:
Samsung Galaxy J2 Pro.
SM-J250G
Android Version: 7.1.1
Bumpity Bump
Try this at your own risk
Make a backup before trying
I got root access with this method
Download stock Rom from sammobile extract and there should be 5 MD5 files extract the AP file with 7z and copied boot.img on to sdcard
Installed MagicalMmanager-7 used it to patch the boot.img to a tar file
Copied the boot image to my pc desktop then flashed the boot with odin
When I booted it back up magisk manager kept crashing so I uninstalled it and installed magiskmanager-5.23 rebooted it opened magisk and followed the prompts to update it
:good:
putzwon said:
Try this at your own risk
Make a backup before trying
I got root access with this method
Download stock Rom from sammobile extract and there should be 5 MD5 files extract the AP file with 7z and copied boot.img on to sdcard
Installed MagicalMmanager-7 used it to patch the boot.img to a tar file
Copied the boot image to my pc desktop then flashed the boot with odin
When I booted it back up magisk manager kept crashing so I uninstalled it and installed magiskmanager-5.23 rebooted it opened magisk and followed the prompts to update it
Click to expand...
Click to collapse
Hello there.
I have tried to patch my boot.img but when I put into a .tar and flash it, it doesn't flash, it's just stuck on file analysis despite being able to flash other files. Would you be able to send me a copy of your boot.img, thanks.
Kindest Regards
-Jayden
JaydenATC said:
Hello XDA!
I am writing this thread to ask for help rooting my Samsung Galaxy J2 Pro.
I attempted to use apps such as: Framaroot, Kingroot, etc.. but so far none of them have worked and I have not been able to find a working guide on the internet of how to root my phone.
I also tried installing an unofficial version of TWRP for my phone but everytime I tried to boot into the recovery it would say "No Command" and then boot into the original recovery.
Is anyone able to help me root my phone? Can it even be done?
Any help is sincerely appreciated. Thanks!
Phone Specifications:
Samsung Galaxy J2 Pro.
SM-J250G
Android Version: 7.1.1
Click to expand...
Click to collapse
Hi Jayden
I've got exactly the same problem. Have you worked this out eventually? Please help!
MC
qichen said:
Hi Jayden
I've got exactly the same problem. Have you worked this out eventually? Please help!
MC
Click to expand...
Click to collapse
Unfortunately I have not found a solution. Please notify me if you find one.
here is a copy of my boot.img after flashing this you will get a verification problem and you will have to reset your phone if it bootloops into recovery or starts to update and says no command take battery out put it back in and boot it again or boot in to odin mode and push down and boot it eventually it will boot in to recovery then factory reset it. first boot may take 5-10 minutes
my software version is J250GDXU2ARD3_J250GXSA2ARD3_XSA
putzwon said:
here is a copy of my boot.img after flashing this you will get a verification problem and you will have to reset your phone if it bootloops into recovery or starts to update and says no command take battery out put it back in and boot it again or boot in to odin mode and push down and boot it eventually it will boot in to recovery then factory reset it. first boot may take 5-10 minutes
my software version is J250GDXU2ARD3_J250GXSA2ARD3_XSA
Click to expand...
Click to collapse
Hello and thanks a lot! I flashed my boot image and now when it boots it says "Set Warranty Bit : Kernel" and an infinite booting screen.
What do I do from here? or do I need to flash the original rom?
don't worry about "Set Warranty Bit : Kernel" mine does it too here is another boot.img after i flashed this i got verification failed so i used 7z to tar userdata.img.ext4 i extracted from the AP image i got the boot.img from.
i put boot in BL and userdata in AP and flashed it. it fired up as normal and then i installed magisk apk
JaydenATC said:
Hello and thanks a lot! I flashed my boot image and now when it boots it says "Set Warranty Bit : Kernel" and an infinite booting screen.
What do I do from here? or do I need to flash the original rom?
Click to expand...
Click to collapse
Flash the original rom then flash boot and userdata as i explain in next post
Hey, sorry for the late response. Everything is working fine! I now have superuser abilities but everytime I try to flash my recovery with TWRP it just loads the stock recovery. I even tried removing certain files from the root folder to avoid the stock recovery being flashed but it hasn't worked.
Any idea? Ps. You are a life saver my man.
JaydenATC said:
Hey, sorry for the late response. Everything is working fine! I now have superuser abilities but everytime I try to flash my recovery with TWRP it just loads the stock recovery. I even tried removing certain files from the root folder to avoid the stock recovery being flashed but it hasn't worked.
Any idea? Ps. You are a life saver my man.
Click to expand...
Click to collapse
glad i could help and i don't think there is an official twrp for this device here is one i ported a couple things still don't work mtp and sideload but it's not really usable until someone ports a rom due to the data encryption which you have to format to be able to flash anything
putzwon said:
glad i could help and i don't think there is an official twrp for this device here is one i ported a couple things still don't work mtp and sideload but it's not really usable until someone ports a rom due to the data encryption which you have to format to be able to flash anything
Click to expand...
Click to collapse
Hello,
Sorry, I don't have the J250G anymore as I traded it for a J5.
Kindest Regards
Jayden
My internal storage showed I only have 8gb instead of 16gb. Is there a fix for this?
P.S. Wiping data fixes it
ok
You can extract it from the AP file from stock firmware using 7z
hey
hey everyone im just wondering but is there a kernel for this device yet or any rom ("J250G")
So I accidentally flashed a wrong boot.img while on my current ROM (AOSiP 8.1) The wrong flash caused my system to be somewhat destroyed (Can't mount and others). The only hope I had was to do the FastBoot method which somehow worked but returned me to MIUI 9.
I did all the rooting and recovery process again and decided to flash the AOSiP ROM again with the proper procedures but as soon as I install after wiping I get the error something like "twfunc failed to flash repacked image". I thought it was just a corrupt download but after downloading twice and using another ROM it was still the same. Can somebody please help me? It's a hassle going through the FastBoot flash method again and it might get worse if not yet fixed ASAP.
ClockUpEx said:
So I accidentally flashed a wrong boot.img while on my current ROM (AOSiP 8.1) The wrong flash caused my system to be somewhat destroyed (Can't mount and others). The only hope I had was to do the FastBoot method which somehow worked but returned me to MIUI 9.
I did all the rooting and recovery process again and decided to flash the AOSiP ROM again with the proper procedures but as soon as I install after wiping I get the error something like "twfunc failed to flash repacked image". I thought it was just a corrupt download but after downloading twice and using another ROM it was still the same. Can somebody please help me? It's a hassle going through the FastBoot flash method again and it might get worse if not yet fixed ASAP.
Click to expand...
Click to collapse
Did you try using redwolf recovery? Also do this. Go to en.miui.com and dl the latest miui zip. Using redwolf try to flash it. If you are able to do it then possibly it's something with stock twrp. If not then you might need to fastboot flash miui again. The last option would be to use edl mode.
I tried FastBoot method flashing the latest MIUI 9 build. Worked out fine but after Rooting again and adding Recovery, flashing ROMs give me Error7 most of the time. What I did is I accidentally clicked the Clear All on the MiFlash and resulted to my problem being fixed while losing all files in my internal. Noooooo!
ClockUpEx said:
I tried FastBoot method flashing the latest MIUI 9 build. Worked out fine but after Rooting again and adding Recovery, flashing ROMs give me Error7 most of the time. What I did is I accidentally clicked the Clear All on the MiFlash and resulted to my problem being fixed while losing all files in my internal. Noooooo!
Click to expand...
Click to collapse
Soo? Is it fixed now? Is that what you mean?