So basically I am not smart and factory reset my phone in settings. The bootloader was unlocked and rooted. First phone I have ever rooted and this is all just a lot of information to take in. Trying to read and look into my problem but nothing I am trying is working.
When I turn my phone on it goes immediately into TWRP. When TWRP came up I wiped the data, cache, and dalvik. Not sure what all I have tried but I can't figure anything out. I am assuming I need to flash a stock ROM back onto my phone? Not sure how to do that. I have a stock rom downloaded. When I try to flash it just says 'waiting for device'. It is plugged in but I am assuming USB debugging is not turned on which is why it doesn't locate it?
Not really sure if my assumptions are correct but I am failing horribly here and would love if someone could explain this to me step by step like I am a cave person. Would even be willing to paypal someone $5 if that kind of thing is allowed for help. Thanks for helping a moron out.
hegro said:
So basically I am not smart and factory reset my phone in settings. The bootloader was unlocked and rooted. First phone I have ever rooted and this is all just a lot of information to take in. Trying to read and look into my problem but nothing I am trying is working.
When I turn my phone on it goes immediately into TWRP. When TWRP came up I wiped the data, cache, and dalvik. Not sure what all I have tried but I can't figure anything out. I am assuming I need to flash a stock ROM back onto my phone? Not sure how to do that. I have a stock rom downloaded. When I try to flash it just says 'waiting for device'. It is plugged in but I am assuming USB debugging is not turned on which is why it doesn't locate it?
Not really sure if my assumptions are correct but I am failing horribly here and would love if someone could explain this to me step by step like I am a cave person. Would even be willing to paypal someone $5 if that kind of thing is allowed for help. Thanks for helping a moron out.
Click to expand...
Click to collapse
Some more information please? Were you on stock rooted or custom rom. Best bet then is clean flashing a custom rom.
GtrCraft said:
Some more information please? Were you on stock rooted or custom rom. Best bet then is clean flashing a custom rom.
Click to expand...
Click to collapse
Pretty sure I was just stock rooted. How would I go about doing that? Like I said, I have a stock rom downloaded on my PC. Tried to flash it but all I get is 'waiting for device' in the cmd window after directing it towards the zip file.
Also as I said, trying to learn and absorb as much info as I can here, never done this before so I am a little slow. =/
just tried using THIS method but when I plug my phone in it is not recognized in RSD Lite. I keep reading I need USB debugging on. I can't turn it on from recovery screen, no? Is there anything I can do?
hegro said:
just tried using THIS method but when I plug my phone in it is not recognized in RSD Lite. I keep reading I need USB debugging on. I can't turn it on from recovery screen, no? Is there anything I can do?
Click to expand...
Click to collapse
Boot to twrp and flash a custom rom zip like lineage os. Or a modified stock rom like stoneware
Yes, wiped phone, put stoneware on my phone, booted to twrp, installed stoneware, reboot, back to twrp. I have to be doing something wrong but I don't know what it is. I have tried doing this with multiple different ROMs, flashing in TWRP.
hegro said:
Yes, wiped phone, put stoneware on my phone, booted to twrp, installed stoneware, reboot, back to twrp. I have to be doing something wrong but I don't know what it is. I have tried doing this with multiple different ROMs, flashing in TWRP.
Click to expand...
Click to collapse
I had this issue when I did (like a idiot) a Ota update. Only fix I got was running g5 plus tool kit and flashing stock Rom though it by following instructions on the program..
Factory reset shouldn't have caused this issue.. Unless you formated your data in twrp.. But if the boot is altered or damaged and you just put a custom Rom on top I think you might find you won't have a baseband (no mobile network).. The original stock Rom is available via links in the windows toolkit 1.6 gig
Go into fastboot and just type fastboot continue
fixed
alevity said:
I has this issue when I did (like a idiot) a Ota update. Only fix I got was running g5 plus tool kit and flashing stock Rom though it by following instructions on the program..
Factory reset shouldn't have caused this issue.. Unless you formated your data in twrp.. But if the boot is altered or damaged and you just put a custom Rom on top I think you might find you won't have a baseband (no mobile network).. The original stock Rom is available via links in the windows toolkit 1.6 gig
Click to expand...
Click to collapse
So I ran the tool kit and put on a stock rom. My phone turns on now! Except when I turn it on it says that the device is unlocked and can't be trusted. ID: bad key.
hegro said:
So I ran the tool kit and put on a stock rom. My phone turns on now! Except when I turn it on it says that the device is unlocked and can't be trusted. ID: bad key.
Click to expand...
Click to collapse
boot into twrp again and reboot system
it should fix it
next time remember just go into fastboot and type "fastboot continue"
no need to wipe or reflash
power off your phone then volume down and power together until bootloader screen appearing than select factory mode and then press power button to select factory mode
hegro said:
So I ran the tool kit and put on a stock rom. My phone turns on now! Except when I turn it on it says that the device is unlocked and can't be trusted. ID: bad key.
Click to expand...
Click to collapse
That's completely normal we all have that just means it's unlocked bootloader. Enjoy your device normally
---------- Post added at 12:47 PM ---------- Previous post was at 12:44 PM ----------
bornlivedie said:
boot into twrp again and reboot system
it should fix it
next time remember just go into fastboot and type "fastboot continue"
no need to wipe or reflash
Click to expand...
Click to collapse
Why would doing that remove the hard coded warning that the bootloader is unlocked? Op had a functioning phone now and just didn't know the warning boot is perfectly OK.
pretty sure my twrp got replaced? idk but when I try to go to recovery all I get is the little dead android guy with the red triangle.
hegro said:
pretty sure my twrp got replaced? idk but when I try to go to recovery all I get is the little dead android guy with the red triangle.
Click to expand...
Click to collapse
That's stock recovery
alevity said:
That's completely normal we all have that just means it's unlocked bootloader. Enjoy your device normally
---------- Post added at 12:47 PM ---------- Previous post was at 12:44 PM ----------
Why would doing that remove the hard coded warning that the bootloader is unlocked? Op had a functioning phone now and just didn't know the warning boot is perfectly OK.
Click to expand...
Click to collapse
I wouldn't know about "perfectly ok" but I had that bad key thing before, and read the rebooting into TWRP fixes the "issue". It's true, it works. I have N/A now and not "bad key".
Related
Followed these instuctions:
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/
My phone is now stuck at the google logo and will not go past. After rooting and clockwork i was not able to load anything else but i would not boot.
Please help.. Thank You
seriously? there is like 4 threads on how to root it, and you go with one that you shouldnt.. lol
it had pictures.. lol
all the threads on here talk about specific phone models and i wasnt sure so i just went with it... Bad choice on my part..
hopefully someone can help
load up fastboot and try to get to recovery if you can then awesome.. try wiping everything and see if that fixes anything
Pull the battery, hold volume up and power and follow this post to get into recovery. Then like shabby penguin said, when you get into recovery wipe everything and you should be good to go. Again, the post I linked you to is the proper way to root the 4g...
http://forum.xda-developers.com/showpost.php?p=13570498&postcount=5
i can get into recovery and i wiped the phone, but still doesnt help.
opie2l said:
i can get into recovery and i wiped the phone, but still doesnt help.
Click to expand...
Click to collapse
Oh, guess I didnt catch that.
ok your best bet it to go into fastboot and flash the clockworkmod 3.0.2.4
did you do the oem unlock command?
yeah i did the oem unlock.
ok well assuming you followed the directions from this guy, then you have a diff bootimg on there i can toss a few files that may fix it, but no garuntees...
seriously tho
(You should see that “LOCK STATE” says “UNLOCKED”, meaning your Nexus S is rooted.)
Click to expand...
Click to collapse
is posted on his site.. that would be a good indicator to me to stop listening to anything he said.. he then later in the comments was trying to help someone and told them if usb wasnt working then use a microsd adapter to put the files on..
yeah i am kicking my self in the a$$. Is there anyway do just get it back to stock?
well have you tried flashing a kernel? if it gets to bootani then its usually rom erros, freezing at spalsh screens is generally kernel images
is it possible to load a kernel when i cant see the phones memory from the computer???
someone has to have some idea of to fix this...
just got me to stock unrooted phone.. please
yes, download this
boot into fastboot and type in fastboot flash boot /path/to/natarchy.img
replace /path/to with where its located.. this should get you rollin again
thank you... thank you... thank you!!!!!!!!
i have learned my lesson and i wont stray from the xda forum next time.
Again thank you
I have a similiar issue as OP...I tried to flash netarchy kernel with kernal manager and then phone rebooted and got stuck at google logo.
I have installed SDK...google drivers, but when I try to flash the kernel I get waiting for device in command prompt. Same error when I type "fastboot oem unlock"
Any ideas?
Skillz1318 said:
I have a similiar issue as OP...I tried to flash netarchy kernel with kernal manager and then phone rebooted and got stuck at google logo.
I have installed SDK...google drivers, but when I try to flash the kernel I get waiting for device in command prompt. Same error when I type "fastboot oem unlock"
Any ideas?
Click to expand...
Click to collapse
Waiting for device means Windows does not recognize phone. Reinstall drivers.
ok sounds like a driver issue, i used pdanet to install the drivers i needed. try fastboot devices, if it doesnt show anything then your phone isnt connected
Ok used my mac and was able to get cwm recovery on device. I could mount it. Now how can I flash back to stock. I9020A att 3G version. Booting now I see google and a lock.
Thanks everyone!
I installed deodexed 4.2.2 stock when i was running deodexed 4.2.1 stock. i felt that it was buggy, so i went into cwrecovery and wiped it and i was about to begin reinstalling deodexed 4.2.2 again when i noticed i forgot to put it onto my phone. then i tried to use my phone, and it would be stuck at "unfortunately, system ui has stopped". it never leaves that popup, so i can't enable usb debugging. i can't use recovery mode, because when i do, the android with a triangle caution sign is there, but no options to select from. i can enter fastboot mode, but that's about it.
CM9onmyMoPho said:
I installed deodexed 4.2.2 stock when i was running deodexed 4.2.1 stock. i felt that it was buggy, so i went into cwrecovery and wiped it and i was about to begin reinstalling deodexed 4.2.2 again when i noticed i forgot to put it onto my phone. then i tried to use my phone, and it would be stuck at "unfortunately, system ui has stopped". it never leaves that popup, so i can't enable usb debugging. i can't use recovery mode, because when i do, the android with a triangle caution sign is there, but no options to select from. i can enter fastboot mode, but that's about it.
Click to expand...
Click to collapse
Reflash a factory image in fastboot, flash CWM/TWRP in fastboot, reroot and reflash the dedexed rom. Your phone isn`t even a bit bricked fortunately.
gee2012 said:
Reflash a factory image in fastboot, flash CWM/TWRP in fastboot, reroot and reflash the dedexed rom. Your phone isn`t even a bit bricked fortunately.
Click to expand...
Click to collapse
How can I reflash the factory image? and where can i find instructions? where can i find the link to download the factory image? thanks
CM9onmyMoPho said:
How can I reflash the factory image? and where can i find instructions? where can i find the link to download the factory image? thanks
Click to expand...
Click to collapse
Look in my signature line 2 and 3.
gee2012 said:
Look in my signature line 2 and 3.
Click to expand...
Click to collapse
thanks. will i lose any personal things such as photos?
CM9onmyMoPho said:
thanks. will i lose any personal things such as photos?
Click to expand...
Click to collapse
Everything will be lost. Considering your phone is bricked there is no way to pull the pictures from your device.
Edit: you might not have to flash full stock, just the system.img that will allow you to overwrite the current system and maintain your sdcard.
i do not know if this is the best place to post this considering i am brand new (i hope so) but i have a soft bricked nexus s 4g that i am trying to fix.
it was loaded with the helly bean 4.2.2 custom rom from nexus hacks (sorry no links) after the reboot it went to a black screen.
what ive tried:
odin: flashing a new rom, this resulted in odin not finding the device (usb debugging is not on and i cant turn it on)
fastboot: (i have all the files but i cant seem to get it set up, i type in adb or fastboot (no device recognized)
nexus root toolkit: (wouldnt find the device and found no options to help with usb debugging)
dfs: (couldnt read the device)
plugging in the phone to the computer: it makes the noise that it is plugged in, comes up as f drive but it is greyed out and i cant click on it (says insert disc)
clock work recovery: i did a full data wipe and required wipes cache and delvik or something along those lines: it reboots into the rom and nothing has changed.. my guess is because there is no back up of the original rom and the cfw is trash, it just wipes the bad rom back to factory and that is still a problem.
pda net: wont recognize the device
galaxy nexus toolkit: nothing useful since the usb debugging is not enabled.
ive worked for 6 hours as of last night to figure this out. i have spent most of those hours in forums and delving further into this phone then id imagined (its not mine) so if there is anyone out there that can suggest anything id appreciate it. this has got me stumped and amazed how such easy fix can really be this complicated.. i will thank any and all answers given to me
theblackrose666 said:
i do not know if this is the best place to post this considering i am brand new (i hope so) but i have a soft bricked nexus s 4g that i am trying to fix.
it was loaded with the helly bean 4.2.2 custom rom from nexus hacks (sorry no links) after the reboot it went to a black screen.
what ive tried:
odin: flashing a new rom, this resulted in odin not finding the device (usb debugging is not on and i cant turn it on)
fastboot: (i have all the files but i cant seem to get it set up, i type in adb or fastboot (no device recognized)
nexus root toolkit: (wouldnt find the device and found no options to help with usb debugging)
dfs: (couldnt read the device)
plugging in the phone to the computer: it makes the noise that it is plugged in, comes up as f drive but it is greyed out and i cant click on it (says insert disc)
clock work recovery: i did a full data wipe and required wipes cache and delvik or something along those lines: it reboots into the rom and nothing has changed.. my guess is because there is no back up of the original rom and the cfw is trash, it just wipes the bad rom back to factory and that is still a problem.
pda net: wont recognize the device
galaxy nexus toolkit: nothing useful since the usb debugging is not enabled.
ive worked for 6 hours as of last night to figure this out. i have spent most of those hours in forums and delving further into this phone then id imagined (its not mine) so if there is anyone out there that can suggest anything id appreciate it. this has got me stumped and amazed how such easy fix can really be this complicated.. i will thank any and all answers given to me
Click to expand...
Click to collapse
You need to be in the bootloader for fastboot to work. Reboot to bootloader and try flashing a recovery.img using this command.
fasboot flash recovery recovery.img
It blows my mind when a user gets all this great help and hasn't given any thanks to the helpers.
Sent from my iPad 4
mitchdickson said:
It blows my mind when a user gets all this great help and hasn't given any thanks to the helpers.
Sent from my iPad 4
Click to expand...
Click to collapse
Happens all the time. I'd have 1000 extra thanks if people new how to use the button or were remotely grateful.
estallings15 said:
Happens all the time. I'd have 1000 extra thanks if people new how to use the button or were remotely grateful.
Click to expand...
Click to collapse
i am sorry i was getting sdk tools set up watching an online tut. i am very greatful for your help my problem was that i had not installed java. so if anyone finds that sdk tools is not coming up. install java and it will work like it is supposed to. i will give a thank you just like i have promised. you guys on this site are the best techs hands down
---------- Post added at 05:13 PM ---------- Previous post was at 05:05 PM ----------
is there a thread on here about adb shell and pushing a new rom onto a nexus s 4g? basically the commands?
theblackrose666 said:
i am sorry i was getting sdk tools set up watching an online tut. i am very greatful for your help my problem was that i had not installed java. so if anyone finds that sdk tools is not coming up. install java and it will work like it is supposed to. i will give a thank you just like i have promised. you guys on this site are the best techs hands down
---------- Post added at 05:13 PM ---------- Previous post was at 05:05 PM ----------
is there a thread on here about adb shell and pushing a new rom onto a nexus s 4g? basically the commands?
Click to expand...
Click to collapse
adb push nameofrom.zip /sdcard/
Sent from my Nexus 4 using xda premium
ran sdk tools tried adb shell and nothing it wont read the device. we tried to push the .tar files to the phone using samsung galaxy nexus tool kit. it didnt work so hes going to take it to a repair but i think the device is toast on the account that usb debugging mode is no where in sight. if it does get fixed ill be sure to report how it got fixed. so anyone else who runs into the problem can get this fixed without a 20 dollar repair bill.
heat361 said:
Everything will be lost. Considering your phone is bricked there is no way to pull the pictures from your device.
Edit: you might not have to flash full stock, just the system.img that will allow you to overwrite the current system and maintain your sdcard.
Click to expand...
Click to collapse
will my computer even detect my phone? usb debugging is off and i can't see the phone's storage from my pc.
Hello my fellow XDA Members. I am stuck in a tight spot and after reading and re-reading some things the situation doesn't look very promising. I hope this is the moment that Karma shows up and I can get some help on this. Here it goes.
Specs - LG G2 D801 Variant > TWRP V2.8.3.1 > NO OS Currently
I was running Cloudy G3 Rom smoothly and got bored and decided to flash that new rom that is a 5.0 Rom all variants. Did the usual back ups and flashed it. Something happened when I flashed the rom. It went through the Aroma installer and then said "successful" but stuck in a bootloop. I tried it again and nothing happened. Then I tried to wipe everything again and started getting an E: Cannot mount (data or system I forget which as that error went away after I completely formatted data, wiped everything and reflashed Cloudy Stock. )
> Cloudy stock bootlooped and nothing is happening in TWRP. I Am using the USB OTG method of getting files on the phone and getting it charged but anytime I try to do anything (flash a rom, an older version of TWRP) it just immediately restarts TWRP and thats that. I have No OS at all.
> I tried to use one of the methods to get into download mode and flash a stock KDZ but the phone acts like it is going into DL mode (shows the little blue transition screen) but never gets into the ACTUAL download mode where the PC or flash tool can recognize it.
So in a nutshell > No OS > I can get into TWRP but it does nothing > No Download Mode > Don't want a new phone > Don't want to take it apart and try to short circuit anything if possible. LOL.
I am totally stuck here. I am done alot of work and even helped friends and family out with their devices over the years. I am just not sure if I need to consider it a done deal and get a new phone or maybe one of you guys know of something easy and obvious (please let it be the latter) I am missing. Thanks for any help you can offer. I Will be standing by.
Have you tried to reflash bootloader? If not, do that and reflash cloudy right away
wisefreakz said:
Have you tried to reflash bootloader? If not, do that and reflash cloudy right away
Click to expand...
Click to collapse
I haven't thought about flashing a bootloader. How would I flash the bootloader if I can not the phone into either DL mode and or TWRP doesn't do anything either? Is a bootloader file just a flashable file like any other .zip file?
jcnbama said:
I haven't thought about flashing a bootloader. How would I flash the bootloader if I can not the phone into either DL mode and or TWRP doesn't do anything either? Is a bootloader file just a flashable file like any other .zip file?
Click to expand...
Click to collapse
@jcnbama
Have you tried this or this?
euphoria360 said:
@jcnbama
Have you tried this or this?
Click to expand...
Click to collapse
The first one I can not do as I do not have any knowledge at all of Ubuntu, Linux, or any of that. It would take forever to get a working knowledge of that software in order to get things going again. I would probably just have to either take it to a cellphone repair shop or get another phone before I could do the first link.
I have not tried the second one but it is a viable option. I was looking at it online and trying to talk myself down from having to do that. I would reallllllllly rather not have to take my phone apart if I can keep from so that's kind of what this post is all about. Just trying to see if anyone knows of ANYTHING else before I go taking apart my phone.
Can you describe more about "twrp doesnt do anything"?
Does twrp boot up?
Can u see/wipe partitions?
Can u install any rom in twrp? Does it finish?
euphoria360 said:
Can you describe more about "twrp doesnt do anything"?
Does twrp boot up?
Can u see/wipe partitions?
Can u install any rom in twrp? Does it finish?
Click to expand...
Click to collapse
TWRP boots and I can go into wipe, advanced wipe, and format data and it says it's successful. I can use file manager and move items back and forth from USB OTG. If I try to flash anything it just reboots TWRP immediately so I can't install any .zip files at all.
My guess is that your bootloader is damaged.
The only option i can see for you is that Ubuntu thing i shared with you. So, lets stop acting lazy and do what needs to be done. Dont scare since there is nothing to loose. LG G2 is unbrikable
Booting up ubuntu or any other linux os is so easy. And there is nothing much to learn. Trust me.
Go to ubuntu website and download their newest iso file. Burn it on dvd and boot it up. You dont have to install it, just choose "live mode" and it boots up. Just like that. Then yiu can proceed with tutorial mentioned above and it shouldnt take more than an hour from you. Its all typing some commands in terminal (remember CMD in windows!).
Just make sure to download the files mentioned in that tutorial before proceeding.
euphoria360 said:
My guess is that your bootloader is damaged.
The only option i can see for you is that Ubuntu thing i shared with you. So, lets stop acting lazy and do what needs to be done. Dont scare since there is nothing to loose. LG G2 is unbrikable
Booting up ubuntu or any other linux os is so easy. And there is nothing much to learn. Trust me.
Go to ubuntu website and download their newest iso file. Burn it on dvd and boot it up. You dont have to install it, just choose "live mode" and it boots up. Just like that. Then yiu can proceed with tutorial mentioned above and it shouldnt take more than an hour from you. Its all typing some commands in terminal (remember CMD in windows!).
Just make sure to download the files mentioned in that tutorial before proceeding.
Click to expand...
Click to collapse
First of all calling people lazy is not nice. I'm not lazy I am trying to play it safe. I wouldn't want to brick it to the point to where I don't even have recovery and it can not even be charged any longer. I have Ubuntu on my desktop upstairs. I have used it a little. It's not that I am completely ignorant to Ubuntu I am just a total novice. Also the issue described in that post doesn't exactly match my situation. I am not in a black screen. It's more like a bootloop that I can not get out of because TWRP is not doing what it needs to do and I can not flash TWRP a ROM or get into DL mode at all. Also that post says,
"VERY IMPORTANT!!!!!!! You must use the img files that correspond to the ROM you have installed before getting the problem to avoid breaking your phone."
I don't have a rom on my phone soooo...
You didn't answer my question well. If on TWRP you can finish installing rom without any error, and you keep coming to twrp after restarts, that's another situation. Try this:
http://forum.xda-developers.com/showthread.php?t=2451696
But if you cant even finish install in twrp (twrp gives you errors or just restarts before giving you "successful", either you have problem in rom you try to flash or you need to build everything up from start.
That lazy thing was for encouraging you to do it.
And you cant brick your device. There is always a way on G2.
For img files: find them from last stock rom that was working on your phone.
Deleted
Could someone please offer some advice, i really am stumped on this one. I have a nexus 4 which is rooted has an unlocked bootloader and is running on the stock version of kitkat. Last week i changed network and as bizarre as it sounds when i got disconnected from three my phone bricked and got stuck on the boot logo.
Since then i went home and got the skipsoft toolkit up and running to essentially put a fresh rom on. Unfortunately no luck, i have gone into the bootloader and recovery,factory/wipe reset -- still no luck it's stuck on the boot logo. Now i realised that adb isn't working only fastboot which has also limited my options. i have tried multiple version of roms/recoverys etc.. they install which confirmed by the change of boot logo but that's it just hangs again.
Is there something else i can try? I would really appreciate some direction on it. Thanks very much in advanced.
airrunner said:
Could someone please offer some advice, i really am stumped on this one. I have a nexus 4 which is rooted has an unlocked bootloader and is running on the stock version of kitkat. Last week i changed network and as bizarre as it sounds when i got disconnected from three my phone bricked and got stuck on the boot logo.
Since then i went home and got the skipsoft toolkit up and running to essentially put a fresh rom on. Unfortunately no luck, i have gone into the bootloader and recovery,factory/wipe reset -- still no luck it's stuck on the boot logo. Now i realised that adb isn't working only fastboot which has also limited my options. i have tried multiple version of roms/recoverys etc.. they install which confirmed by the change of boot logo but that's it just hangs again.
Is there something else i can try? I would really appreciate some direction on it. Thanks very much in advanced.
Click to expand...
Click to collapse
What do you mean you changed network? What recovery are you using twrp or cwm hope it's twrp I think you need to search forums for wugfresh tool kit and start fresh which means going back to stock rom, recovery etc.. Wugfresh toolkit is the easiest method for you and even has videos on YouTube for step by step instructions you can't go wrong be patient and pay attention and you will be OK..www.wugfresh.com/youtube
---------- Post added at 09:58 PM ---------- Previous post was at 09:56 PM ----------
WelfareBaby said:
What do you mean you changed network? What recovery are you using twrp or cwm hope it's twrp I think you need to search forums for wugfresh tool kit and start fresh which means going back to stock rom, recovery etc.. Wugfresh toolkit is the easiest method for you and even has videos on YouTube for step by step instructions you can't go wrong be patient and pay attention and you will be OK..www.wugfresh.com/
Click to expand...
Click to collapse
[/COLOR]
WelfareBaby said:
What do you mean you changed network? What recovery are you using twrp or cwm hope it's twrp I think you need to search forums for wugfresh tool kit and start fresh which means going back to stock rom, recovery etc.. Wugfresh toolkit is the easiest method for you and even has videos on YouTube for step by step instructions you can't go wrong be patient and pay attention and you will be OK
Click to expand...
Click to collapse
I meant literally that i changed network from three to ee, which i also brought my original number over with it. The day my number transfered to ee my phone bricked and it's been stuck on boot loop since.
I have never used wugfresh before but i followed your instructions and spent sometime with it this morning. It's a very simple piece of software and i must admit i was feeling hopeful it might have fixed my boot-loop issue, but it hasn't. I have done factorywipes/wiped cache, flashed multiple version roms. As far as recovery i had TWRP running on my device, but for some reason i am no longer able to go into it only the bootloader. When i do click on recovery i got the android on its back with the exclamation mark, which obviously gives me the wipe options which i have done.
If there is anything else you can think of i would be greatly appreciative.
airrunner said:
[/COLOR]
I meant literally that i changed network from three to ee, which i also brought my original number over with it. The day my number transfered to ee my phone bricked and it's been stuck on boot loop since.
I have never used wugfresh before but i followed your instructions and spent sometime with it this morning. It's a very simple piece of software and i must admit i was feeling hopeful it might have fixed my boot-loop issue, but it hasn't. I have done factorywipes/wiped cache, flashed multiple version roms. As far as recovery i had TWRP running on my device, but for some reason i am no longer able to go into it only the bootloader. When i do click on recovery i got the android on its back with the exclamation mark, which obviously gives me the wipe options which i have done.
If there is anything else you can think of i would be greatly appreciative.
Click to expand...
Click to collapse
.
I really have no clue what changing network to ee is did you not create a backup if so you could restore it but since you can't once you get in bootloader and scroll to recovery you get dead android use to toolkit I told you and flash stock+unroot option it should work
---------- Post added at 12:57 AM ---------- Previous post was at 12:56 AM ----------
WelfareBaby said:
.
I really have no clue what changing network to ee is did you not create a backup if so you could restore it but since you can't once you get in bootloader and scroll to recovery you get dead android use to toolkit I told you and flash stock+unroot option it should work
Click to expand...
Click to collapse
If not pm me try to help you figure it out
I am very grateful you taking the time to help me with the boot issue. But i have actually just managed to sort it, finally!
It came down to me changing to an older radio version for 4.4.4., then i installed a 4.3 rom which it worked! I then upgraded to 5.01 and hey presto it's back to normal.
Thanks again nexus root tool-kit is definitely an essential
airrunner said:
I am very grateful you taking the time to help me with the boot issue. But i have actually just managed to sort it, finally!
It came down to me changing to an older radio version for 4.4.4., then i installed a 4.3 rom which it worked! I then upgraded to 5.01 and hey presto it's back to normal.
Thanks again nexus root tool-kit is definitely an essential
Click to expand...
Click to collapse
Your welcome glad I could help we all been in some situation before since you back up and running don't forget to make a backup of current rom always good idea to have that handy in case.. Cheers...
Hi, guys.
Today, my OP5 decided to troll me. I was using normally him, when suddenly it started to lags pretty bad. I restarted and he continued to lags and freeze. I made a wipe cache via stock recovery (i didnt made any change at all in it, no unlocked bootloader, no root). That's when my nightmare begins. It begins to bootloop. Sometimes i was able to start the boot animation, but then it just restarts to the beginning. I tried a lot of tips, wiping cache, system, etc. Then, i left it charging. When i tried to turn on again, it worked like nothing ever happened to him. I made a backup of my personal data fast, scared to him suddenly restart again. After that, i decided to made a Factory Reset, clean up everything. When i did it, he started the lag and freezes again. I was at lost. That's was when i decided to use the official unbrick tool, to make the cleanest OP5 ever possible. I grabbed the archives from this link and followed this tutorial. When i was executing the programa, in the userdate.img, he showed a error. When i saw it, i just stopped and closed the program. Now, my OP5 is hardbricked. The only sign of life that i get from him is when i connect him at the PC. I can identify it as qualcoom 9008, but when i try to run the program, he just fail and show me error 258.
Plz, i need some orientations. I have been read things for about 10 hours and didnt found a solution. I live abroad for any oneplus tech center, and i believe, for the other posts that i read, that online tech support wouldn't help me a lot. I really don't like to make this kind of post but i am kind of desesperate. I dont have money to afford another phone
Again, sry to disturb you all. Sry if i broke some rule of the forum too. And sry for my bad english, i hope that i was able to communicate right.
EDIT: I just tried in another computer. Same error appears. :'(
Hummm why follow a Unbrick Topic with tools for ...3T ?
Maybe you have a encryption problem, all your Tools/Topic are so old for the actual versions (Oreo 8.X OOS / 8.1 OOS)
I advise to you (in the first time), to flash this TWRP (using fastboot, very simple) just follow this guide : here
If you can flash TWRP, your phone is not bricked, you will boot in TWRP:
- Format Data > tape "yes" > Reboot in TWRP
- Copy/Past xXx 10.0 ROM to test, install and xXx Rom will fix/install for you the best OOS Custom ROM for your OP5 with a great Aroma Installer.
If TWRP with this rom work perfectly, you wil able to restore a official stock OOS for sure, just flash original/stock recovery (fastboot), wipe all data/partitions, install your OOS rom and it's fine
I think @cidsantiago says they bootloader isn't unlocked.
He needs to know that unlock the bootloader implies lost all /sdcard data and also installed apps and settings) before start the TWRP install process...
Pho3nX said:
Hummm why follow a Unbrick Topic with tools for ...3T ?
Maybe you have a encryption problem, all your Tools/Topic are so old for the actual versions (Oreo 8.X OOS / 8.1 OOS)
I advise to you (in the first time), to flash this TWRP (using fastboot, very simple) just follow this guide : here
If you can flash TWRP, your phone is not bricked, you will boot in TWRP:
- Format Data > tape "yes" > Reboot in TWRP
- Copy/Past xXx 10.0 ROM to test, install and xXx Rom will fix/install for you the best OOS Custom ROM for your OP5 with a great Aroma Installer.
If TWRP with this rom work perfectly, you wil able to restore a official stock OOS for sure, just flash original/stock recovery (fastboot), wipe all data/partitions, install your OOS rom and it's fine
Click to expand...
Click to collapse
Pho3nX said:
Hummm why follow a Unbrick Topic with tools for ...3T ?
Click to expand...
Click to collapse
I used the tools for 5. Just the procedure that i get from this topic. :T I am gonna try the method that you gave me now brb.
EDIT: Just tried this. My cellphone cant be recognized in fastboot devices. As a said, i am not getting any response for him, just when i plug it in the PC. So i wasn't able to unlock bootload or anything like that. I tried just to plug it and see if fastboot was able to identifying it, but it wasn't.
bartito said:
I think @cidsantiago says they bootloader isn't unlocked.
He needs to know that unlock the bootloader implies lost all /sdcard data and also installed apps and settings) before start the TWRP install process...
Click to expand...
Click to collapse
Yes, it should not be unlocked. But at the moment, i am taking anything, really. I just want to use my phone.
cidsantiago said:
Yes, it should not be unlocked. But at the moment, i am taking anything, really. I just want to use my phone.
Click to expand...
Click to collapse
Wipe your device data from the stock recovery.
You loss the settings and downloaded apps but not requires to unlock the bootloader.
bartito said:
Wipe your device data from the stock recovery.
You loss the settings and downloaded apps but not requires to unlock the bootloader.
Click to expand...
Click to collapse
I can't access recovery anymore, as i said. The only sign of life that i get is when i connect it in the PC.
I guess i have to do something to restore the basics partitions of my cellphone. Like recovery, boot, etc. But i just have the official tool to do that. There is another way? Like transfering directly by the COM port?
Have you tried following this guide? https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------
I had the same exact problem with my old One plus One. Spent like 4 days trying to unbrick it. That msm tool did the fix for me. Also, in that link to the guide you provided, doesn't it flash the Chinese version of the OS? If that's the case, I don't think it was a good idea to do so lol
Mash1ro said:
Have you tried following this guide? https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------
I had the same exact problem with my old One plus One. Spent like 4 days trying to unbrick it. That msm tool did the fix for me. Also, in that link to the guide you provided, doesn't it flash the Chinese version of the OS? If that's the case, I don't think it was a good idea to do so lol
Click to expand...
Click to collapse
In one of the links, it had the OOS and the HOS. I tried to use the msm tool in one of them, but it didnt worked I'm gonna try the archives in this link that you gave me. It may work brb with updates.
Don't worry though, it happens to plenty of people. It happened to me as well, and everyone eventually fixes it. It is unlikely that it is a hardware problem, so just following the correct steps should get it working. Keep trying stuff out, it's very good that your computer recognizes it as a qualcomm port, as far as I know that's all you need to flash the necessary things in order for it to boot.
I am getting the same error 258 in this post. :T I posted there to see if the OP can help me. But thx for your help @Mash1ro
Mash1ro said:
Don't worry though, it happens to plenty of people. It happened to me as well, and everyone eventually fixes it. It is unlikely that it is a hardware problem, so just following the correct steps should get it working. Keep trying stuff out, it's very good that your computer recognizes it as a qualcomm port, as far as I know that's all you need to flash the necessary things in order for it to boot.
Click to expand...
Click to collapse
Thx for your support! I will continue to try stuff
Try reading the comments from this post as well https://forum.xda-developers.com/oneplus-3t/help/hard-bricked-op3t-t3574720/page2
2 of the people had the same error as you, and one of them solved the issue by changing the USB port.
---------- Post added at 02:26 PM ---------- Previous post was at 02:23 PM ----------
But don't use the same files and all that stuff, since that's for the 3T. Try to pick out the things that might help but use the files for the OnePlus 5 only
After try the unbrick procedure in 3 different PCs, using about 10 different USB ports, i still getting the same error in the same step. When downloading cache.img, he stuck in about mid bar, and shows me the warning: SendProgramCommand Failed, Error: 258". Besides that, he turns on the green led and stop being recognize by the PC. Then i have to hold power and turn off the green led. :T Maybe i can use a linux to access the partitions?
cidsantiago said:
After try the unbrick procedure in 3 different PCs, using about 10 different USB ports, i still getting the same error in the same step. When downloading cache.img, he stuck in about mid bar, and shows me the warning: SendProgramCommand Failed, Error: 258". Besides that, he turns on the green led and stop being recognize by the PC. Then i have to hold power and turn off the green led. :T Maybe i can use a linux to access the partitions?
Click to expand...
Click to collapse
it seems like a hardware problem, i was facing this on different phone ( 5X )
Apayah said:
it seems like a hardware problem, i was facing this on different phone ( 5X )
Click to expand...
Click to collapse
yeah... But it is kind of weird. He was running smoothly, until suddenly started lag and freeze. He didn't fall or any of that... I think is just a defective phone. Doesn't find another explanation to that.
I think your best option is to RMA the device through OnePlus. Since you haven't rooted it or anything, they should repair it for you.
david19au said:
I think your best option is to RMA the device through OnePlus. Since you haven't rooted it or anything, they should repair it for you.
Click to expand...
Click to collapse
I already contact the store that i bought to get my warranty. Unfortunately, i didn't bought it in oneplus.net, bcs they don't deliver in my country. I am hoping that everything work out
Guys, in the end, i RMA my device back to the seller and gonna have a refund Thank you for your help. So sad that this phone came faulty :T
Best regards to you all!