Database Users

I bricked my Nexus S. Please help.

I tried looking around the forums to see if someone has had this problem before. Couldn't find something similar.
I had stock 4.0.3 installed and I saw today that 4.0.4 was being pushed out. Since 4.0.3 wasn't a stock build I tried to downgrade to 2.3.6 in order to keep everything stock. I rooted the phone, installed the ROM Manager and flashed 2.3.6 through Clockworkmod Recovery. Everything went smoothly but when I powered on the phone force quit messages kept popping up and I can't get past the welcome screen. When I go into Fastboot mode and try to go in Recovery mode it just shows the Android symbol and a warning sign. I tried flashing a recovery .zip file I found online through fastboot but couldn't manage to do it (I'm on Mac OSX)
Can someone please help me? I'm completely desperate and wouldn't care about erasing everything (I think I already did, actually).
Thanks in advance.

flash a recovery.img
that multiple fc happened to me when i installed a i9023 rom on my i9020a.
unzip the recovery.zip and flash the .img file through fastboot and make sure you have the right rom for your model

Thank man, but that's what I tried to do. I got confused and wrote that it was a .zip up there. I'm really confused and couldn't flash the .img. Could you walk me through it? or point me to a thread that shows me how to do it?

im not sure how a mac is set up, i can walk you through flashing it on windows through command prompt ...

Please do that. I guess I can try to work it out.
Thanks

http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
memorize that lol it saved me.
you can skip the root part, but it explains how to set up the pc so it'll read the nexus with the correct drivers and whatnot, and what commands to run to flash the recovery. then when youre in the recovery, mount as usb, copy over 2.3.6 (the right one!) and install from zip.

I just tried that. I get this message: "error: cannot load 'twrp-crespo-2.0.0RC0.img'" I don't know what to do!

Can you get into boot loader mode?
Have you tried to use Odin?
http://forum.xda-developers.com/showthread.php?t=947950&highlight=odin
Sent from my Nexus S 4G using XDA Premium App

colettamiguel said:
I just tried that. I get this message: "error: cannot load 'twrp-crespo-2.0.0RC0.img'" I don't know what to do!
Click to expand...
Click to collapse
Did you unlock your bootloader?
Code:
fastboot oem unlock

My LG LS980 device is now bricked

I need big help, my LG LS980 device is now bricked currently works only in recovery mode with ADB commands, any firmware I tried to upload I did not succeed
adb devices
List of devices attached
03xxxxxxxxxxxx07 sideload
adb sideload aokp_ls980_kitkat_unofficial_2014-01-16. zip
sending 100%
on my screen devices
finding update package
Opening update package
Verifying update package
Installing update
assert failed: run_program ("/system/bin/loki.sh") == 0
Installation aborted.
I've tried other firmware that is supposed to my device with similar result
You may need to restore to stock firmware but I can't figure out the process.
Is there anyone who can help me to restore the device

follow steps to reroot and push loki to device, reinstall recovery. try install again.
before redownload different rom and try to install that, aokp is buggy rom anyway, latest 16th build doesnt boot .

bachera said:
follow steps to reroot and push loki to device, reinstall recovery. try install again.
before redownload different rom and try to install that, aokp is buggy rom anyway, latest 16th build doesnt boot .
Click to expand...
Click to collapse
Thanks for your reply, my problem is that I don't understand how do reroot the device.
The device does not have many options, pressing the buttons (power and Vol +) the device enters in a State Factory Hard Reset.
Pressing (power and Vol-) goes into recovery mode and loads the black screen with anticipation for the adb commands
reboot system now
update from external apply sdcard
apply update from cache
apply update from ADB
wipe data/factory reset
wipe cache partition
With closed then press the device (Vol +) and connect the USB cable enters into Download Mode, here you also don't know what to do.
When I hit the power button just opens the device showing the logo of LG and the led flashing in green/blue and after a while makes itself restarted
I searched the forum for reroot and saw that need to do some settings on the device to do root, did I forget something and so I do not understand?
Sorry, I don't understand and become tedious but it's my first time playing with the object

so, you dont have recovery now?
"adb reboot recovery" not working ?

Based on what you said, you are able to get in recovery and adb is working, then push the ROM zip file over and reflash it in recovery.

I'm happy because I just unbrick my device by selecting Download Mode Firmware Update and with the LGFlashTools loaded LS980ZV8_ software 13.51097. tot.
Now I lie in my original problem, I want to unlock to accept SIM card from another provider and another country.
Some help to be able to start from somewhere the unlock process?

id3210 said:
so, you dont have recovery now?
"adb reboot recovery" not working ?
Click to expand...
Click to collapse
Who not any command except devices-sideload-kill server-start server-reboot
any other command, I was giving "error close"
votinh said:
Based on what you said, you are able to get in recovery and adb is working, then push the ROM zip file over and reflash it in recovery.
Click to expand...
Click to collapse
to command push, I was giving "error close"
But all ok, unbrick my devices with LGFlashTools

Great!
Good to hear that.

I need help as well. My phone ls980 is bricked only works in recovery TWRP. Can someone please help me?

antbox12 said:
I need help as well. My phone ls980 is bricked only works in recovery TWRP. Can someone please help me?
Click to expand...
Click to collapse
Did you accidentally accept that update too?
Sent from my SM-N900P using Tapatalk

natefuhr said:
Did you accidentally accept that update too?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
No but I fixed it. I had to put it in download mode and flash the stock rom back to it.

[Q]LG G2 re-flashing or rooting stock 4.4.2 bad rom

Hi all,
First off I've tried now for a two days to solve this, reading as much as I could find on here and the rest of the internet.
I decided to root my LG D802 running 4.2 and install CWM recovery no problem. Next I flashed a stock 4.4.2 vodaphone img. All went well untill i tried to use the touch screen, which shows that when i press on one point on the screen it selects multiple points basically its unusable and unable to do almost anything with it, however i have managed to turn on ADB and connect to the phone. So now i have a stock recovery and an unusable ROM.
So next up I tried to rooting it since I had ADB shell working ok, using the IOROOT25. This appears to work as when it reboots and installs the kkroot.zip in the recovery it's saying it worked. Now when I reboot and open ADB shell then type SU to get root I can't press ok when superuser pops up to asking me to give it permission, because of the touch screen problem.
If i can get root in ADB then remount the files system then i will be able to DD a new recovery img??
After getting this far and loosing, I then found this: http://forum.xda-developers.com/showthread.php?t=2432476 on flashing to stock, but the program crashes every time it's about to flash, so i tried doing a fresh install of windows 7 and then tried windows 8 however the program still crashes every time and yes I have followed the instructions and tried the manual method and checking the 127.0.0.0. lgblahblah is there
So no I am turning to you guys for help.
phone details;
Model: D802 32GB
Firmware operator: VDF
sw version: D80220a
ro.build.fingerprint: lge/g2_vdf_com/g2:4.4.2/KOT49I.D80220a/D80220a.1392133741:user/release-keys
Recovery: <3e> KOT49I.D80220a test-keys

UPADATE: I have root but getting this error when trying to flash the recovery:
+] loki_flash v2.0
[-] Loki aboot version does not match device.
any ideas?
Ok so i found a different aboot img pushed to the phone and flashed that using dd
Code:
dd if=/data/local/tmp/about.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
this solved the problem above and a allowed me to flash cwm recovery. This then broke the installed rom so it wouldn't boot. now I had a custom recovery i flashed a EUR open 16gb stock zip this all went well and now i have a working phone What i should of done is remove the stock recovery.img from the zip and the line to flash it in the update script so it didn't flash the stock recovery.
This now leaves me with the loki flash problem above when trying to flash a custom recovery i could flash a different aboot.img but i don't want to break the current rom.
Any one else found a way to solve this problem?

need help
need help please!!
i have pretty much the same as your first problem, i installed the vodafone kitkat and the touch went crazy
and the custom recovery was deleted
and the lg support tool doesnt work for me
i dont know what to do.
sorry i forgot to mention that my phone is lg g2 d802 16 GB

Mustafa1 said:
need help please!!
i have pretty much the same as your first problem, i installed the vodafone kitkat and the touch went crazy
and the custom recovery was deleted
and the lg support tool doesnt work for me
i dont know what to do.
sorry i forgot to mention that my phone is lg g2 d802 16 GB
Click to expand...
Click to collapse
Have you tried running IO root to again root on your device? Also do you know much about linux, command line and android tools like ADB? Or do I need to explain the commands step by step?

twon23 said:
Have you tried running IO root to again root on your device? Also do you know much about linux, command line and android tools like ADB? Or do I need to explain the commands step by step?
Click to expand...
Click to collapse
i downloaded ioroot25 and extracted it and ran root.bat
Looking for device...
Make sure drivers are installed. Check Windows Device Manager.
Make sure proper USB Debugging mode is enabled.
Verizon users make sure ethernet mode is selected.
Did you check phone screen for Yes/No prompt?
(select checkbox to always remember then hit yes)
...sometimes you need to unplug the USB cable then re-plug.
Determining device model...
Rebooting into stock recovery...
When recovery loads, select: *apply update from adb* with power button...
then press Enter/Return on your keyboard.
Press any key to continue . . .
(here the phone restarts and LG logo appears with (secure booting error)message in the upper left corner, and when i press any key)
Reboot back into System after flash in recovery finishes.
Press any key to continue . . .
and when pressing any key the cmd closes and the phone stays on with black screen and the back light on
in the pc i get many windows about formating drives (from H to S)
and i dont know anything about linux or command line
would you explain it to me??

Ok so your phone not longer boots, correct? Do you know what build/version plus any other details of the rom you flashed? or even a link so i can have a look at the rom you have installed. Can you get into recovery mode and is it still a stock recovery image? also what is your phone d802? 16gb 32gb?

Mustafa1 said:
i downloaded ioroot25 and extracted it and ran root.bat
Looking for device...
Make sure drivers are installed. Check Windows Device Manager.
Make sure proper USB Debugging mode is enabled.
Verizon users make sure ethernet mode is selected.
Did you check phone screen for Yes/No prompt?
(select checkbox to always remember then hit yes)
...sometimes you need to unplug the USB cable then re-plug.
Determining device model...
Rebooting into stock recovery...
When recovery loads, select: *apply update from adb* with power button...
then press Enter/Return on your keyboard.
Press any key to continue . . .
(here the phone restarts and LG logo appears with (secure booting error)message in the upper left corner, and when i press any key)
Reboot back into System after flash in recovery finishes.
Press any key to continue . . .
and when pressing any key the cmd closes and the phone stays on with black screen and the back light on
in the pc i get many windows about formating drives (from H to S)
and i dont know anything about linux or command line
would you explain it to me??
Click to expand...
Click to collapse
If you're running root.bat as an admin, try executing it without admin privileges. Dunno why, but it seemed to work for me.

Mustafa1 said:
need help please!!
i have pretty much the same as your first problem, i installed the vodafone kitkat and the touch went crazy
and the custom recovery was deleted
and the lg support tool doesnt work for me
i dont know what to do.
sorry i forgot to mention that my phone is lg g2 d802 16 GB
Click to expand...
Click to collapse
Did you try to flash CWM recovery? http://forum.xda-developers.com/showthread.php?t=2582142 This thread has What you need to do .. After then you can nandroid backup after then wipe everything except EFS on twrp after that you can stock_kitkat.zip on the xda forum. Efter that restore data via twrp.
I think that It will be correct without deleting your current rom ...
---------- Post added at 06:18 PM ---------- Previous post was at 06:12 PM ----------
makgun said:
Did you try to flash CWM recovery? http://forum.xda-developers.com/showthread.php?t=2582142 This thread has What you need to do .. After then you can nandroid backup after then wipe everything except EFS on twrp after that you can stock_kitkat.zip on the xda forum. Efter that restore data via twrp.
I think that It will be correct without deleting your current rom ...
Click to expand...
Click to collapse
NOT CWM , it is TWRP
Are you from turkey?

twon23 said:
UPADATE: I have root but getting this error when trying to flash the recovery:
+] loki_flash v2.0
[-] Loki aboot version does not match device.
any ideas?
Ok so i found a different aboot img pushed to the phone and flashed that using dd
Code:
dd if=/data/local/tmp/about.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
this solved the problem above and a allowed me to flash cwm recovery. This then broke the installed rom so it wouldn't boot. now I had a custom recovery i flashed a EUR open 16gb stock zip this all went well and now i have a working phone What i should of done is remove the stock recovery.img from the zip and the line to flash it in the update script so it didn't flash the stock recovery.
This now leaves me with the loki flash problem above when trying to flash a custom recovery i could flash a different aboot.img but i don't want to break the current rom.
Any one else found a way to solve this problem?
Click to expand...
Click to collapse
Hi! I've recently flashed an updated stock ROM and have the same Touchscreen issue as yourself! Can you tell me the steps you have done to fix it? I'm using windows 8.1 to flash etc, and using a stock ROM I can't seem to get it to work again

Get rid of shutting down after "device corrupt" message - so possibility to gain root

Get rid of shutting down after "device corrupt" message - so possibility to gain root
Some of you might face the problem that whatever you do anything you change on your device in order to gain root even if your bootloader is unlocked your device is turning off after promting "device corrupt, etc..." message.
Sometimes you can't even unbrick with lg bridge cos' it can't see that your firmware has any problems.
Typical symptom of this problem that very interestingly your phone is not showing any corrupt messages during normal boot up even if your bootloader is unlocked (it should write some warnig message at every boot up).
Also when you "fastboot boot yourstockbootimage.img" it's booting up but writing some network related error then shuts down saying corrupt battery.
In order to root your phone you must be able to change the firmware a bit (tweak the boot image).
First of all you need to unlock your bootloader if you didn't do it yet: http://forum.xda-developers.com/lg-k10/how-to/unlock-bootloader-lg-k10-mtk-devices-t3486302
All you have to do is allow modifications in TWRP step 2.1 here: https://forum.xda-developers.com/lg-k10/how-to/friendly-root-method-lg-k8-k10-t3531223
It means the rest written under is fully unnecessary but i keep it just in case the above mentioned method would not work for someone:
Other requirements:
- lg up working with your device: http://forum.xda-developers.com/lg-k10/how-to/flashing-firmware-using-lg-t3517839
- kdz firmware
- twrp recovery of your device (usually you can find it in your favorite root thread or somewhere on xda)
Extract boot image from your firmware with lg firmware extractor (http://viid.me/qe7ufH). First you have to extract the ".dz" file and then the boot image form that ".dz" file.
Once you have your boot image (eg. boot_157696.bin) rename it to "boot.img"!
Put this "boot.img" on your sd card!
Flash this firmware (that you taken your boot image form!!!) on your phone with LG UP.
Boot up and see if it works also tick all the necessary options (oem unlock in developer options, usb debug,...)
Reboot to fastboot, check if your bootloader is still unlocked ("fastboot getvar all"). If it's locked unlock it!
Boot into your TWRP (fastboot boot twrp.img), you can allow it to read system.
Go to "install" (tick install image) and flash your "boot.img" form your sd card (naturally onto your boot partition).
Now before you reboot make a full wipe (fastory reset) in TWRP (wipe menu) then you can reboot to system.
After the "device corrupt" message it must be booting on and boot up normally and during every boot up there should be that message.
Now you can go and root your phone - always use that boot image you just flashed during the first step of the root process (recompress this boot image to gzip and ... read a rooting guide: http://forum.xda-developers.com/lg-k10/how-to/twrp-root-lg-k8-k350n-t3475807 there this should be "bootlz4_0.img")
There is no explanation why it works... wierd.

Hi.
I have this problem, corrupt device screen and continuous bootloops, I only have access to the download mode, but LG UP does not allow me to flash the .kdz even though I have the boot.img file on the sd card. It shows me the typical error at 9% of the process 'Error code = 0x81000304, CBasicFlash :: _func_LoadGptF - ErrorCode: 8222'. Would someone tell me what it is and how can I fix it?
I have tried to revive the cell phone in myriad ways and it is not possible for me.
I appreciate any suggestions.
Thank you very much.

Llony said:
I appreciate any suggestions.
Thank you very much.
Click to expand...
Click to collapse
This thread is not about bootloops but shutting down. Different subject. You should start a new thread about it.
However i looked at it, check out this comment:
http://forum.xda-developers.com/showpost.php?p=66135219&postcount=74
anyways if i were you i'd do a hard reset (http://www.hardreset.info/devices/lg/lg-k10/) and then i'd use lg bridge's update error recovery function (or you can change the order - first lg bridge, then hard reset).
Also make sure you chose "refurbish" when you use lg up and also make sure you are using the right kdz file (i recommend using lg mobile support tool to download your kdz - there is a possibility under options and upgrade recovery that using your imei it downloads the kdz to a hidden folder: http://forum.xda-developers.com/showthread.php?t=2395323)

I have bootloop with usb connected, without usb powered off

Llony said:
I have bootloop with usb connected, without usb powered off
Click to expand...
Click to collapse
I see... okay. However check out what i wrote above and one more thing: make sure you use usb 2.0 not any 3.0 ports.

I still do not find the solution, LG Up detects that it has installed the version k43010y, this version does not even exist! And I still give the error to 9% of the process. I do not know what to do to recover it

Llony said:
I still do not find the solution, LG Up detects that it has installed the version k43010y, this version does not even exist! And I still give the error to 9% of the process. I do not know what to do to recover it
Click to expand...
Click to collapse
Did you try lg bridge - update error recovery?

LG Bridge It does not give me the option to recover update error. And the LG flash tool before starting the process shows me 'contact the system administrator'. He does not let me get him back in any way.
Would it be possible to enter the fastboot mode through the download mode? So I guess I could try to flash an unmodified boot.
Thanks.

Llony said:
LG Bridge It does not give me the option to recover update error. And the LG flash tool before starting the process shows me 'contact the system administrator'. He does not let me get him back in any way.
Would it be possible to enter the fastboot mode through the download mode? So I guess I could try to flash an unmodified boot.
Thanks.
Click to expand...
Click to collapse
What do you mean it doesn't give you the option? I mean LG bridge, there is no update error recovery on the software update page? As in this video:
https://www.youtube.com/watch?v=b_GqAG02OXU

Phones in a bit of a state

Hey guys,
Yesterday I tried, after a few months of not modding my phone, to update my recovery as i was running a very old version of TWRP. Long story short I did something wrong somewhere and my phone has ended up in a bit of a weird state.
At the moment the OS is BlissRom, however it fails to boot. The loading screen runs very slowly and never actually boots the OS. The current recovery is the stock recovery.
The thing that is giving me an issue is the fact that somehow the bootloader has locked, so I am unable to flash a new OS onto my phone. I'm not able to flash anything onto my phone as it throws an error telling me the phone is locked.
Overall I aren't able to boot into the OS, however I have access to the stock recovery and fastboot. Unfortunately it looks as though the bootloader has locked some how.
Any ideas how I can fix this, or have I completely messed my phone up?
Thanks in advance.

Hi
U said u were running twrp before which means u have unlocked bootloader and flash roms already.
How did u end up with stock recovery?
Also is it phone being detected bycur PC?
Sent from my ONE A2005 using Tapatalk

I believe it was a result of running the QualComm restoration tool. I ran this and it didn't look as though it did anything however after i rebooted into recovery I found it was stock.
I'm not sure if using this tool also re locked the bootloader however as it appears to be locked and I cant flash anything in fastboot mode.

colinbest2 said:
I believe it was a result of running the QualComm restoration tool. I ran this and it didn't look as though it did anything however after i rebooted into recovery I found it was stock.
I'm not sure if using this tool also re locked the bootloader however as it appears to be locked and I cant flash anything in fastboot mode.
Click to expand...
Click to collapse
Did u also tried command fastboot oem unlock
Sent from my ONE A2005 using Tapatalk

Indeed I have, I get an error saying "phone is locked".
I think the resolution will be running the restoration tool fully but i cant seem to get it to do anything. It just sits there with no progress bars appearing.
Have you ever had any experience with this tool?

No I never used recovery tools.
Can u at any point let's say u boot into recovery and connect the device to PC, will it detected the internal storage?
Sent from my ONE A2005 using Tapatalk

Unfortunately not, if I boot the OS it gets stuck at the loading animation, it isn't a bootloop oddly enough.
Booting in recovery the PC doesn't detect the internal storage, however if I choose "Update from USB" I can see that ADB detects my phone in sideload mode.
Much like in fastboot mode I can see my PC detects my phone in fastboot mode.
I do have some OS zips on the internal storage which I have tried flashing in stock recovery, however these always result in "Install failed" errors.

Dude i think you have to use recovery tool now
Here is the link first read carefully https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/

Thanks for the link buddy.
I've gone through this thread, I think the issue preventing this from working for me is the fact that although I have installed the relevant drivers, when I plug my phone into my PC the drivers assigned to it are "Android Bootloader Interface". When I try to target another driver, using the Update driver functionality it just refuses to change, saying the driver already assigned is the newer one.
Any ideas how I can get around this? I know ideally it should appear as Qualcomm 9008. I've tried all the methods in the "How to Make the device show as Qualcomm 9008" section without any success.

colinbest2 said:
Unfortunately not, if I boot the OS it gets stuck at the loading animation, it isn't a bootloop oddly enough.
Booting in recovery the PC doesn't detect the internal storage, however if I choose "Update from USB" I can see that ADB detects my phone in sideload mode.
Much like in fastboot mode I can see my PC detects my phone in fastboot mode.
I do have some OS zips on the internal storage which I have tried flashing in stock recovery, however these always result in "Install failed" errors.
Click to expand...
Click to collapse
Here's what to do...
U will need to sideload the stock rom which can be downloaded from here: https://s3.amazonaws.com/oxygenos.o...4_OTA_020_all_1608262242_44a55e674a2b4bf6.zip
-Place the zip in ur adb folder and rename it to update.zip.
-Connect the Oneplus2 to the PC with USB cable and open a command prompt or terminal on your PC. To do this open the ADB folder press shift + right click and click on open command here.
-Reboot to recovery and select install from usb.
-Flash the OxygenOS on OnePlus 2 by typing:
adb sideload update.zip
-Now the update will start and this will take some time.
Hope it helped[emoji106]
Sent from my ONE A2005 using Tapatalk

Brandon Indar said:
Here's what to do...
U will need to sideload the stock rom which can be downloaded from here: https://s3.amazonaws.com/oxygenos.o...4_OTA_020_all_1608262242_44a55e674a2b4bf6.zip
-Place the zip in ur adb folder and rename it to update.zip.
-Connect the Oneplus2 to the PC with USB cable and open a command prompt or terminal on your PC. To do this open the ADB folder press shift + right click and click on open command here.
-Reboot to recovery and select install from usb.
-Flash the OxygenOS on OnePlus 2 by typing:
adb sideload update.zip
-Now the update will start and this will take some time.
Hope it helped[emoji106]
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
Hey dude, thanks for the help! So I went through these steps and it actually appeared to sideload and update properly.
However now it looks as though my phone is stuck at the one+ logo when I go to boot the OS.

colinbest2 said:
Hey dude, thanks for the help! So I went through these steps and it actually appeared to sideload and update properly.
However now it looks as though my phone is stuck at the one+ logo when I go to boot the OS.
Click to expand...
Click to collapse
Try this one :
https://s3.amazonaws.com/oxygenos.o...4_OTA_019_all_1606041303_bd42fc5cc5cc4ab2.zip
If still stuck on boot logo, boot in fastboot, connect to PC and run command : fastboot erase userdata
If not work try sideload a rom u have with same steps[emoji4]
Sent from my ONE A2005 using Tapatalk