Related
Hi,
Last night i was playing with my N4 (with some root applications) and an app asked for a reboot. I just pressed yes so that the phone will reboot (I have done this earlier without any issues). Suddenly the device doesn't boot up. My N4 is stuck at a black screen. While trying to boot up, the Google logo appears and then a black screen. It doesn't advance to the 'X' logo. I'm running on stock, rooted phone (used N4 toolkit by Wugfresh to root).
I'm able to boot into recovery although. I tried all the possible means, wiped cache, dalvik cache, did a factory reset, backed up the system and tried to restore the same. Nothing happened.
Then i tried the "Back to Stock" option in the N4 toolkit and chose the option "Soft-brick/Bootloop" to recover my N4. These are what happened:
Downloaded the 4.2.2 image from Google servers and tried to flash in the device with prior instruction from the toolkit. Everything went fine until the flashing process. In the last step the CMD window opens up saying it is unrooting and flashing stock and immediately it'll bring up a complete message saying the flashing is complete and to wait until the device boots up. But nothing happens again.
I tried the automatic flashing and on the downloading window it saying download failed and hash checks failed meaning its not downloading.
I searched all the possible threads in a day to find a similar problem but in vain. I'm not a noob but i'm too lazy . But i would do anything to bring my N4 back to life. Anyone please show me a direction.
In short:
Status: Soft-Bricked (guess so), black screen after Google logo
Version: Stock 4.2.2 (rooted+busybox+supersu+twrp)
Able to boot to recovering: Yes, bootable to recovery and bootloader.
Tried Nexus toolkit recovery: Yes but in vain.
Gave up: No and never, I'm searching and searching for answers and I'm worried if I'll end up in a hard brick. :crying:
Guys, please help.
Thank You!
Aghil
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
ameinild said:
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
Click to expand...
Click to collapse
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
aghilvr said:
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Click to expand...
Click to collapse
No, my suggestion would require that the ROM is still on the phone, so you should restore your ROM prior to my suggestion. And I'm by no means an expert (therefore the disclaimer), but I *think* that since it's a bootup problem, it could be solved by flashing a new boot.img (which is essentially flashing a new kernel to the system).
But yeah, let's see if others think this might help, haven't researched it, is at work right now. Just throwing in a suggestion, that's all...
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
I *think* (again, I'm totally not sure about this, as I haven't tried it) that you can sideload a ROM via zip file from recovery, but since I haven't tried it I'm not sure - can anybody confirm???
EDIT: Chromium's suggestion is better, by pushing the ROM.zip to the device and flashing from recovery (check md5 first, just in case).
aghilvr said:
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
Yes there is. Your nexus is not bricked and this is why you shouldnt use toolkits to do things. This is honestly an extremely easy and simple fix. Use adb to push a rom onto the n4.
Code:
adb push \path\to\rom.zip /sdcard
Boot into recovery, do a full wipe, and flash the rom.
You said you downloaded the Google images.
Just boot your phone into the bootloader and run the flashall.bat that is in the Google image folder.
Note this will probably fully wipe you're phone in the process
Sent from my Nexus 4 using xda app-developers app
try this it may help u this toolkit is damn easy to use :
http://forum.xda-developers.com/showthread.php?t=1995688
Okay, thanks guys. I'm on it. Will let you know when I'm done.
That same thing happened to me once. I had to extract the google file and look for the 4 img files(bootloader, system, userdata, recovery) and flash them with toolkit manually and it fixed it, but it erased everything on my sd
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
aghilvr said:
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
Click to expand...
Click to collapse
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
chromium96 said:
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
Click to expand...
Click to collapse
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
aghilvr said:
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
chromium96 said:
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
Click to expand...
Click to collapse
Oh that's why it didn't work all the time
Thanks chromium :fingers-crossed:
Hey thanks guys, my device is back to normal. Chromium a special thanks for you for helping me out. See you guys with my next problem/queris!
If you haven't seen yet, from 9/6-9/7 causes bricks on some devices.
I can still get into TWRP recovery, but it's not recognizing my device in ADB, and the kernel is probably corrupted too.
How can I push a new kernel to my device and install an older rom?
When attempting to manually install the drivers, I get "The hash for the file is not present in the specified catalog file."
ThomasBags said:
If you haven't seen yet, from 9/6-9/7 causes bricks on some devices.
I can still get into TWRP recovery, but it's not recognizing my device in ADB, and the kernel is probably corrupted too.
How can I push a new kernel to my device and install an older rom?
When attempting to manually install the drivers, I get "The hash for the file is not present in the specified catalog file."
Click to expand...
Click to collapse
Try to get into recovery and do a adb sideload install in TWRP, here is the how to http://www.google.nl/url?sa=t&rct=j...=Vp_GX8CUK5C4PSCnBss8Yw&bvm=bv.51773540,d.Yms If that doesn`t work reflash the factory image in fastboot.bootloader mode.
I have the same issue... TWRP adb sideload is not working for me. Is there any way I can fastboot flash an older version of CM (i.e. 9/05)?
kino1122 said:
I have the same issue... TWRP adb sideload is not working for me. Is there any way I can fastboot flash an older version of CM (i.e. 9/05)?
Click to expand...
Click to collapse
You guys need to flash a factory image from here https://developers.google.com/android/nexus/images in fastboot.
kino1122 said:
I have the same issue... TWRP adb sideload is not working for me. Is there any way I can fastboot flash an older version of CM (i.e. 9/05)?
Click to expand...
Click to collapse
CM 9/05 isn't in a fastboot image format. Its a flashable zip so no.
Your best case is to do a ADB sideload as what gee2012 said. Always have a trusted backup or older flashable zip to work off of.
As a last resort, flash factory image but you'll have to start all over
Hey guys I found a solution.
For those unable to get ADB sideload to work, be sure to install the drivers here: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Following that you can do the TWRP sideload thing and then it'll just tell you it's starting it up. Go into your adb command and under adb devices you will see your device in sideload mode. With that, it's just a simple command of adb sideload ROM.zip and it'll install the .zip for you and you are good to go!
That happened to me too, you can try to use adb pull and install the 9/5 cm update that is not corrupted.
Guys there is a way to alert other people to not install those updates? Always is a pain in the ass to get your phone bricked
by the way, sorry for my bad english.
one day people will learn the difference between what a brick and a soft brick is. if you can get into the bootloader, the device is not bricked, it can be fixed. even if you can't get into the bootloader, sometimes it can be fixed. doing a little research/reading before rooting your device can save you lots of hassle later on, like in this situation. even just making a backup of your current set up in your recovery before flashing anything can save you hours of stress afterwards.
simms22 said:
one day people will learn the difference between what a brick and a soft brick is. if you can get into the bootloader, the device is not bricked, it can be fixed. even if you can't get into the bootloader, sometimes it can be fixed. doing a little research/reading before rooting your device can save you lots of hassle later on, like in this situation. even just making a backup of your current set up in your recovery before flashing anything can save you hours of stress afterwards.
Click to expand...
Click to collapse
I just a matter of name bro, but, anyways, you know what have gove wrong with these nightlies?
lwkkazz said:
I just a matter of name bro, but, anyways, you know what have gove wrong with these nightlies?
Click to expand...
Click to collapse
nightlies by definition are not stable, nor are meant to be. tbey are just tbe most recent upload with whatever code was added. new code will not play nice many times, especially with other stuff included. that why they build the nightlies, to test out how the newest code will behave. whats wrong with this nightly i dont know, i don't run cm. normally, after a bad nightly, flashing tge ladt nightly tgat was good would fix the non booting problem, or restoring a nandroid backup. anyways, its a good idea to keep the last good rom(or kernel) in your storage at all times, just in case of situation like this.
simms22 said:
nightlies by definition are not stable, nor are meant to be. tbey are just tbe most recent upload with whatever code was added. new code will not play nice many times, especially with other stuff included. that why they build the nightlies, to test out how the newest code will behave. whats wrong with this nightly i dont know, i don't run cm. normally, after a bad nightly, flashing tge ladt nightly tgat was good would fix the non booting problem, or restoring a nandroid backup. anyways, its a good idea to keep the last good rom(or kernel) in your storage at all times, just in case of situation like this.
Click to expand...
Click to collapse
I do that too, you know if that a way to sinalize that the last two nightlies are not bootable?
lwkkazz said:
I do that too, you know if that a way to sinalize that the last two nightlies are not bootable?
Click to expand...
Click to collapse
if they arent bootable, then whomever compiles them already probably knows. the thing to do will be to flash the last good nightly and wait for the next nightly.
kino1122 said:
Hey guys I found a solution.
For those unable to get ADB sideload to work, be sure to install the drivers here: plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Following that you can do the TWRP sideload thing and then it'll just tell you it's starting it up. Go into your adb command and under adb devices you will see your device in sideload mode. With that, it's just a simple command of adb sideload ROM.zip and it'll install the .zip for you and you are good to go!
Click to expand...
Click to collapse
Thank you!
It worked!
An update for whoever is looking for an update: I have tried 20130918 build and it's working fine.
Well this is embarrassing to say what I actually did to my phone but I desperately need help to fix it (if it is possible).
My device is D802.
I wanted to try some custom rom so I installed TWRP 2.6.3.2.
I have downloaded a rom and gapps and then I saw that it is desirable to wipe everything, and I mistakenly wiped even data on internal storage which left me without rom to flash.
I can enter recovery and download mode, but it can't seem to start that offline flash tutorial I found on this forum.
I am on Windows 8.1 and tried to install drivers. I did not get any errors during that but adb do not see my phone. when in recovery. PLEASE I am desperate, someone help me! (maybe I just said the stupid thing but I am not that good in all of this).
ozren said:
Well this is embarrassing to say what I actually did to my phone but I desperately need help to fix it (if it is possible).
My device is D802.
I wanted to try some custom rom so I installed TWRP 2.6.3.2.
I have downloaded a rom and gapps and then I saw that it is desirable to wipe everything, and I mistakenly wiped even data on internal storage which left me without rom to flash.
I can enter recovery and download mode, but it can't seem to start that offline flash tutorial I found on this forum.
I am on Windows 8.1 and tried to install drivers. I did not get any errors during that but adb do not see my phone. when in recovery. PLEASE I am desperate, someone help me! (maybe I just said the stupid thing but I am not that good in all of this).
Click to expand...
Click to collapse
Anyone? At least point me in right direction?
I've never did this but heard its happened many times before ... Adb or sideload/push the rom into your internal sdcard to flash it and all should be good!!! Just google how to a d should bring up a you need
Sent from my LG-VS980 using XDA Premium 4 mobile app
Thank you My problem was that adb did not "see" the phone. I had to manually install the driver. Once I got that working I managed to install a custom 4.2.2 RM. Do you have any idea why I coud not install 4.4 rom (I get error no matter what version I choose).
But seriously thank you very much for the efort of replaying and pointing me to the right direction.
You need a newer version of your recovery to install kitkat roms
Sent from my LG-D800 using Tapatalk
All done thank you
Sent from my LG-D802 using Tapatalk
I have a Note 3 N9005.
I installed the latest TWRP recovery.
No matter which rom I try to flash to the system, the same thing happens.
I see that the Aroma installer is strarting and than it just resets for no reason, no install made.
The only sulotion I have found so far is to install a 5.0 stock rom via Odin.
I want to install a custom rom 6.0.1.
Does anyone know what the hell?
Sae problem but a lil worse!!
vashthestampede! said:
I have a Note 3 N9005.
I installed the latest TWRP recovery.
No matter which rom I try to flash to the system, the same thing happens.
I see that the Aroma installer is strarting and than it just resets for no reason, no install made.
The only sulotion I have found so far is to install a 5.0 stock rom via Odin.
I want to install a custom rom 6.0.1.
Does anyone know what the hell?
Click to expand...
Click to collapse
I tried to do the same but ended up bricking my phone. So then I try to unbrick/unroot my phone by flashing the stock rom but I can't do that either cause now it says "Volume Size is too big 4620288<4718599. Need help!!!! ASAP!
Hey guys, I had the same problem at first and it freaked me out too.
Try installing the older 2.8.7.0 version for TWRP through the app, instead of the latest or any other after v3 for that matter. Apparently I've read from other forums that it's due to lack of Aroma Installer Support.
Hope this helps
Confirm the phone's model # by booting into download mode befor flashing TWRP or a stock ROM from sammobile.com.
Will try
I flashed the stock rom packege with odin.
saved my phone after brick.
so you are saying that by downgrading the TWRP recovery i can use aroma insatller based roms again?
cause i also tried to install reserection remix rom (I think this has no aroma in it), i got a massage that said that i cannot install it as well.
refuses to let me change into anything but stock rom.
rooting did not help at all.
vashthestampede! said:
so you are saying that by downgrading the TWRP recovery i can use aroma insatller based roms again?
cause i also tried to install reserection remix rom (I think this has no aroma in it), i got a massage that said that i cannot install it as well.
refuses to let me change into anything but stock rom.
rooting did not help at all.
Click to expand...
Click to collapse
To be honest I don't really know about Cyanogen Mod, however this was just my personal experience with Aroma Installer. I've tried DarkWolf_FW and Aryamod ROMs which are both S7 Edge Port ROMs, and they both use Aroma Installer.
- Also! Take the opportunity to make a Nandroid backup just in case the installation goes bad, then you can restore to where you are right now. Honestly downgrading just worked for me so please don't make me liable if anything goes to pot, at least you will have a full device backup to the exact point in your system which I have found extremely useful when trying different ROMs and Kernels.
tnks
don't worry man
1. I always backup the whole phone before ANY change.
2. your suggestion sound interesting, cause i tried the same rom's you did but no install was made.
3. i'll maybe try a different recovery... maybe CWM.
vashthestampede! said:
don't worry man
1. I always backup the whole phone before ANY change.
2. your suggestion sound interesting, cause i tried the same rom's you did but no install was made.
3. i'll maybe try a different recovery... maybe CWM.
Click to expand...
Click to collapse
Hey, just randomly thinking, did you reset all your System, Data and Cache and Dalvik Cache files before you tried to install the ROMs? Sorry, this might not make a difference, but I don't think I have any more advice to give (I'm kinda new to this too ).
Hope CWM recovery goes well, let me know how it goes
vashthestampede! said:
don't worry man
1. I always backup the whole phone before ANY change.
2. your suggestion sound interesting, cause i tried the same rom's you did but no install was made.
3. i'll maybe try a different recovery... maybe CWM.
Click to expand...
Click to collapse
Doing a complete backup before anything is always the safest bet.
From my experience, TWRP 3+ is fine for CM and AOSP based ROMs.
TWRP 2.8.7-0 is the one you should use to flash ROMs using AROMA Installer.
If you read the OP (opening post) on any ROM forum, it will usually include installation instructions and generally states which TWRP version should be used.
Good Luck.
theawesomecw said:
To be honest I don't really know about Cyanogen Mod, however this was just my personal experience with Aroma Installer. I've tried DarkWolf_FW and Aryamod ROMs which are both S7 Edge Port ROMs, and they both use Aroma Installer.
- Also! Take the opportunity to make a Nandroid backup just in case the installation goes bad, then you can restore to where you are right now. Honestly downgrading just worked for me so please don't make me liable if anything goes to pot, at least you will have a full device backup to the exact point in your system which I have found extremely useful when trying different ROMs and Kernels.
Click to expand...
Click to collapse
Well I'm now stuck in a boot loop. I cannot turn my phone on at all. how do I install a lower version of TWRP on my phone and how do I unbrick it?
kurosaki999 said:
Well I'm now stuck in a boot loop. I cannot turn my phone on at all. how do I install a lower version of TWRP on my phone and how do I unbrick it?
Click to expand...
Click to collapse
You just need download mode to flash it.
Sent from my SM-G925F
kurosaki999 said:
Well I'm now stuck in a boot loop. I cannot turn my phone on at all. how do I install a lower version of TWRP on my phone and how do I unbrick it?
Click to expand...
Click to collapse
I presume when you say it doesn't turn on you mean it doesn't boot into the Android environment. Have you tried unplugging the battery and pressing the Volume Up + Home + Power Button? Yes... I was surprised you don't have to be an octopus too..
Then restore the Nandroid backup from before.
You can also flash TWRP through Odin without root, have a look at the TWRP website for more info.
re
kurosaki999 said:
Well I'm now stuck in a boot loop. I cannot turn my phone on at all. how do I install a lower version of TWRP on my phone and how do I unbrick it?
Click to expand...
Click to collapse
all you need is to flush new stock rom via Odin.
Search the web (like I did) to find a stock rom with 4 .tar files in it.
There should be instructions on how to install but usually all needs to be done is this:
1. load odin 3.*
2. enter the phone in download mode.
3. After you see the line 'add' in odin, load the .tar files to the correct place each (not hard they are tagged by same name)
4. Flush and pray.
5. After a successful install the phone will reboot, this will take a while so don't get streesed.
after about 10-15 min the phone will load again.
Root one more time via odin and try to install again.
vashthestampede! said:
all you need is to flush new stock rom via Odin.
Search the web (like I did) to find a stock rom with 4 .tar files in it.
Click to expand...
Click to collapse
Try Sammobile as they have a large database of firmwares for your phone and the country variants.
Hello, I was trying to root my phone last night, I unlocked the boot loader that worked perfectly, easy. Nothing else went well, I was fighting with it TWRP for hours and then Magisk wouldn't install. I gave up on that and tried SuperSu... now the phone just stays on the loading screen instead of booting, It won't boot into recovery either just fastboot. Can it be fixed?
Your phone is soft bricked and can only boot to bootloader, correct?
The only solution is flashing the stock ROM of the device. You can get your device (Tissot) stock ROM from here.
I just got it to boot into TWRP, after it cycled a few times.
Well that may make it easier, you can try wiping dalvik cache then wiping data and see if that works. Needless to say wiping data is going to delete all your personal data, but since you're in TWRP recovery you can back it up.
Wiping it didn't work, I'm trying to use MiFlash I have downloaded "Tissot_9.0_V10.0.10.0.PDHMIXM_Fastboot" my phone is in fastboot. MiFlash detects it but when I try to flash I just get "can not found file flash_all_lock.bat"
How do you tell is MiFlash has successfully installed drivers, it gives me a window in Chinese?
If it's not working - I never thought it would anyway - then your only option is to flash stock ROM.
You can try using fastboot commands through cmd window, if it returns <waiting for device> or something similar then the driver isn't installed properly. Alternatively you can install the driver from here.
Thanks, it detects my phone. How would you recommend flashing the stock ROM? Do I need to use the same version the phone was running before?
galaxymini1 said:
Thanks, it detects my phone. How would you recommend flashing the stock ROM? Do I need to use the same version the phone was running before?
Click to expand...
Click to collapse
You can use any version as long as it is meant for your device. Flashing the latest version might be best option.
Happy to help.
I tried flashing it with TWRP but just got "no digest file found" I'll try again tomorrow.
This must be the most annoying thing I've done with electronics in years, nothing wants to work.
galaxymini1 said:
I tried flashing it with TWRP but just got "no digest file found" I'll try again tomorrow.
This must be the most annoying thing I've done with electronics in years, nothing wants to work.
Click to expand...
Click to collapse
Lemme guess, you have TWRP v3.2.2-0? Try flashing the latest version from here.
XDHx86 said:
Lemme guess, you have TWRP v3.2.2-0? Try flashing the latest version from here.
Click to expand...
Click to collapse
v3.2.1 anyway it's gone now, I got it booting with the guide on https://xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1/
probably the best written one I've found.
Now to try and root it again...
galaxymini1 said:
v3.2.1 anyway it's gone now, I got it booting with the guide on https://xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1/
probably the best written one I've found.
Now to try and root it again...
Click to expand...
Click to collapse
You can find that in an XDA revised article here.
I got TWRP and Magisk installed no problem. I don't know if I was just tired or it was the crap guides but nothing wanted to cooperate on my first attempt.
Thanks for all the help.