I flashed the 4.1.1 OTA and after that I installed the Chainfire3D driver. After the reboot the phone didnt boot anymore. I pulled the battery and tried to boot into recovery but I couldn't.
The phone show this when I try to boot into recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then I tried to flash the recovery again via fastboot. Thing is
Code:
fastboot devices
doesn't list the phone as being connected. I tried 4 different usb ports on my machine.
Also, my phone is listed as unknown device in the device manager although the USB drivers are installed.
Is it dead?
No your phone isn't dead. If it still has root installed, you can download ROM manager from the play store and flash CWM from there. However it won't stick and you will have to flash it again after every reboot. But I think there is a fix somewhere. Just search the forums.
Sent from my Nexus S using xda premium
If not even get goo manager beta from market and install twrp recovery and then u should be good to go
Sent from my PG86100 using xda premium
steven.truong said:
No your phone isn't dead. If it still has root installed, you can download ROM manager from the play store and flash CWM from there. However it won't stick and you will have to flash it again after every reboot. But I think there is a fix somewhere. Just search the forums.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
You just have to rename the recovery script in /system/etc, reboot into fastboot and flash CWM and it'll stick.
Smh. The op said the phone WONT BOOT! He can't go to the market....
Op your phone is fine. That picture you posted is the stock recovery. Which is useless for you at the moment.
Boot the phone into the bootloader. Use fastboot on a computer to do one of these things. Flash or boot a custom recovery/do a full wipe and flash a full ROM with it. If you want to return to stock ics flash the factory images with fastboot.
Accepted solution
kkk this is my problem. sorry my english is very bad. next link is read and your problem solution.
http://forum.xda-developers.com/showthread.php?t=1572307
Next is my step. Very good.
On Windows:
1) copy the ecxtracted files (two times with 7zip) on android-sdk/platform-tools/ (this is important, if you dont unzip it, dont complain about "radio couldnt be loaded")
2) run a cmd and moves in "platform-tools" folder
3) write those command:
4A) If you are coming from a custom rom, this wipe your data/cache:
adb reboot bootloader
fastboot flash bootloader bootloader-crespo-********.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-********.img
fastboot reboot-bootloader
fastboot -w update image-********.zip
I install my nexus s i9023 and android JB 4.1.1 then Chainfire3d installed. But not reboot again. I re-flash ICS and update JB. Chainfire is not running JB.
1) You first re-flash your ICS rom
2) Install CWM 6.0.1
3) Updade ICS to JB 4.1.1
3) Re-install CWM 6.0.1
4) Simple root install.
5) Not install again Chainfire3D. kkk it is not compatible JB.
Related
introduction
Hey guys, I was trying to figure out how to root my device so I could install CWM, so I could install jellybean or something... I totally forgot I made a one-click CWM installer.
Here is a one-click for the Defuse1.5 kernel by LinuxBozo with CWM installed. It's old, but it's a good launchpad for a stock device.
This works on Windows, Linux and Mac and Windows and Linux. Make sure you follow the in-app directions if you've never used Heimdall.
Instructions
1. reboot into Download Mode
2. click the flash button in this app
3. if any problems, repeat with flash bootloaders option checked
4. reboot into recovery
5. flash rom
6. advanced>reboot recovery you will now see a blue recovery instead of orange.
7. flash rom again
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Usually i show it with the Green Connected icon at the bottom, but I decided to release this as an afterthought. Sorry.
Download
http://files.teamkomin.com/Infuse4G/Infuse4g-Defuse1.5-Kernel-One-Click.jar
Thak you sir, downloading...
Sent from my SGH-I997 using xda premium
Thanks...downloading...
This works on Windows, Linux and Mac and Windows and Linux.
LOL... thank you so much for all that you do !!!
.....still lol.... priceless :good: :good:
AdamOutler said:
1. reboot into Download Mode
2. click the flash button in this app
3. if any problems, repeat with flash bootloaders option checked
4. reboot into recovery
5. flash rom
6. advanced>reboot recovery you will now see a blue recovery instead of orange.
7. flash rom again
Click to expand...
Click to collapse
Quick question, Adam.
In step three, you had wrote, "repeat with flash bootloaders option checked."
Does this package contain GB bootloaders, being a 2.2.1 kernel?
If someone came directly from 2.2.1 and had never had a previous GB bootloader, will they see the distorted rainbow recovery?
I was not sure if this package had bootloaders.
Thanks.
Thanks, but when click on the download link I just get a page that says welcome to nginx...
qkster said:
Quick question, Adam.
In step three, you had wrote, "repeat with flash bootloaders option checked."
Does this package contain GB bootloaders, being a 2.2.1 kernel?
If someone came directly from 2.2.1 and had never had a previous GB bootloader, will they see the distorted rainbow recovery?
I was not sure if this package had bootloaders.
Thanks.
Click to expand...
Click to collapse
I didn't see that problem. Link may be down for a while. Server issues..
Here's a link.
So I'm trying to flash a ROM that will grant me root access and the person who made the ROM doesn't explain how to flash it.
I've heard of ADB and Fastboot before but I have no idea where to even start. This is the contents of the .zip:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is the original thread: http://www.needrom.com/download/infocus-m512
Thanks
I tried searching for a guide on how to flash a ROM with adb/fastboot but I'm not even sure if im searching for the right things
Anyone?
Before you flash a custom ROM, make sure you have a custom recovery installed. This is the part where ASB/FastBoot comes in.
The custom recovery may be CWM or TWRP, or anything at all which supports your device, look on the website of the recovery you want to use if they support your device or seach the XDA forums for one.
After downloading the recovery image, you can optionally rename it to recovery.img.
You can use the zip file you curently have, but I'll advice to use the adb installer which I've included as attachment.
Once you have ADB installed with the installer you can omen op a command promt (cmd.exe).
Make sure your device is turned on and USB debugging is enabled!
After ADB sees your device (with the command: adb devices), boot into fastboot using adb reboot bootloader.
After your phone has rebooted into the bootloader(fastboot), use the command: fastboot flash recovery (path/filename to recovery).img
Following these steps should allow you to install a custom ROM through the recovery you justs installed. if you also want to include superSU(if it's not included into the ROM you're using), flash the SuperSU2.02 falshable zip from chainfire.
But before you do anything of this, make sure you've got a compatible recovery and ROM!
Khatarian said:
Before you flash a custom ROM, make sure you have a custom recovery installed. This is the part where ASB/FastBoot comes in.
The custom recovery may be CWM or TWRP, or anything at all which supports your device, look on the website of the recovery you want to use if they support your device or seach the XDA forums for one.
After downloading the recovery image, you can optionally rename it to recovery.img.
You can use the zip file you curently have, but I'll advice to use the adb installer which I've included as attachment.
Once you have ADB installed with the installer you can omen op a command promt (cmd.exe).
Make sure your device is turned on and USB debugging is enabled!
After ADB sees your device (with the command: adb devices), boot into fastboot using adb reboot bootloader.
After your phone has rebooted into the bootloader(fastboot), use the command: fastboot flash recovery (path/filename to recovery).img
Following these steps should allow you to install a custom ROM through the recovery you justs installed. if you also want to include superSU(if it's not included into the ROM you're using), flash the SuperSU2.02 falshable zip from chainfire.
But before you do anything of this, make sure you've got a compatible recovery and ROM!
Click to expand...
Click to collapse
Thanks for your help, I got it working. Much appreciated
Well i downloaded the new developer preview for m
and tried to flash the usual way
Then i encountred this error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
tried running cmd in admin mode too, no effect.
The method i used is as follows
I extract the zip in the folder to get access to the images inside and then flashed them manually.
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system sysytem.img (did not work)
fastboot flash userdata userdata.img
Click to expand...
Click to collapse
Running Fastboot and adb v 1.4 from here
http://forum.xda-developers.com/showthread.php?t=2588979
Kindy someone assist thank you
Your image doesn't show
Sent from my Android M Nexus 5 yo!
Try to reboot to your bootloader, and then flash system.img.
Schoat333 said:
Try to reboot to your bootloader, and then flash system.img.
Click to expand...
Click to collapse
i try this and still get the error
Schoat333 said:
Try to reboot to your bootloader, and then flash system.img.
Click to expand...
Click to collapse
I tired that.
I actually even tried restarting the bootloader after flashing every component.
Seems this fastboot has some issues with android m.
Can anyone who has flashed it provide some input.
Sent from my A0001 using XDA Free mobile app
I had the same problem. Not just with android M, other Google OEM Roms. I was only able to get it to work by doing it on my Mac. I would think that Linux would have no problem either.
I had no issues flashing M through fastboot - even used flash-all.sh.
I couldn't get M to boot until I individually erased each part using fastboot, and then individually flashed each part, extracted from Google's zip, also using fastboot.
lnchbx said:
I had the same problem. Not just with android M, other Google OEM Roms. I was only able to get it to work by doing it on my Mac. I would think that Linux would have no problem either.
Click to expand...
Click to collapse
I can't get it to work on my Mac! I keep getting the data length too large error when trying to flash system.mg. Everywhere I've looked has said update the sdk, but I'm on the latest version.
theChief_ said:
I can't get it to work on my Mac! I keep getting the data length too large error when trying to flash system.mg. Everywhere I've looked has said update the sdk, but I'm on the latest version.
Click to expand...
Click to collapse
You need to pass the '-s' argument to fastboot to be able to flash system.
Redownload the file could be corrupt. Only other thing try using mfastboot(google it)
Hello everybody
Well, I have his issue. I tried to flash some new roms into the OPO yesterday and I had some issues with one, so I decided to flash other one, but when I wiped the things I also wiped the internal storage and I didnt know that that would erase my OS, now i'm trying to flash a rom but it wont let me with the bootloader because it says its locked, and if i try to unlock it using OPO toolking via ADB sideload the phone shows it requires ADB 1.0.32 which is the same that i have installed on my computer and if I try it using the bootloader option it just restarts and it keeps being locked. If I try to send a rom with the CMD on my pc it says "error: closed"
I have done some research and found some similar cases but not simiilar enough to have the same fixes
I have windows 10 and TWRP is 2.8.7.0
If anybody helps me that would be pretty useful
Thanks!
minor9719 said:
Hello everybody
Well, I have his issue. I tried to flash some new roms into the OPO yesterday and I had some issues with one, so I decided to flash other one, but when I wiped the things I also wiped the internal storage and I didnt know that that would erase my OS, now i'm trying to flash a rom but it wont let me with the bootloader because it says its locked, and if i try to unlock it using OPO toolking via ADB sideload the phone shows it requires ADB 1.0.32 which is the same that i have installed on my computer and if I try it using the bootloader option it just restarts and it keeps being locked. If I try to send a rom with the CMD on my pc it says "error: closed"
I have done some research and found some similar cases but not simiilar enough to have the same fixes
I have windows 10 and TWRP is 2.8.7.0
If anybody helps me that would be pretty useful
Thanks!
Click to expand...
Click to collapse
SOLUTIONS THAT MIGHT WORK
1) Use Fastboot instead of Sideload
Cmd
Go to Fastboot folder with CD
Boot into Fastboot , then type fastboot devices.
If you see the Oneplus One, then just download a random ROM and FLASH the ZIP
2) [Toolkit] Wug's Bacon Root Toolkit v1.0.3 [Updated 04/16/15] by WugFresh ---> LINK
Screenshots 1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Screenshot 2
3) [GUIDE] How to unbrick or make your phone 100% stock by vigneshvar1
This installing Android CM11s but you can afther that installing a other rom of your choise. --> LINK
Hey there,
I´ve received my used Oppo today and couldn´t do stuff with it so I decided to flash it with CM13 and after some more things I did, I couldn´t restore my backups properly anymore (why I find odd and this has never happened to me before). Then I decided to switch back to ColorOS 2 following the instructions on oppoforums.com. Somehow I think that when I finished step 4: To make a clean install please select "Wipe data and cache", press "Yes" when it's done. my entire internal storage was wiped :-/ instead of wiiping data and cache it turned off and on and so on....it didn´t boot into ColorOS so I went with booting into TWRP again. There I found that I can only see some folders of Interal Storage
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(open in new tab). I managed to adb-move the file "cm-13.0-20160311-NIGHTLY-r7plus.zip" into /sdcard and tried to install it from there which it apparently does successfully
.
When I click reboot -> system it still boots into TWRP everytime :crying:
How can I boot into an OS again? My computer recognizes my phone and I have adb access.
hmm... try use msm download tool
I have the same issue couple of days before... do this
Download Stock Recovery.
Boot in to fastboot
and flash stock recovery using this command fastboot flash recovery stock.img
After flash use command fastboot reboot
if you see wiping data and gone black screen then follow this....
Use this command. fastboot boot stockrecovery.img
now you can boot to stock recovery and you will see fully loaded wiping bar and it shoul reboot the phone. Now its done.
Power of the phone by press and hold. And boot to recovery asusal u do...flash the rom.
for qurey whatsapp me +919790397283
sriszone said:
I have the same issue couple of days before... do this
Download Stock Recovery.
Boot in to fastboot
and flash stock recovery using this command fastboot flash recovery stock.img
After flash use command fastboot reboot
if you see wiping data and gone black screen then follow this....
Use this command. fastboot boot stockrecovery.img
now you can boot to stock recovery and you will see fully loaded wiping bar and it shoul reboot the phone. Now its done.
Power of the phone by press and hold. And boot to recovery asusal u do...flash the rom.
for qurey whatsapp me +919790397283
Click to expand...
Click to collapse
Thanks, this actuually did it for me! I tried adb sideload, but that didn´t work.
https://goo.gl/photos/vSRMhRjyxr4MW8CA7
No ... Dont side load.
Just boot to twrp. Not flash.
Go to Fastboot. and boot . use this command. fastboot boot twrp.img
then you can mount internal storage.