Related
Hello,
Earlier today I installed BAKED ROM on my AT&T HTC ONE XL that was at the time running CM 10.1 After having some issues with wifi not working I decided to restore from my backup made in CWR when installing CM 10.1 on my phone. After the restore finished i was stuck in a bootloop. So i went back into CWR to re install the BAKED ROM. Once i cleared drive i came to realize that i somehow deleted the .zip files for the ROM on my phone and no longer had a ROM to install. After that i decided that I would mount my phone from CWR so i can transfer the .zip to my phone and then install. After realizing i need to use TWRP to be able to mount and transfer files i was going to flash over TWRP in fastboot. My issue currently is that my phone is powered off after telling it to shutdown in bootloader, and i can not get it to turn back on or to boot into bootloader so that i can flash TWRP. Hopefully i am missing something small here. Any advise is appreciated.
Thank You
coltp10 said:
Hello,
Earlier today I installed BAKED ROM on my AT&T HTC ONE XL that was at the time running CM 10.1 After having some issues with wifi not working I decided to restore from my backup made in CWR when installing CM 10.1 on my phone. After the restore finished i was stuck in a bootloop. So i went back into CWR to re install the BAKED ROM. Once i cleared drive i came to realize that i somehow deleted the .zip files for the ROM on my phone and no longer had a ROM to install. After that i decided that I would mount my phone from CWR so i can transfer the .zip to my phone and then install. After realizing i need to use TWRP to be able to mount and transfer files i was going to flash over TWRP in fastboot. My issue currently is that my phone is powered off after telling it to shutdown in bootloader, and i can not get it to turn back on or to boot into bootloader so that i can flash TWRP. Hopefully i am missing something small here. Any advise is appreciated.
Thank You
Click to expand...
Click to collapse
hold the power button down for about 15 seconds. wait for 5 seconds, then press the power button and volume down at the same time after a few seconds you should get the bootloader screen.
does the led come on when you're charging it?
cr1960 said:
hold the power button down for about 15 seconds. wait for 5 seconds, then press the power button and volume down at the same time after a few seconds you should get the bootloader screen.
does the led come on when you're charging it?
Click to expand...
Click to collapse
Thank you for your response. From following your instructions i was still not able to get into bootloader, and when i plug it in to charge the LED does not come on
coltp10 said:
Thank you for your response. From following your instructions i was still not able to get into bootloader, and when i plug it in to charge the LED does not come on
Click to expand...
Click to collapse
Sadly based on my knowledge and experience(I learned this the hard way by taking the ATT OTA) if the led doesn't come on while charging and you cant access your bootloader your phone is sadly dead. However you can double check to see if its your cord and if it is not then call HTC if device is still under warranty. They replaced the internals of mine and recieved it back at no charge.
If I have helped in any way hit the Thanks button please.
Why did you "need" to go to TWRP to mount SD? Clockworkmod has had SD mount fixed for some time now, hasn't it?
Leave the phone on wall charger (not connected to computer) overnight or 8 Hrs or so, and see if you get any LED's or can get into bootloader. If you were only messing with ROMs and recovery, I don't see how you can be bricked (as long as anything you were trying to flash was for the EVITA). The battery may just have run down while you were messing with the device.
redpoint73 said:
Why did you "need" to go to TWRP to mount SD? Clockworkmod has had SD mount fixed for some time now, hasn't it?
Leave the phone on wall charger (not connected to computer) overnight or 8 Hrs or so, and see if you get any LED's or can get into bootloader. If you were only messing with ROMs and recovery, I don't see how you can be bricked (as long as anything you were trying to flash was for the EVITA). The battery may just have run down while you were messing with the device.
Click to expand...
Click to collapse
Well when i went into clockworkmod and told it to mount SD it did not work, i have all of my drivers installed properly so it couldn't be a driver issue. So i figured that i would just flash over TWRP and use mount to usb as a second shot. I will have to try and leave it plugged in later after work. Yes the ROM that i installed was for the EVITA, it was running fine except the wifi wouldnt turn on.
coltp10 said:
Well when i went into clockworkmod and told it to mount SD it did not work, i have all of my drivers installed properly so it couldn't be a driver issue.
Click to expand...
Click to collapse
If/when you get back up and running, if still on CWM, make sure its up to date. I think the SD mount was fixed quite some time ago.
redpoint73 said:
If/when you get back up and running, if still on CWM, make sure its up to date. I think the SD mount was fixed quite some time ago.
Click to expand...
Click to collapse
Okay thanks for the input i will check it out as soon as I am able
When i came home from work and plugged it in the red LED light came on. After letting it charge for about 5 hours i tried to access the bootloader by pressing power down for 15 seconds, then waiting 5, and then power and volume down, to no result. Only when holding down power for the first 15 seconds the soft on screen keys did flash
coltp10 said:
When i came home from work and plugged it in the red LED light came on. After letting it charge for about 5 hours i tried to access the bootloader by pressing power down for 15 seconds, then waiting 5, and then power and volume down, to no result. Only when holding down power for the first 15 seconds the soft on screen keys did flash
Click to expand...
Click to collapse
After holding the power button down and let the capacitive keys flash 6 times. The 6 flashes means a hard reset and it's about to start rebooting. Let go of the power button and immediately hold volume down. It should take you into the bootloader. Then you can fastboot flash TWRP.
Sent from my HTC One X using Tapatalk 2
Thank you
Finally after letting it charge all night, i was able to access my bootloader, i flashed over TWRP and am in the process of mounting my sd to transfer the rom and hopefully install. Thank you all for you help!!
coltp10 said:
Finally after letting it charge all night, i was able to access my bootloader, i flashed over TWRP and am in the process of mounting my sd to transfer the rom and hopefully install. Thank you all for you help!!
Click to expand...
Click to collapse
Good luck
Sent from my HTC One X using xda premium
Well i was able to install cm 10.1 back to my phone and successfully load it, my only issue now as before when i installed the BAKED rom, is my wifi doesn't seem to work or recognize any networks
coltp10 said:
Well i was able to install cm 10.1 back to my phone and successfully load it, my only issue now as before when i installed the BAKED rom, is my wifi doesn't seem to work or recognize any networks
Click to expand...
Click to collapse
Glad you got it working.
What hboot are you on? If you are on one of the newer ones, not 1.09, and don't have s-off you have to manually flash the boot.img through fastboot after installing the ROM. That sounds like it might be your issue.
pside15 said:
Glad you got it working.
What hboot are you on? If you are on one of the newer ones, not 1.09, and don't have s-off you have to manually flash the boot.img through fastboot after installing the ROM. That sounds like it might be your issue.
Click to expand...
Click to collapse
Agreed, i did forget to flash to boot image during my excitement to a working phone again, even so, if i hadn't flashed the boot image why is it that my phone was actually able to start up the rom and go through phone system setup?
coltp10 said:
Agreed, i did forget to flash to boot image during my excitement to a working phone again, even so, if i hadn't flashed the boot image why is it that my phone was actually able to start up the rom and go through phone system setup?
Click to expand...
Click to collapse
because the rom you flashed is based on CM so it was compatible enough to boot but not have everything working as it should. if you don't flash the boot.img, the previously used kernel would still be used.
The ROM was running and i was able to use my phone. Then i flashed over the boot.img for my rom and now it doesnt boot up it is stuck at the Cyanogen Mod loading screen
coltp10 said:
The ROM was running and i was able to use my phone. Then i flashed over the boot.img for my rom and now it doesnt boot up it is stuck at the Cyanogen Mod loading screen
Click to expand...
Click to collapse
boot to recovery, wipe everything (cache, dalvik, system, factory reset), reflash the rom you want to use, then reboot to bootloader and fastboot flash boot boot.img extracted from the rom you just flashed.
Not sure where you went wrong but that will get you booting. To avoid having to fastboot flash boot boot.img everytime, you can S-OFF.
exad said:
boot to recovery, wipe everything (cache, dalvik, system, factory reset), reflash the rom you want to use, then reboot to bootloader and fastboot flash boot boot.img extracted from the rom you just flashed.
Not sure where you went wrong but that will get you booting. To avoid having to fastboot flash boot boot.img everytime, you can S-OFF.
Click to expand...
Click to collapse
I will have to look into the S-OFF. As of right now i wiped everything, installed rom, installed gaps, went to bootloader flashed boot.img and now just waiting to see if it will start up
coltp10 said:
I will have to look into the S-OFF. As of right now i wiped everything, installed rom, installed gaps, went to bootloader flashed boot.img and now just waiting to see if it will start up
Click to expand...
Click to collapse
You can also use the flash image GUI app to flash a boot image in Android right before you boot to recovery to flash the ROM. But I would definitely look into s-off. It's a very easy process and then you don't ever have to worry about the boot.img at all.
Hello,
Yesterday there was an update for the Moto G, I confirmed to do the update. Since then the phone is in a reboot loop. I mean it doesn't matter what ever I do,the phone restart itself in every 2-3 minutes. The phone is rooted.
I've tried to do a factory reset from the setting,however nothing happens when I want to erase the settings. In the bootloader if I chose Recovery or Factory reset,the phone reboots.
I've got a tip that I should remove the update file from the /chace directory,however I don't know how to do so,as the phone keeps reboot itself.
The only place,where the phone is not restarts is in the bootloader.
Is there any way to somehow solve this problem without flash a stock rom ?
Thanks for your help!
Regards,
Péter
The same here. Help!
Tussky said:
Hello,
I've tried to do a factory reset from the setting,however nothing happens when I want to erase the settings. In the bootloader if I chose Recovery or Factory reset,the phone reboots.
Click to expand...
Click to collapse
You have to press volume up instead of power to choose something in fastboot menu.
Unroot and if used custom recovery go back to stock recovery.
mokkami said:
Unroot and stock recovery.
Click to expand...
Click to collapse
How should I do the unroot ? I find this solution,but I can't post the link,as I didn't have 10+ posts... its in the site unlockr and there's an article about moto g unroot.
However I can't enable the usb debug,as the phone restart faster,than I'am able to do this.
Yes I know I have to press volume up,however if I chose recovery it's reboot itself,so I'am not able to select Recovery from the bootloader.
Tussky said:
How should I do the unroot ? I find this solution,but I can't post the link,as I didn't have 10+ posts... its in the site unlockr and there's an article about moto g unroot.
However I can't enable the usb debug,as the phone restart faster,than I'am able to do this.
Click to expand...
Click to collapse
My is rooted and cwm 6.0.4.6
May be we must do something with fastboot command
my GF's Moto G did the same thing, luckily it was a simple fix.
I had already rooted her stock 4.4.2 and installed CWM Recovery 6.0.4.6.
If you havent installed, CWM or TWRP, then I recommend to do so by fastboot command and the recovery.img.
Here is the forum link to install CWM Recovery for your Moto G:
http://forum.xda-developers.com/showthread.php?t=2563599
So I just Powered Off the phone. Then go back into the CWM Recovery by:
- hold down Volume Down and hold down Power Button for about 4-5 secs
- then let them go and you will see the Fastboot menu
- Press Volume Down (to highlight Recovery)
- then Press Volume Up (to select and go into Recovery, in this case the custom recovery)
- then just Wipe Cache and Wipe Dalvik Cache
- then Reboot Phone.
Done.
I think I will install CM11 for her and not have to deal with the stock ROM that gets official updates pushed onto it causing issues like this.
eyeoncomputers said:
my GF's Moto G did the same thing, luckily it was a simple fix.
I had already rooted her stock 4.4.2 and installed CWM Recovery 6.0.4.6.
So I just Powered Off the phone. Then go back into the CWM Recovery by:
- hold down Volume Down and hold down Power Button for about 4-5 secs
- then let them go and you will see the Recovery menu
- Press Volume Down (to highlight Recovery)
- then Press Volume Up (to select and go into Recovery, in this case the custom recovery)
- then just Wipe Cache and Wipe Dalvik Cache
- then Reboot Phone.
Done.
Click to expand...
Click to collapse
I see,however It's not possible on the phone. If I select the Recovery and I press volume up -> phone reboots
You mean this.
Download Stock image, extract.
Go to fastboot mode and flash following.
If you used Superboot method then use:
fastboot flash motoboot motoboot.img
Click to expand...
Click to collapse
if you used the modified recovery method:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Tussky said:
I see,however It's not possible on the phone. If I select the Recovery and I press volume up -> phone reboots
Click to expand...
Click to collapse
Thats strange.
eyeoncomputers said:
my GF's Moto G did the same thing, luckily it was a simple fix.
I had already rooted her stock 4.4.2 and installed CWM Recovery 6.0.4.6.
If you havent installed, CWM or TWRP, then I recommend to do so by fastboot command and the recovery.img.
The general command to install a custom recovery in Fastboot is:
fastboot flash recovery your_recovery_image.img
So I just Powered Off the phone. Then go back into the CWM Recovery by:
- hold down Volume Down and hold down Power Button for about 4-5 secs
- then let them go and you will see the Fastboot menu
- Press Volume Down (to highlight Recovery)
- then Press Volume Up (to select and go into Recovery, in this case the custom recovery)
- then just Wipe Cache and Wipe Dalvik Cache
- then Reboot Phone.
Done.
I think I will install CM11 for her and not have to deal with the stock ROM that gets official updates pushed onto it causing issues like this.
Click to expand...
Click to collapse
Thanks MAN! It works perfect!
mokkami said:
You mean this[/URL].
Download Stock image, extract.
Go to fastboot mode and flash following.
If you used Superboot method then use:
if you used the modified recovery method:
Thats strange.
Click to expand...
Click to collapse
Yes, I mean that,so if I follow this guide,then it will help ? I used the followin from modaco site -> Root your Moto G - option 1: Superboot
@kokonai OH? I thought unroot is essential?
I guess u used the modified recovery to root?
Tussky said:
Yes, I mean that,so if I follow this guide,then it will help ? I used the followin from modaco site -> Root your Moto G - option 1: Superboot
Click to expand...
Click to collapse
At the moment i am confused. But yeah i'm assuming it will work.
Cause if i understand it right, the superboot method is a modified kernel.
So you should flash motoboot.img.
There are several ways now. Either you flash cwm and wipe /cache as described above.
Or you flash motoboot and then , in my opinion, it should work.
mokkami said:
@kokonai OH? I thought unroot is essential?
I guess u used the modified recovery to root?
At the moment i am confused. But yeah i'm assuming it will work.
Cause if i understand it right, the superboot method is a modified kernel.
So you should flash motoboot.img.
There are several ways now. Either you flash cwm and wipe /cache as described above.
Or you flash motoboot and then , in my opinion, it should work.
Click to expand...
Click to collapse
I used the method to root the phone what is on that site,I followed that description and it worked. I'am not an expert in it,so I just followed PaulOBrien guide,so I can't answer for it for sure.
At this point I'am really desperate as the phone is completely useless, so I don't care even if I had data loss,as I can't access it anymore,nor save it to my PC.
In my knowledge, which seems not to be true anymore, the phone needs to be stock to install any update.
I am not talking about installed apps. It is more about system partition, recovery, kernel and so on.
I would try now to flash the motoboot.img and see what happens.
If this does not work i would flash cmw and try what was mentioned above.
Sure you can go completly stock. But in my view you are not that lost.
I'll stay with you
......but max 5 hours =)
mokkami said:
In my knowledge, which seems not to be true anymore, the phone needs to be stock to install any update.
I am not talking about installed apps. It is more about system partition, recovery, kernel and so on.
I would try now to flash the motoboot.img and see what happens.
If this does not work i would flash cmw and try what was mentioned above.
Sure you can go completly stock. But in my view you are not that lost.
I'll stay with you
......but max 5 hours =)
Click to expand...
Click to collapse
Thanks! However I can try it out only after 20 UTC.
However I have an idea,but maybe I'am wrong.
What happens if I try the chace wipe via in command line, I mean:
mfastboot erase cache
This should delete the cache right ? Shouldn't this command remove the problematic update file ?
Oh yeah this should be also an option.
But you'll come again to that point where you wanna install the update?!
mokkami said:
Oh yeah this should be also an option.
But you'll come again to that point where you wanna install the update?!
Click to expand...
Click to collapse
I want to give it a try. Yes,however I don't have to install the update. But I think I will flash a stock rom,make the update and then re-root the phone.
Thank you guys, I was going crazy with this rebooting problem. So now it is fixed, but how can I get the update? Noway?
mokkami said:
Oh yeah this should be also an option.
But you'll come again to that point where you wanna install the update?!
Click to expand...
Click to collapse
I was able to enable the usb debugging,and then to start the bootloader. However If I connected the phone and tried to execute the adb reboot-bootloader command it didn't worked. So I restarted the phone and entered into the bootloader,then I've done the following:
fastboot reboot-bootloader
fastboot erase cache
After the first command,the phone rebooted into bootloader,then the second command finally cleared the chace. Now my uptime is more then 8 minutes,so the phone is working great now
However I will do the complete process on the weekend,but not now as I'am really tired,but I will flash a stock rom at the weekend.
Possible solution...
Just started a thread with a possible solution
http://forum.xda-developers.com/showthread.php?t=2663205
Hope it helps...
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:
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
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.