I need help. I relocked my bootloader, and now my phone (OP7P) won't even turn on - OnePlus 7 Pro Questions & Answers

So over the past day I had rooted my oneplus 7 pro and all was going well until I decided to delete the netflix stock application. Then I restarted my phone from holding the power button and pressing restart and then I booted into fastboot. Everytime I pressed start it would send me back to fastboot but I was able go to twrp recovery. Stupidly, I wiped the whole phone thinking I had no other options. Then after that, I found a setting in advanced that allowed me to leave recovery mode I think? Whatever it was, I was booted back into the oneplus start screen and reset up my phone. Then I tried to re-root my phone and couldn't get it to work because it said the magisk zip file was corrupt. Then I just decided to give up and go back to stock.
Little did I no, you are NOT supposed to relock the bootloader, because that is exactly what I did. After doing that, I got a message saying my phone was corrupt and I looked up quick solution and it said to press my volume buttons and power buttons. Now my phone won't even turn on. I am freaking out right now, knowing that my phone is probably bricked and I am going to have to pay probably a third of what I even paid for this phone to get it fixed. When I plug my phone into my pc the device is shown as "QUSB_BULK_CID:0404_SN:3BB285D7". If any of you guys can help, I'm all ears.
edit: I meant I locked oem/bootloader. Also, I got the phone to power on. It is in a bootloop where the oneplus logo shows up and then it gives me the message "Your device is corrupt. it can't be trusted and will not boot"
edit 2: After two hours, I finally fixed it. I downloaded the MSM tool and found the qualcomm drivers and after a few trial and errors, I finally got it to work

gotdiamonds99 said:
So over the past day I had rooted my oneplus 7 pro and all was going well until I decided to delete the netflix stock application. Then I restarted my phone from holding the power button and pressing restart and then I booted into fastboot. Everytime I pressed start it would send me back to fastboot but I was able go to twrp recovery. Stupidly, I wiped the whole phone thinking I had no other options. Then after that, I found a setting in advanced that allowed me to leave recovery mode I think? Whatever it was, I was booted back into the oneplus start screen and reset up my phone. Then I tried to re-root my phone and couldn't get it to work because it said the magisk zip file was corrupt. Then I just decided to give up and go back to stock.
Little did I no, you are NOT supposed to relock the bootloader, because that is exactly what I did. After doing that, I got a message saying my phone was corrupt and I looked up quick solution and it said to press my volume buttons and power buttons. Now my phone won't even turn on. I am freaking out right now, knowing that my phone is probably bricked and I am going to have to pay probably a third of what I even paid for this phone to get it fixed. When I plug my phone into my pc the device is shown as "QUSB_BULK_CID:0404_SN:3BB285D7". If any of you guys can help, I'm all ears.
edit: I meant I locked oem/bootloader. Also, I got the phone to power on. It is in a bootloop where the oneplus logo shows up and then it gives me the message "Your device is corrupt. it can't be trusted and will not boot"
edit 2: After two hours, I finally fixed it. I downloaded the MSM tool and found the qualcomm drivers and after a few trial and errors, I finally got it to work
Click to expand...
Click to collapse
U probably should have flashed stock firmware before relocking the bootloader

As long as you can boot into fastboot you should be good. Make sure you have correct drivers etc etc. Boot into fastboot and just boot into twrp, don't flash. Wipe data, system, vendor, dalv, cache. Recheck on what to delete and what order because it has to be the correct things and I might be mixed up off the top of my head, delete them in twrp. Then boot back into twrp after all that and reflash your custom rom. Take note if your ****s bricked you wont be able to install the zip via regular twrp swipe, you will have to use twrp sideload feature with adb and install from pc and install it that way. If that doesn't work at all just do a complete reflash of stock firmware via fastboot. Reflashing custom should work though I got mine out of a brick this way. As long as fastboots working you can get out of anything. Also Linux is 100x better than other OSs for this stuff.

cuNezzar said:
As long as you can boot into fastboot you should be good. Make sure you have correct drivers etc etc. Boot into fastboot and just boot into twrp, don't flash. Wipe data, system, vendor, dalv, cache. Recheck on what to delete and what order because it has to be the correct things and I might be mixed up off the top of my head, delete them in twrp. Then boot back into twrp after all that and reflash your custom rom. Take note if your ****s bricked you wont be able to install the zip via regular twrp swipe, you will have to use twrp sideload feature with adb and install from pc and install it that way. If that doesn't work at all just do a complete reflash of stock firmware via fastboot. Reflashing custom should work though I got mine out of a brick this way. As long as fastboots working you can get out of anything. Also Linux is 100x better than other OSs for this stuff.
Click to expand...
Click to collapse
OK here's the order. Boot into twrp, don't flash.
Wipe -> ADVANCED -- select system + vendor -> SWIPE TO WIPE
reboot bootloader
fastboot boot back into twrp
-- then --
Format data, Wipe cache & dalvik-cache
Flash ROM.
Then reboot system. Boom.
Remember you will most likely have to flash the ROM via sideload. As transferring will not work in a bricked phone.

cuNezzar said:
As long as you can boot into fastboot you should be good. Make sure you have correct drivers etc etc. Boot into fastboot and just boot into twrp, don't flash. Wipe data, system, vendor, dalv, cache. Recheck on what to delete and what order because it has to be the correct things and I might be mixed up off the top of my head, delete them in twrp. Then boot back into twrp after all that and reflash your custom rom. Take note if your ****s bricked you wont be able to install the zip via regular twrp swipe, you will have to use twrp sideload feature with adb and install from pc and install it that way. If that doesn't work at all just do a complete reflash of stock firmware via fastboot. Reflashing custom should work though I got mine out of a brick this way. As long as fastboots working you can get out of anything. Also Linux is 100x better than other OSs for this stuff.
Click to expand...
Click to collapse
I don't know if u realize this but he said that he relocked the bootloader after installing twrp and root

Austinredstoner said:
I don't know if u realize this but he said that he relocked the bootloader after installing twrp and root
Click to expand...
Click to collapse
Austinredstoner said:
I don't know if u realize this but he said that he relocked the bootloader after installing twrp and root
Click to expand...
Click to collapse
Damn forgot about that. Yeah In that case its most likely bricked to hell OP with no method of recovery as far as I know.

Related

[Q] Bricked Nexus 5

Hello
I followed this guide http://forum.xda-developers.com/show....php?t=2507905 to root my new Nexus 5 and flashed this rom http://forum.xda-developers.com/show....php?t=2528265 onto it, when I tried to boot it up it got stuck in the boot animation so I rebooted into recovery and wiped the data, cache partition and the dalvik cache and tried to boot it up and encountered the same problem so I went to reboot and it wont boot back up not even to the bootloader and when I plug it into my pc its unrecognized and wont even show charging animations
Did I brick my new phone?
Smragnol said:
Hello
I followed this guide http://forum.xda-developers.com/show....php?t=2507905 to root my new Nexus 5 and flashed this rom http://forum.xda-developers.com/show....php?t=2528265 onto it, when I tried to boot it up it got stuck in the boot animation so I rebooted into recovery and wiped the data, cache partition and the dalvik cache and tried to boot it up and encountered the same problem so I went to reboot and it wont boot back up not even to the bootloader and when I plug it into my pc its unrecognized and wont even show charging animations
Did I brick my new phone?
Click to expand...
Click to collapse
Press and hold volume up then connect usb cable, what the result?
bitdomo said:
Press and hold volume up then connect usb cable, what the result?
Click to expand...
Click to collapse
same as above, nothin.
Smragnol said:
same as above, nothin.
Click to expand...
Click to collapse
Then it is bricked , but I don't really understand how could fromating data, cache and dalvik cache destroy the bootloader . There must be something wrong those recoveries, because you are not the only one
Did you ever check the md5 of the rom you flashed? It could have been a corrupted download
does your bootloader work? hold the vol up/down and power on boot. if u can get to the bootloader u can save it with wugs nexus tool.
malibu_23 said:
does your bootloader work? hold the vol up/down and power on boot. if u can get to the bootloader u can save it with wugs nexus tool.
Click to expand...
Click to collapse
If you can get into bootloader you can save it without a tool kit.
Do this if u can't go into recovery
http://forum.xda-developers.com/showthread.php?t=2513937
But if u are able to go into recover, just flash any other rom, make sure you before flashing u do a factory data reset, and after finished wipe cache/dalvik always so u dont go into bootloops.
Through some miracle I was able to get to the bootloader (sat there and held the vol and power buttons for like 3 minutes while my pc dinged and donged as it disconnected and reconnected) but I'm unsure of what to do now. Should I keep trying to load a custom rom on it or just go back to stock? and either or how am I going to get the rom on the internal storage as its still not being recognized by my pc (but I do have fast boot access)
Smragnol said:
Through some miracle I was able to get to the bootloader (sat there and held the vol and power buttons for like 3 minutes while my pc dinged and donged as it disconnected and reconnected) but I'm unsure of what to do now. Should I keep trying to load a custom rom on it or just go back to stock? and either or how am I going to get the rom on the internal storage as its still not being recognized by my pc (but I do have fast boot access)
Click to expand...
Click to collapse
I'd flash the factor image with fastboot and start all over
Do this if u can't go into recovery
http://forum.xda-developers.com/showthread.php?t=2513937
But if u are able to go into recover, just flash any other rom, make sure you before flashing u do a factory data reset, and after finished wipe cache/dalvik always so u dont go into bootloops.
Stay away from tool kits. You got enough problems on your hand
Alright so I got the stock os flashed on there and booted up and everything is looking goood, thanks guys for all your help I'll be sure to come back if I have any more problems
Smragnol said:
Alright so I got the stock os flashed on there and booted up and everything is looking goood, thanks guys for all your help I'll be sure to come back if I have any more problems
Click to expand...
Click to collapse
Glad to hear you're back up and running. Google md5 checksum and make sure the roms you download are good. I think that was your problem
Done this to my Nexus 7.. something went wrong when flashing the Rom and ended up somehow cocking up my drivers aswell.. Weird one.
Glad to hear your back up and running buddy.

Shield doesnt boot anymore

So guys, i've done it. I bring my first device.
Yesterday i tried to downgrade via fastboot with this recovery images https://developer.nvidia.com/gameworksdownload (yes is choose the right ones)
flash boot, check
flash recovery, check
flash system, failes (insufficient memory)
erase sytem, check
flash system, failed (insufficient memory)
flash twrp, check, but no usb mouse so
flash cwm, check
factory reset, check
rom.zip and gapps on sd card, check
reboot, boot into bootloader, no chance
It boots everytime normal, so i cant enter the recovery.
Connect it to charger, check
charging led lights up, check
Go sleeping, check
doenst boot into bootloader :/
Back to charger
Now I wanted to try it again and i wont even boot.
Anyone has an Idea? Or is it really bricked?
Can you still see the device listed using fast boot?
No, because I can't enter the bootloader or the recovery. But it boots again
...
The same thing just happened to me. Unfortunately, I am still trying to figure it out. I flashed a "stock" recovery that I had found in order to be able to take the OTAs. Now when I boot, I just stay stuck on the NVIDIA splash screen.....been there for hours.
rafaelvelasquez2 said:
The same thing just happened to me. Unfortunately, I am still trying to figure it out. I flashed a "stock" recovery that I had found in order to be able to take the OTAs. Now when I boot, I just stay stuck on the NVIDIA splash screen.....been there for hours.
Click to expand...
Click to collapse
Same here.....
Mine is working again. Booting in the bootloader is a little bit tricky.
Have you tried to flash all? Boot.img, recovery.img and system.img?
...
I had the same issue. But after trying to get into the bootloader using POWER + VOLUME DOWN for about 15 minutes it finally went to the bootloader and I was able to re-flash it. I have a feeling it's the cludgy power button.
You do not need to flash the stock recovery to take the ota. I have taken 2 otas now on custom recovery without any issue and without loosing root. Just an FYI.
Sent from my SHIELD Tablet using XDA Free mobile app
I just did a factory reset under lollipop, locked boot-loader rooted and it rebooted to the green android screen then dropped into CWM and asked to fix root. I said no, then it went to the nvidia boot logo and it is stuck. Any suggestions? Thanks.
Edit: nevermind, I just powered it off after about 20 minuets and it hung again. When I plugged it into my pc, it finally poped into the setup/welcome screen. Pretty weird. Heart attack averted

stuck in loop, possibly a different kind of loop

I was trying to fix my girlfriends nexus 5 that was doing the restart loop after an update. Everything seemed to go fine. Unlocked the bootloader, etc. Flashed the newest rom (6.0.1 (MMB29S) ce1d670f61061c3902f3997510ea55d7 6bfcdfa4f4840898e5d76fa044f5e6a0f71343bf) and then something obviously went wrong (not quite sure, dont think i touched anything) and it's now stuck in a different kind of loop that only loops while it's plugged in. Ive uploaded a video to youtube, but since im a new user i cant actually link it properly yet. Hopefully this wont annoy any mods, I promise it's not spam. youtube . be / yNSoiTPnGZw
Is there any way to get it to stay on for more than a couple seconds to retry the flashing?
Any help is appreciated.
atomkrieg said:
I was trying to fix my girlfriends nexus 5 that was doing the restart loop after an update. Everything seemed to go fine. Unlocked the bootloader, etc. Flashed the newest rom (6.0.1 (MMB29S) ce1d670f61061c3902f3997510ea55d7 6bfcdfa4f4840898e5d76fa044f5e6a0f71343bf) and then something obviously went wrong (not quite sure, dont think i touched anything) and it's now stuck in a different kind of loop that only loops while it's plugged in. Ive uploaded a video to youtube, but since im a new user i cant actually link it properly yet. Hopefully this wont annoy any mods, I promise it's not spam. youtube . be / yNSoiTPnGZw
Is there any way to get it to stay on for more than a couple seconds to retry the flashing?
Any help is appreciated.
Click to expand...
Click to collapse
What was your flashing procedure, did u is a toolkit or do it manually, can u get it into bootloader or recovery? What files did u is for update and where did u get them?
Sent from my XT1526 using Tapatalk
soupysoup said:
What was your flashing procedure, did u is a toolkit or do it manually, can u get it into bootloader or recovery? What files did u is for update and where did u get them?
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
First i followed the guide here on xda to unlock the bootloader(guide-nexus-5-how-to-unlock-bootloader-t2507905), installed twrp, which went fine. Then i realized that i couldnt (or didnt realize how to via command line) to copy the stock rom and install it via twrp, so then i followed this guide here on xda (tutorial-how-to-flash-factory-image-t2513701) with the factory img (6.01 hammerhead), got to this point in the guide: ★After everything finished, select "Recovery" using the volume buttons. then it stalled out,turned off and now just cycles on and offf through the google logo with the lock picture or if i hold down the volume button it will go into the bootloader briefly then restart, rinse repeat.
atomkrieg said:
First i followed the guide here on xda to unlock the bootloader(guide-nexus-5-how-to-unlock-bootloader-t2507905), installed twrp, which went fine. Then i realized that i couldnt (or didnt realize how to via command line) to copy the stock rom and install it via twrp, so then i followed this guide here on xda (tutorial-how-to-flash-factory-image-t2513701) with the factory img (6.01 hammerhead), got to this point in the guide: ★After everything finished, select "Recovery" using the volume buttons. then it stalled out,turned off and now just cycles on and offf through the google logo with the lock picture or if i hold down the volume button it will go into the bootloader briefly then restart, rinse repeat.
Click to expand...
Click to collapse
Have u tried messing with the power button, there are a lot of issues on the nexus 5 with the power button causing loops, simply from getting stuck, try playing with the power button a little and see of that helps, it might just need to be replaced
Wait, did u flash the factory img with twrp, or did u flash it using fastboot?
Sent from my XT1526 using Tapatalk
soupysoup said:
Have u tried messing with the power button, there are a lot of issues on the nexus 5 with the power button causing loops, simply from getting stuck, try playing with the power button a little and see of that helps, it might just need to be replaced
Wait, did u flash the factory img with twrp, or did u flash it using fastboot?
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
in the end fastboot, since i coulndt see how i could copy the img over to install via twrp
im pretty sure the button is fine, since it was cycling from the ota update install, then was working fine unlocking the bootloader, but after the flash, it crapped the bed.
Different problem
I had a problem where the google logo keeps on booting up with a slight vibration.This started to happen when my was dropped.I initially thought that was a software issue and thought of installing new ROM's but eventually my device was not detected :crying:
So i took it to repair shop near my house and they said it would cost 2500
I did some google research and found the reason was due to the power button being stucked during the fall.I got that repaired and my device is good to go
siddhu007 said:
I had a problem where the google logo keeps on booting up with a slight vibration.This started to happen when my was dropped.I initially thought that was a software issue and thought of installing new ROM's but eventually my device was not detected :crying:
So i took it to repair shop near my house and they said it would cost 2500
I did some google research and found the reason was due to the power button being stucked during the fall.I got that repaired and my device is good to go
Click to expand...
Click to collapse
ok, took it into a shop, got the power button fixed. It must have been on the way out because literally one minute it worked and the second it didnt. now i think ive got it narrowed down. it's saying it's unable to mount /persist. ive tried the various fixes:
e2fsck/dev/block/platform/msm_sdcc.1/by-name/persist
and
make_ext4fs/dev/block/platform/msm_sdcc.1/by-name/persist
but all i get is a not found error. not sure what to do from here on.
success!! i ended up stumbling on a bit how to restore the persist partition i didnt try. got a custom rom installs and everything works. thanks to everyone who tried to help!!
stuck in bootloop while flashing cataclysm rom
i tried to flash cataclysm rom in my n5..i unlock bootloader, flash custom recovery using TWRP and flash cataclysm rom following the instructions in this thread http://forum.xda-developers.com/goo...s-5-how-to-unlock-bootloader-t2507905...after that it was stuck in bootloop...i tried to open recovery but it wont open anymore it will only go back to loop....how can open the recovery? is it safe to flash CWM recovery?..tnx in advance..
When it was stuck in the loop, I had to hold vol up and down with the power button (wait a few secs until it was completely off) then reboot holding down + power till it opened the bootloader. if that doesnt work, try reflashing the bootloader via fastboot. I only found out i couldnt mount the persist partition by looking at the terminal window in twrp after trying to install a rom which kept it in the boot loop. I then used the cmd: make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist to rebuild it.
jpau11 said:
i tried to flash cataclysm rom in my n5..i unlock bootloader, flash custom recovery using TWRP and flash cataclysm rom following the instructions in this thread http://forum.xda-developers.com/goo...s-5-how-to-unlock-bootloader-t2507905...after that it was stuck in bootloop...i tried to open recovery but it wont open anymore it will only go back to loop....how can open the recovery? is it safe to flash CWM recovery?..tnx in advance..
Click to expand...
Click to collapse
After flashing TWRP, use the volume and power button to select recovery. Once in TWRP, wipe cache, data, reboot.
audit13 said:
After flashing TWRP, use the volume and power button to select recovery. Once in TWRP, wipe cache, data, reboot.
Click to expand...
Click to collapse
problems solved!!i flashed TWRP again and it it already to the recovery so i reflashed the cataclysm rom and it worked...my n5 is now working..tnx guys!
jpau11 said:
problems solved!!i flashed TWRP again and it it already to the recovery so i reflashed the cataclysm rom and it worked...my n5 is now working..tnx guys!
Click to expand...
Click to collapse
Great to hear it. Congratulations:good:

Honor 8 Can't Download Firmware, Can't Flash, Bricked? [Solved]

Hi, after trying unlock my bootloader, I couldn't get into recovery mode without "Your phone cannot be trusted" getting stuck on my screen.
I re-locked the boot loader but now when I go into recovery it says "Data Partition is corrupted please format" then it asks me to connect to a wifi network which then just shows errors everytime the password comes up.
I tried to turn on USB Debugging to ADB sideload a firmware, but I can't because the phone has been resetted; if I try to enter a wifi password the keyboard doesnt show it's just the google voice (which doesn't work) with no options. If i skip the wifi option it just goes on the google login and gets stuck on "Checking Info".
Any solutions to the problem please?
EDIT: I just re-unlocked the bootloader and now its permanently stuck on "Your device cannot be trusted, booting now" regardless of what buttons I press during startup
EDIT 2: I fixed it, it was long and complicated but I got it to work, here's how.
1. When flashing TWRP, I realized I was flashing the TWRP for EMUI 4, so I flashed TWRP for EMUI 5. (Make sure Bootloader is unlocked)
First have all the adb/fastboot drivers, for windows shift + right click the folder and click "Open Command here"
Make sure the twrp img file is in the same folder as the adb folder.
On the honor 8 phone, if it is stuck like mine, turn the phone off and then hold Volume Down + Power Button until the download mode is on the screen
Type "fastboot flash recovery (twrpfilename).img"
Once it's done, turn it off and then hold power button + volume up AND volume down at once till TWRP comes on
(Continuously hold it, if the "Your Device cannot be trusted" screen comes on release)
2. (Make sure internal storage and data are backed up externally for this)
Reset system, data, cache/dalvik, and internal storage
3. Download Update.zip and the second .zip from a website on google, search Honor 8 Manual Nougat and click the link from smartstocknews (I can't post links) but do not follow the steps from that website, and also download GAPPS from open GAPPS. Make sure ARM64 is selected and not ARM as well as 7.0
4. After wiping, mount the Honor 8 by connecting it via USB to a computer, and press "Mount" on TWRP
Upload the both update.zip and update_data_full_hw_eu.zip and GAPPS ARM64 7.0 to internal or external storage
5. Exit mount and go to install, install the zips in this specific order and do not reboot in between
A) Update.zip
B) Update_data_full_hw_eu.zip
C) GAPPS.zip
6. Reboot after GAPPS is done (it might show already installed, if that's the case then it's alright, reboot anyways)
Download the 70mb package for firmware downgrade and the latest marshmallow firmware from your regional huawei's website.
Extract the small package and put the .app file in a folder called dload on the SD card and insert it in your phone.
Boot by holding volume + volume - and pressing power, holding all 3 buttons until the phone vibrates.
The package will flash and afterwards you repeat the process, this time using an .app file from the full marshmallow firmware.
The 70mb package installs not matter how messed up your file system is, and makes your phone ready for the MM firmware. This process brings any brick back to life. Good luck.
I too was trying to root my FRD-L04 and apparently used the wrong TWRP because now I get...
Code:
Unable to open ' ' to wipe crypto key
Unable to wipe Data
Unable to format to remove encryption
Failed to mount /data (invalid argument)
and I cant get the keyboard loaded so I can log into my wifi when I do a factory reset. I really have no idea how best to attack this...my phone is bricked I can get into TWRP 3.0.2.0 recovery, sideload, and fastboot (i think). I am currently downloading the stock ROM for my device and will try to sideload it.
I feel I need to fix the data issues thought before trying to load the ROM as I dont think my data partition is working at all now. Does anyone have any suggestions or a step-by-step guide on how to fix my bricked phone?
I've tried all sort of things today but no matter what, I cant get a keyboard working so I guess that means I'm screwed....
EDIT - my phone doesnt have a insertable SD card so I cant fix things the way the above poster suggests.
menriquez said:
I too was trying to root my FRD-L04 and apparently used the wrong TWRP because now I get...
Code:
Unable to open ' ' to wipe crypto key
Unable to wipe Data
Unable to format to remove encryption
Failed to mount /data (invalid argument)
and I cant get the keyboard loaded so I can log into my wifi when I do a factory reset. I really have no idea how best to attack this...my phone is bricked I can get into TWRP 3.0.2.0 recovery, sideload, and fastboot (i think). I am currently downloading the stock ROM for my device and will try to sideload it.
I feel I need to fix the data issues thought before trying to load the ROM as I dont think my data partition is working at all now. Does anyone have any suggestions or a step-by-step guide on how to fix my bricked phone?
I've tried all sort of things today but no matter what, I cant get a keyboard working so I guess that means I'm screwed....
EDIT - my phone doesnt have a insertable SD card so I cant fix things the way the above poster suggests.
Click to expand...
Click to collapse
If you have nougat just flash the correct recovery from the twrp you already have. https://forum.xda-developers.com/honor-8/development/twrp-t3566563
sysak said:
If you have nougat just flash the correct recovery from the twrp you already have. https://forum.xda-developers.com/honor-8/development/twrp-t3566563
Click to expand...
Click to collapse
This is truly one of the worse phones I have ever had when it comes to root and such. My frustration over what, for a unbranded unlocked phone that *should* probably SHIP with root, this phone has and is putting me through is super high.
That being said...so I flashed the new 3.1.0.0 recovery. Before doing that, I had just tried to Unbrick the phone with flashing B162 image with 3.0.3.0...so now the phone is totally frozen in the "Your device has been unlocked and can't be trusted..." screen. Nothing I seem to do can get it out of this mode.
I want to install the rooted b378 boot.img file I just downloaded, but am unable to find the button commands to get the bootloader loaded. Does anyone have any suggestions in somehow trying to save the day with this damned phone?
much thanks in advance.
EDIT: So I got the phone in bootloader mode by pressing vol up/vol down/power and inserting the usb cable...i flashed the rooted boot.img and twrp 3.1.0.1 to both recovery and recovery2 and now i can get into recovery. I feel like I may actually have a chance now to fix this damn thing...
So can anyone point me in a direction where, from this point with the new recovery loaded and the modded boot image installed, where i can get this phone working?? ill use ANY ROM it dont really matter at this point...
Don't worry. It's really easy, once you know what to do, just realy easy to screw up if you don't. If your phone is a mess just roll back to android 6 using the procedure i described above. Once your phone works, update to nougat and install twrp and root following this guide: https://forum.xda-developers.com/honor-8/development/twrp-t3566563
Same issue
Ramonator said:
Hi, after trying unlock my bootloader, I couldn't get into recovery mode without "Your phone cannot be trusted" getting stuck on my screen.
I re-locked the boot loader but now when I go into recovery it says "Data Partition is corrupted please format" then it asks me to connect to a wifi network which then just shows errors everytime the password comes up.
I tried to turn on USB Debugging to ADB sideload a firmware, but I can't because the phone has been resetted; if I try to enter a wifi password the keyboard doesnt show it's just the google voice (which doesn't work) with no options. If i skip the wifi option it just goes on the google login and gets stuck on "Checking Info".
Any solutions to the problem please?
EDIT: I just re-unlocked the bootloader and now its permanently stuck on "Your device cannot be trusted, booting now" regardless of what buttons I press during startup
EDIT 2: I fixed it, it was long and complicated but I got it to work, here's how.
1. When flashing TWRP, I realized I was flashing the TWRP for EMUI 4, so I flashed TWRP for EMUI 5. (Make sure Bootloader is unlocked)
First have all the adb/fastboot drivers, for windows shift + right click the folder and click "Open Command here"
Make sure the twrp img file is in the same folder as the adb folder.
On the honor 8 phone, if it is stuck like mine, turn the phone off and then hold Volume Down + Power Button until the download mode is on the screen
Type "fastboot flash recovery (twrpfilename).img"
Once it's done, turn it off and then hold power button + volume up AND volume down at once till TWRP comes on
(Continuously hold it, if the "Your Device cannot be trusted" screen comes on release)
2. (Make sure internal storage and data are backed up externally for this)
Reset system, data, cache/dalvik, and internal storage
3. Download Update.zip and the second .zip from a website on google, search Honor 8 Manual Nougat and click the link from smartstocknews (I can't post links) but do not follow the steps from that website, and also download GAPPS from open GAPPS. Make sure ARM64 is selected and not ARM as well as 7.0
4. After wiping, mount the Honor 8 by connecting it via USB to a computer, and press "Mount" on TWRP
Upload the both update.zip and update_data_full_hw_eu.zip and GAPPS ARM64 7.0 to internal or external storage
5. Exit mount and go to install, install the zips in this specific order and do not reboot in between
A) Update.zip
B) Update_data_full_hw_eu.zip
C) GAPPS.zip
6. Reboot after GAPPS is done (it might show already installed, if that's the case then it's alright, reboot anyways)
Click to expand...
Click to collapse
I pretty much have the same issue. No keyboard showing, just the stupid voice thing, and the Bootloader is Relocked. How did you get it fully unlocked. I can't get it. I guess let me get that resolved first (the bootloader) and I can try to go from there. Please help me.
UPDATE: Never mind I fixed it. I'm not really for sure how either but I think it mainly was just persistence.
Didn't work
Hello, so earlier today I tried to install RROS newest version in hope to get magisk/unrooting my phone because I'm addicted to snapchat and I rooted my phone with SuperSU earlier but didn't know u can't login to snapchat after that. It failed idk why, (I followed instructions very clearly and searched info from internet before doing that) causing me to brick my phone so when I booted it, it only showed black screen. After couple hours not finding way to get into twrp with my circumstances I managed to flash boot, recovery and system images, I tried to reboot and see what happens, (just in case, I kinda knew I didn't had ROM installed at the time, I also was hoping RROS to boot) nothing happened expect my phone got stuck in boot screen for booting EMUI, which was not installed obviously. Again after couple hours I stumbled to your post and managed to finally get myself into TWRP, I followed again ur instructions and everything was going fine, no erros, not anything. When Gapps was finished installing, I rebooted and again it just got stuck into booting screen. I did press and hold Power button, vol+, vol- and got myself into some kind of ROM installing screen, (hard to explain I don't exactly know what is name of it) and no it wasn't Huawei erecovery screen (Power button & Vol+ and no it didn't work me either saying that "getting package info failed") so in that ROM installing screen it just was stuck at 5% installing, and now I don't know what to do. My phone got locked again and I'm stuck at booting screen.
Note:
I don't have SD Card, should I get one and install stock rom?
Sorry for being kinda unclear but I'm tired it was 7 hours ago I got my phone bricked and have surfed on the web finding for answers ever since.
Also as you might notice, yes, I'm new to modding devices etc but still I'm not totally noob. Please help ASAP.
[SOLVED] So after hour of watching netflix as depressed teen I tried to reboot my phone again just in case, got stuck in booting screen. Then I held Power Button + Vol+ and got myself into EMUI stock recovery mode, I chose wipe cache partition and wipe data/factory reset, after that I rebooted my phone, it was stuck in booting screen for like 2 minutes but then it actually finished booting and now my phone is again functioning and god bless locked & unrooted.

J4 plus (J415GB) bricked

Is there anyone here facing same with my situation? today i bricked my J4 plus, Dunno if its hard bricked or soft brick, I can't enter to download mode and system restore anymore. Im just trying to get oreo back because i fell little laggy on my current os (pie). I went to samsung service center and they told to use JTAG to get it fix but its too expensive for me to pay hundreds buck for this.
Thank you
its not bricked. your battery is full drained. i had the same problem and how i fixed!!! i presed all 3 buttons and put usb cable to my pc and my phone. it goes like bootloop starts and shuts. you will wait with pressed buttons from 5 to 10 mins depend how low is your battery. and finaly will go to download mode and you can flash it then!!!
Bricked my J4+
Can someone help me with a bricked J4+?
I wanted to install TWRP, I followed the guide to the letter on how to install TWRP.
After successfully flashing TWRP 3.2.3-0 and flashing RMM bypass zip (without booting to the OS) I also performed a Wipe Cache in TWRP.
I booted to the Samsung OS and the system overall felt laggy.
I performed a Factory Reset, still the system felt laggy.
I decided to use Odin and install the Samsung factory system (thus go back to Samsung OS).
I booted successfully and decided to give TWRP 3.2.3-0 another chance.
Odin resulted in FAIL when trying to flash with the following error: Can't open the specified file (line: 1892)
I tried different versions of Odin (from last to previous ones), different USB ports, I even tried another PC but no success.
I performed another factory reset and now the phone is hard bricked I guess because it will power on...try to get in stock recovery and Erase...and then power off. I can't get to download mode or stock recovery.
Any help I would highly appreciate it.
Thanks.
FL0R1AN said:
Can someone help me with a bricked J4+?
I wanted to install TWRP, I followed the guide to the letter on how to install TWRP.
After successfully flashing TWRP 3.2.3-0 and flashing RMM bypass zip (without booting to the OS) I also performed a Wipe Cache in TWRP.
I booted to the Samsung OS and the system overall felt laggy.
I performed a Factory Reset, still the system felt laggy.
I decided to use Odin and install the Samsung factory system (thus go back to Samsung OS).
I booted successfully and decided to give TWRP 3.2.3-0 another chance.
Odin resulted in FAIL when trying to flash with the following error: Can't open the specified file (line: 1892)
I tried different versions of Odin (from last to previous ones), different USB ports, I even tried another PC but no success.
I performed another factory reset and now the phone is hard bricked I guess because it will power on...try to get in stock recovery and Erase...and then power off. I can't get to download mode or stock recovery.
Any help I would highly appreciate it.
Thanks.
Click to expand...
Click to collapse
you didnt follow guide from letter to letter. is obviuosly you didnt do all you need to do. if you in pie update you need to flash twrp (you did) then NEED to format data(go to wipe choose format data(not wipe data,cache) write yes and swipe to format data.this step is important.then go to recovery again and flash pie patched boot.img and oreo enforcing.zip,then RMM bypass,and then you can do boot up your device.thanks.
rudi021 said:
you didnt follow guide from letter to letter. is obviuosly you didnt do all you need to do. if you in pie update you need to flash twrp (you did) then NEED to format data(go to wipe choose format data(not wipe data,cache) write yes and swipe to format data.this step is important.then go to recovery again and flash pie patched boot.img and oreo enforcing.zip,then RMM bypass,and then you can do boot up your device.thanks.
Click to expand...
Click to collapse
The part where I had to format the data...I have missed that. Thanks for pointing it out.
I took the phone to a repair shop because it is hard bricked and it needs jtag to unbrick it.
As soon as I have it back I will try again to install TWRP.
Thanks for the help, I appreciate it.
FL0R1AN said:
The part where I had to format the data...I have missed that. Thanks for pointing it out.
I took the phone to a repair shop because it is hard bricked and it needs jtag to unbrick it.
As soon as I have it back I will try again to install TWRP.
Thanks for the help, I appreciate it.
Click to expand...
Click to collapse
no need to thanks.btw if your device is unlocked you cant be bricked.just flash firmware you want and thats it.btw your device must be unlock to do this stuff(twrp,gsi,etc....) btw you can have read my guide for flashing gsi on samsung j4+.https://forum.xda-developers.com/galaxy-j4+/how-to/how-to-flash-gsi-genericsystemimage-to-t3942554.
if you have any question be free to ask.i will help you if i can.
rudi021 said:
no need to thanks.btw if your device is unlocked you cant be bricked.just flash firmware you want and thats it.btw your device must be unlock to do this stuff(twrp,gsi,etc....) btw you can have read my guide for flashing gsi on samsung j4+.https://forum.xda-developers.com/galaxy-j4+/how-to/how-to-flash-gsi-genericsystemimage-to-t3942554.
if you have any question be free to ask.i will help you if i can.
Click to expand...
Click to collapse
This is a phone from work and I did toggle EOM unlock and USB debugging in order to flash TWRP.
I did not enter any password, face unlock, pattern or sign in to google....nothing of the sort. As soon as I opened the phone from the box tried to install TWRP knowing it will erase everything after TWRP installation. I really hate Samsung UI and wanted to try Lineage OS or another custom ROM which is not laggy like ONE UI.
After installing TWRP the phone became very laggy (obviously I did not perform a format data...my bad) I did use Odin and flashed the corresponding firmware of the phone and it did that successfully.
I tried to give TWRP another shot by flashing it again but I was getting a FAIL in Odin with the following error: Can't open the specified file (line: 1892)
After this I tried to flash again the same Samsung firmware but kept getting the same FAIL and the same error: Can't open the specified file (line: 1892)
I have tried all versions of Odin but the same FAIL and same error.
Now I can't even get into Download mode or Samsung recovery mode.
I press Volume Up + Volume Down and insert the micro USB cable....the phone takes at least 10 seconds to power up (Samsung logo) and then I see a blue screen with Android robot trying to perform an Erase and then fails and the phone powers off immediately.
As soon as I get the phone I will check your link on XDA and try a GSI ROM.
Which one do you recommend...this is a work phone, all I care about is speed and fluidity and it has to be a daily driver.
FL0R1AN said:
This is a phone from work and I did toggle EOM unlock and USB debugging in order to flash TWRP.
I did not enter any password, face unlock, pattern or sign in to google....nothing of the sort. As soon as I opened the phone from the box tried to install TWRP knowing it will erase everything after TWRP installation. I really hate Samsung UI and wanted to try Lineage OS or another custom ROM which is not laggy like ONE UI.
After installing TWRP the phone became very laggy (obviously I did not perform a format data...my bad) I did use Odin and flashed the corresponding firmware of the phone and it did that successfully.
I tried to give TWRP another shot by flashing it again but I was getting a FAIL in Odin with the following error: Can't open the specified file (line: 1892)
After this I tried to flash again the same Samsung firmware but kept getting the same FAIL and the same error: Can't open the specified file (line: 1892)
I have tried all versions of Odin but the same FAIL and same error.
Now I can't even get into Download mode or Samsung recovery mode.
I press Volume Up + Volume Down and insert the micro USB cable....the phone takes at least 10 seconds to power up (Samsung logo) and then I see a blue screen with Android robot trying to perform an Erase and then fails and the phone powers off immediately.
As soon as I get the phone I will check your link on XDA and try a GSI ROM.
Which one do you recommend...this is a work phone, all I care about is speed and fluidity and it has to be a daily driver.
Click to expand...
Click to collapse
1. two possible mistake. 1.after you try flash firmware dont check user data,just check AP,BL,CP,CSC and flash firmware.2.no need to try old odin. all new firmware is work on new odin.just need to know what to checked to flash. about gsi all is good but i like Havoc OS, Lineage OS 16, RR,almost all.again you are welcome to ask help if you want.:good:
rudi021 said:
1. two possible mistake. 1.after you try flash firmware dont check user data,just check AP,BL,CP,CSC and flash firmware.2.no need to try old odin. all new firmware is work on new odin.just need to know what to checked to flash. about gsi all is good but i like Havoc OS, Lineage OS 16, RR,almost all.again you are welcome to ask help if you want.:good:
Click to expand...
Click to collapse
Hmmm I did check USER DATA. So that bricked my device. Thanks for letting me know.
FL0R1AN said:
Hmmm I did check USER DATA. So that bricked my device. Thanks for letting me know.
Click to expand...
Click to collapse
yeeeahhh. i am knowing that in hard way. you can check user data only if you have ORIGINAL firmware and not rooted phone(mean twrp),if you have rooted(twrp) then flash with or without user data. some firmwares on web can flash with user data, some cant.anyway as i say you can always ask for help.i will gladly help if i can. good luck.
rudi021 said:
yeeeahhh. i am knowing that in hard way. you can check user data only if you have ORIGINAL firmware and not rooted phone(mean twrp),if you have rooted(twrp) then flash with or without user data. some firmwares on web can flash with user data, some cant.anyway as i say you can always ask for help.i will gladly help if i can. good luck.
Click to expand...
Click to collapse
Thanks. I will wait for the phone to be unbricked and then will try TWRP again.
Can i install gsi rom if the phone is in oneui?
FL0R1AN said:
I press Volume Up + Volume Down and insert the micro USB cable....the phone takes at least 10 seconds to power up (Samsung logo) and then I see a blue screen with Android robot trying to perform an Erase and then fails and the phone powers off immediately .
Click to expand...
Click to collapse
What you're describing are symptoms of a flat battery and a direct boot to recovery.
To boot to download mode plug in the USB cable first then hold vol up, vol down and power until download mode appears.
There is absolutely no way TWRP caused the lag. TWRP runs in its own minimal OS environment and has no effect on a booted android OS whatsoever.
Lastly your device wasn't hard bricked, a device that powers on even if it doesn't boot is only soft bricked.
Usually recoverable using the right procedure.
ashyx said:
What you're describing are symptoms of a flat battery and a direct boot to recovery.
To boot to download mode plug in the USB cable first then hold vol up, vol down and power until download mode appears.
There is absolutely no way TWRP caused the lag. TWRP runs in its own minimal OS environment and has no effect on a booted android OS whatsoever.
Lastly your device wasn't hard bricked, a device that powers on even if it doesn't boot is only soft bricked.
Usually recoverable using the right procedure.
Click to expand...
Click to collapse
I managed to boot into the Revovery and perform a factory reset, now the phone booted normally.
I will try and install TWRP.
When these strange things happened the device had over 80% battery...at least that's what it showed on screen.
Now I see that indeed it was flat 0% and you were right to point out that this is a flat battery problem.
Thanks for the help I really appreciate it.
FL0R1AN said:
I managed to boot into the Revovery and perform a factory reset, now the phone booted normally.
I will try and install TWRP.
When these strange things happened the device had over 80% battery...at least that's what it showed on screen.
Now I see that indeed it was flat 0% and you were right to point out that this is a flat battery problem.
Thanks for the help I really appreciate it.
Click to expand...
Click to collapse
well like i told you it is not problem of twrp.but as senior member ashyx told in answer today device cant be hard bricked.just flash firmware and device will boot as normal. btw keep battery full
rudi021 said:
well like i told you it is not problem of twrp.but as senior member ashyx told in answer today device cant be hard bricked.just flash firmware and device will boot as normal. btw keep battery full
Click to expand...
Click to collapse
Yes Thanks. I am at 100% battery. Can I ask a few questions on how to install TWRP?
I am on Android 9.x.x PIE.
Install TWRP and immediately force reboot to recovery.
Flash the RMM bypass.
Format data
Boot to Samsung OS.
Is this procedure correct?
Thanks.
FL0R1AN said:
Yes Thanks. I am at 100% battery. Can I ask a few questions on how to install TWRP?
I am on Android 9.x.x PIE.
Install TWRP and immediately force reboot to recovery.
Flash the RMM bypass.
Format data
Boot to Samsung OS.
Is this procedure correct?
Thanks.
Click to expand...
Click to collapse
install twrp(in odin option uncheck Auto Reboot) ,format data reboot to recovery,flash oreo enforcing.zip,flash RMM,flash magisk(newest) then reboot.
rudi021 said:
install twrp,format data,flash oreo enforcing.zip,flash RMM,flash magisk(newest) then reboot.
Click to expand...
Click to collapse
Got it, Thanks.
FL0R1AN said:
Yes Thanks. I am at 100% battery. Can I ask a few questions on how to install TWRP?
I am on Android 9.x.x PIE.
Install TWRP and immediately force reboot to recovery.
Flash the RMM bypass.
Format data
Boot to Samsung OS.
Is this procedure correct?
Thanks.
Click to expand...
Click to collapse
It's correct, but if you want access to the data partition in twrp you need to also install the encryption patch.
You will also need to either install magisk or some other patch that disables dmverity.
ashyx said:
It's correct, but if you want access to the data partition in twrp you need to also install the encryption patch.
You will also need to either install magisk or some other patch that disables dmverity.
Click to expand...
Click to collapse
Got it, Thanks

Categories

Resources