First off, I have a Chinese model of the Galaxy Note II SCH-N719. I was given this phone for free by a friend.
The phone is now bricked. I was trying to install a custom recovery. After going into the stock Android recovery, I flashed the CWM zip and it bricked the phone.
What doesn't work
- When I load up the phone it will only load up the splash screen and stay stuck there, it will not go any further no matter how long I wait.
- If I attempt to load the phone into recovery mode (Volume Up + Home + Power) it will show a blank screen. I cannot interface with the device via adb or by any other means.
If I boot the phone into download mode (Volume Down + Home + Power) it will show a blank screen/no activity. However, in this mode I can interface with the device using fastboot so I can issue commands to the phone.
What I've tried so far
So because the phone is apparently bricked, I have
-Attempted to flash a custom recovery via fastboot, no difference
-Attempted to flash the stock recovery, no difference
-Attempted to boot directly into the stock recovering using fastboot boot boot.img but it just produced a blank screen
I downloaded the stock ROM for this phone, which is 4.3 (N719KEUCML2). After unziping the contents of this archive, I was successfully able to use the fastboot flash all command to flash the recovery, system etc partitions to the phone.
However, it produced no change in the phone. I have used fastboot to wipe the partitions and individually flash the partitions using the .img files but with no result.
The only thing I was unable to get working was using fastboot update. The stock (factory) ROM for this phone does not seem to satisfy as an Update.zip. I receive the typical "system.img" not being found and it cannot update from the .zip (which is a shame). My worry is that the bootloader partition has been corrupted, however there is no bootloader.img provided in the stock rom!
Do anyone have any experience with this? Would be grateful for your help! If I should put this in a more suitable section please let me know.
Any thoughts on this? Phone is still unresponsive..
Related
Two weeks ago:
I rooted my phone using HTC's method since I had already ran the update to 1.5 shooter. I flashed CWM to the recovery of the phone and took a backup. Loaded ViperROM and all was good.
Last night:
I wanted to load a new kernel since the one I put on there was not working well with WiFi. At the time I did not know i could just boot to HBOOT then go to recovery I thought I had to use Fastboot. Using Fastboot and doing the commands from memory I think I flashed it to the boot instead of recovery... Not exactly sure what I did but whatever it was i'm stuck in a continual reboot that gets no further then HTC.
What I've tried so far to resolve issue:
1. Boot into recovery and restore from backup. - Did not work
2. Boot to recovery and load a new ROM (Myns zip). - Did not work
3. Boot to recovery and load a stock ROM (4.53.651.1_Rooted_deodexed_signed.zip) - Did not work
4. Rename the stock ROM(from above) as PG86IMG.zip and put on SD. - Didnt work
Any ideas cause i'm out and I dont want to go back to my previous Evo 4g.
cgprelude said:
Two weeks ago:
I rooted my phone using HTC's method since I had already ran the update to 1.5 shooter. I flashed CWM to the recovery of the phone and took a backup. Loaded ViperROM and all was good.
Last night:
I wanted to load a new kernel since the one I put on there was not working well with WiFi. At the time I did not know i could just boot to HBOOT then go to recovery I thought I had to use Fastboot. Using Fastboot and doing the commands from memory I think I flashed it to the boot instead of recovery... Not exactly sure what I did but whatever it was i'm stuck in a continual reboot that gets no further then HTC.
What I've tried so far to resolve issue:
1. Boot into recovery and restore from backup. - Did not work
2. Boot to recovery and load a new ROM (Myns zip). - Did not work
3. Boot to recovery and load a stock ROM (4.53.651.1_Rooted_deodexed_signed.zip) - Did not work
4. Rename the stock ROM(from above) as PG86IMG.zip and put on SD. - Didnt work
Any ideas cause i'm out and I dont want to go back to my previous Evo 4g.
Click to expand...
Click to collapse
From what I've read regarding the HTC unlock method, when you boot the custom recovery, the HTC unlock method does not grant the custom recovery write access to the boot partition.
There are only three ways I'm familar with having write access to the boot partition when having used the HTC unlock method:
1) From normal android mode, the boot partition is unlocked and you can flash a kernel/write to it. My application, Flash Image GUI, works great for this purpose.
2) Using fastboot to temporarily load the custom recovery. When using fastboot to temporarily load the custom recovery, the HTC unlock method grants the temporarily loaded custom recovery write access to the boot partition.
3) Having the bootloader directly flash the boot partition via a PG86IMG.zip file.
Hope that helps! Good luck!
#2. That reminds me. I did try to use fastboot to flash the boot partition. I was doing: fastboot boot (kernel i found online as .zip) (stock rom i found online.zip)
This did not work then i tried:
fastboot flash:raw boot (kernel) (rom.zip)
this did not work either. Am i doing this wrong?
Your #3 option. Where can I download the PG86IMG.zip file so that the bootloader will flash my boot partition?
cgprelude said:
#2. That reminds me. I did try to use fastboot to flash the boot partition. I was doing: fastboot boot (kernel i found online as .zip) (stock rom i found online.zip)
This did not work then i tried:
fastboot flash:raw boot (kernel) (rom.zip)
this did not work either. Am i doing this wrong?
Your #3 option. Where can I download the PG86IMG.zip file so that the bootloader will flash my boot partition?
Click to expand...
Click to collapse
2) fastboot boot c:\downloads\custom-recovery.img or temporarily boot the custom recovery with write access to the boot partition to flash the .zip file
also, you can directly flash the kernel, but the modules will not work until you manually push those: fastboot flash boot c:\downloads\boot.img
3) http://goo-inside.me/shooter/ruu - the latest version is 2.08 which must be what you're using to have used the HTC unlock method.
It seems that u have an evo 3d but u are trying to use evo 4g rom. Or maybe I'm not understanding this
Sent From My Pocket
So I already had a rooted (and I'm pretty sure unlocked bootlader) version of the stock Asus and wanted to put CM13 nightly on there. Everything was going smooth until I got to the stage where I have to load into TWRP and I got the error screen with the little dead alien and the red symbol.
Now I can't enter normal boot, but entering recovery mode seems to work. I tried the option to side load a package from ADB on that screen but nothing worked (.zip files extracted, but I got an error on the phone).
As you can tell, I'm really new to this so any help would be greatly appreciated. I tried looking around, but it seems the more common issue is people not being able to enter recovery mode or something similar.
Thanks
Looks like your doing it wrong. Being rooted does not necessarily mean that your bootloader is unlocked.
By the looks of it your in recovery mode with the dead robot with the "error" message. That is normal. To reboot back into system you either have to press (I don't remember) power button and volume up or down button. Then you should see some options with reboot to system. Or if that does not work you can hold the power button till it turns off.
Then you get back into Android, download the official bootloader unlock tool from ASUS and install it on your device. NOTE: If you updated to MM then this will not work and this will void your warranty.
Run the tool and press unlock and it should reboot into fastboot where it should begin the unlocking process. I believe it should automatically reboot and you should see that the Asus logo is now black instead of white. If not, repeat the process.
You can now proceed to flash twrp recovery. Boot into fastboot/bootloader mode either with "adb reboot bootloader" or hold a specific set of buttons while off to go directly into fastboot.
On the computer, connect your device and type in "fastboot flash recovery (path to twrp IMG without brackets)"
When done you should be able to reboot into twrp recovery where you can flash the cm13 zip.
Hope this helped.
1 week ago i bought in china the watch .i dont know Chinese and i was just there for business so i thought that when i will connect to my phone it will automatically change to English but that never happend . So i tried several threads in xda to understand how it is working and what can i do . And i followed the thread that says to flash another system img recovery and boot . So i first unlocked the bootloader and booted on it and i flash the images and tried to reboot to recovery but already the recovey option in the bootloader is missing i get only shutdown , reboot , reboot bootloader , so i thought that i haven't correct flash the recovery.img so i flash it again but still the same . I also tried twrp recoveries and other recoveries that i found in other threads but still the same i can only boot to bootloader and nothing else . Has any one had the same problem and fixed it ? And if not were can i find the stock chinese firmware to try to flash it maybe it will come back to life .. thanks in advance
Have you tried using adb and fastboot commands?
Ex::
adb reboot-bootloader (for bootloader)
adb push xxxxxxx.img or xxxxxxx.zip /sdcard/ (for transfer files to sdcard)
adb push recovery.img /sdcard/ (for transfer yours custom recovery - i recommend the latest 3.1.1.0 because the others have some bugs)
after that boot to recovery: fastboot boot recovery.img (personally i never tried to flash the recovery but just boot it, baut it works)
from recovery just install the files that you have transferred earlier to sdcard (oh, and prior that erase everything except internal memory, or that toot but you have to transfer your files again)
ex: install zip (i recommend negalite) after that install kernel (negalite too) and install performance or battery booster .
Oh, after kernel install, it will automatically reboot, so you have to repeat the process to install the booster.
Reboot.
p.s. - the reboot process take LOOONG, so wait patiently.
Hope i could help you.
Currently my watch is stuck on AW boot logo from Skin Sturgeon kernel, how can I boot back to stock to reflash? Am unable to access adb as it doesn't seem to get that far in the boot process.
Enter bootloader
spicerackk said:
Currently my watch is stuck on AW boot logo from Skin Sturgeon kernel, how can I boot back to stock to reflash? Am unable to access adb as it doesn't seem to get that far in the boot process.
Click to expand...
Click to collapse
If you want to enter the bootloader, to choose, where u want to reboot and you are stuck:
Hold the button on your watch...hold it, till you feel the first vibration after the restart at the HUAWEI-Logo. Then, press the button once again (Its just timing).
It should show you your bootloader and you can restart into recovery or wherever you want.
Hope I could help :highfive:
Hi,
So I've flashed my phone with HTC_U11_Eyes_1.00.709.7_rom_backup.zip found here and now I can't get past boot screen with the usual "This build is for development purposes only...".
Screenshot attached.
I keep trying to reset the phone or power it off, in order to get to fastboot/download/recovery and try to get it back to life. BUT, any reboot ends up on the same screen within a second.
Does anyone know how I can save it? Flash it back to stock, anything?
It's a Chinese version bought in China, if that's of relevance.
Thanks!
You should wait U11 eyes out of power, then hold volume down button and plug in USB cable, it will boot to download mode.
While under download mode, leave it charge to 50% then flash TWRP recovery into boot, recovery partition.
https://twrp.me/htc/htcu11eyes.html
Code:
fastboot flash boot twrp-3.2.3-0-hay.img
fastboot flash recovery twrp-3.2.3-0-hay.img
According to your issue, I assume that your device is htc_haydtwl or you can execute the command below and provide the log here.
Code:
fastboot getvar all
Now you should flash RUU to unbrick the device.
https://forum.xda-developers.com/u11-eyes/how-to/rom-htc-u11-eyes-ruu-1-00-1405-9-t3756115
If you can go to download mode you can try this HTC Stock ROM Global not RUU and it has google apps.
https://drive.google.com/file/d/1l06p8Gc5zJ1csnH6knVOKbFPunlBpD08/view?usp=drivesdk
Download the file and saved it on SD then plug it in your phone, go to download mode and choose update from SD then wait a while
Note: this Stovk ROM is Android 7 and not rooted or modified.
Hi guys,
I tried to flash TWRP on my Wiko Lenny 4 earlier.
I used adb and fastboot to flash it, however the touchscreen wouldn't work and I was stuck at the "swipe to allow kernel modifications" screen in TWRP. No problem, I reboot in recovery mode, and switched to fastboot mode.
I found another TWRP image and, after flashing with
-> fastboot flash recovery twrp.img
I typed another command,
- >fastboot boot twrp.img.
Since then I am stuck at the Wiko boot screen, saying:
Orange State
Your device has been unlocked and can't be trusted (initially I unlocked OEM)
Your device will boot in 5 seconds
Whatever combination of power+vol up/down I try to use, it only reboots to this screen.
adb won't reconize any device, as well as fastboot. And both are up-to-date.
Perhaps there exists a recovery image that I can put on my sd card, and hopefully it will automatically boot on the sd card as I don't have any control right now.
If someone has an idea, please tell me.
thanks
[EDIT] Solved
Using this link https://aiomobilestuff.com/how-to-unbrick-wiko-stock-firmware-via-wiko-official-site/
I was able to download Wiko's recovery tool from https://customer-world.wikomobile.com/
After unzipping and starting the software, it automatically installed drivers (I guess, if it does not, mediatek usb wiko drivers can be used instead) and downloaded the software into the phone which works now.