Hello,
First of all, Thanks for this great community. It has been helping me with my S4 for a long time.
Almost a year ago, I bought a fire phone for my younger brother. Today I tried to install the Custom Rom CM11 (which I successfully did), but, among the files in the proper thread, are 2 more files, the Google apps and also, a "flash wipe out". I did this in the end, expecting that just cleaned everything without touching the OS. Huge and novice mistake from miself. After almost 5 hours of looking for a solution, I realized that I don't have an OS and can only enter to "Fire phone recovery mode". I have downloaded almost 5 or 6 stock firmwares that are available to donwload here in XDA. Tried to download the OTA for an unlocked phone from amazon and tried to upload it to the phone via ABD tools. In the end, I always get the same errors: Not-signed and can't install it in the phone.
I'm going to be honest: I'm desperate.
In conlcusion:
1) No OS in a fire phone.
2) No custom TWRP.
3) I just have recovery mode
4) Been trying to install through ADB tools without any success the stock OTA update (the last one, since I had the 4.6.6 version)
Anything that can help will be well received.
Thanks in advance
Hello,
Have you tried ADB sideload when you go into your phone's recovery? And if you did, what did it say when you tried installing it? Try using this to sideload your phone.
Thanks for your answer @mechasnyper but I have tried that out as well
Hey, thanks for the answer. I really appreciate the time for doing it.
Yes, I have tried the ADB Sideload. The phone it's identified through the CMD (I get to see the serial) and then try the ADB Sideload. It doesn't work with bin files. It says unable to load. I tried also with the zip files that are posted here in the forums, being able to load then at 100% but the cell phone says "invalid signature", and for this couldn't install it over the fire phone.
lordofra said:
Hey, thanks for the answer. I really appreciate the time for doing it.
Yes, I have tried the ADB Sideload. The phone it's identified through the CMD (I get to see the serial) and then try the ADB Sideload. It doesn't work with bin files. It says unable to load. I tried also with the zip files that are posted here in the forums, being able to load then at 100% but the cell phone says "invalid signature", and for this couldn't install it over the fire phone.
Click to expand...
Click to collapse
Try sideloading using this file. https://www.androidfilehost.com/?fid=24052804347783512 I found this somewhere else and this is the file I used when I screwed up my ROM installation.
When I get home I'll try using that file that you have posted.
I'll update the results.
lordofra said:
When I get home I'll try using that file that you have posted.
I'll update the results.
Click to expand...
Click to collapse
Success?
Sorry for the delay. Been talking with centurylink because since yesterday I have no Internet service (Answering from the phone). No, no success at all.
lordofra said:
It says unable to load.
Click to expand...
Click to collapse
Your need free RAM on computer bigger than .bin size.
Hey, thanks for the answer.
I'm doing it on my laptop that has 8 Gb of ram. Just in case, I'm going to try it on my brother's laptop that has 16 gb of ram to test this out. But I doubt this will make a difference, since I've tried already many .bin files (all of them are unable to load an their size its 1.2 GB max. Many zip files as well where I have obtained 100% load but the firephone aborts the installation due to signature verification failure.
This is really strange. I have screwed up installing Cyanogenmod onto my phone, yet I was able to revert back to the stock ROM with just the stock recovery. I will have to look more into this. I will post again soon for updates. Have you wiped the data and cache?
EDIT: I am not sure if this will work, but try using this bin file. http://androidhost.org/o120v
@lordofra
Try (with quotes)
adb sideload "full_path_and_name_of_the_bin.bin"
Related
hey everyone,
I normally don't post on here because I find the info without needing to, but I can't find this even with google fu, any help appreciated
Problem: Wifi won't turn on
ROMs tried: Orignal Kindle ROM, CM 9 (hashcode make), CM 9 (Energy mod ICS)
Other notes: My methods worked on my other KFs, but not this one.... however its an older version. I was sure to make everything factory default, wipes the two caches, and out of frustration from TeamWin deleted everything on the flash and system (except TeamWin Obviously). I have the Android SDK setup to interface with the device, so if you need me to hit it from there let me know. Everything else works, but a wifi only tablet without wifi is useless in my book.
Thanks once again for any help I will go back to google fu'n and head to wall bashing
Well can you mount your sdcard in twrp? If so transfer this to your sdcard http://forum.xda-developers.com/showthread.php?t=1439916 wipe everything except your external storage and flash it. Maybe this will help isolate whether this is a hardware issue.
hmm
Thepooch said:
Well can you mount your sdcard in twrp? If so transfer this to your sdcard http://forum.xda-developers.com/showthread.php?t=1439916 wipe everything except your external storage and flash it. Maybe this will help isolate whether this is a hardware issue.
Click to expand...
Click to collapse
Thanks for the quick reply, will give this one a shot and hopefully it works
Edit/update:
I can mount the device in TWRP, however it will not mount when I boot the ROM. Also adb is apparently not running on the device? Did these commands:
adb kill-server
adb device
and device not listed.
update
initialhit said:
Thanks for the quick reply, will give this one a shot and hopefully it works
Edit/update:
I can mount the device in TWRP, however it will not mount when I boot the ROM. Also adb is apparently not running on the device? Did these commands:
adb kill-server
adb device
and device not listed.
Click to expand...
Click to collapse
update: got a terminal emulator on the device while I waited for the download (I already had the apk). One thing peculiar is it cant find wlan0... which I can on my other one. Also usb is still a no go unless from TeamWin. Still waiting on the ROM.
final update
initialhit said:
update: got a terminal emulator on the device while I waited for the download (I already had the apk). One thing peculiar is it cant find wlan0... which I can on my other one. Also usb is still a no go unless from TeamWin. Still waiting on the ROM.
Click to expand...
Click to collapse
ROM flashed to device, kept having Google android process fail and restart causing major pains... so I couldnt even check the wifi. Using the Kindle Fire Utility I reflashed Gapps and rebooted, it locked up, so I wiped the caches and whatnots and put the ROM in Factory reset mode from TWRP. It looks like for sure the wifi NIC is fried... going to have to just send it back and have them send me another one... one final thing is I am downloading the latest factory ROM for this device and flashing it with it to see if that works, and if not then the people I am sending back to wont know the wiser lol. Thanks for giving ideas nonetheless yall!
initialhit said:
ROM flashed to device, kept having Google android process fail and restart causing major pains... so I couldnt even check the wifi. Using the Kindle Fire Utility I reflashed Gapps and rebooted, it locked up, so I wiped the caches and whatnots and put the ROM in Factory reset mode from TWRP. It looks like for sure the wifi NIC is fried... going to have to just send it back and have them send me another one... one final thing is I am downloading the latest factory ROM for this device and flashing it with it to see if that works, and if not then the people I am sending back to wont know the wiser lol. Thanks for giving ideas nonetheless yall!
Click to expand...
Click to collapse
Did the factory ROM flash correct the issue or still a no-go for WiFi?
Hey guyz.. i solve the issue!..
if your system version is lower the the the latest version:
just download the update img in amazon kindle. using PC. then copy to kinlde directory..and after updating the wifi works..
if latest version:
downgrade the kindle using KFHD_SRT_v1.2.3.zip and a fastboot cable.
then apply the above process.
kibusaki said:
Hey guyz.. i solve the issue!..
if your system version is lower the the the latest version:
just download the update img in amazon kindle. using PC. then copy to kinlde directory..and after updating the wifi works..
if latest version:
downgrade the kindle using KFHD_SRT_v1.2.3.zip and a fastboot cable.
then apply the above process.
Click to expand...
Click to collapse
Wrong device. Wrong forum.
Hi,
First off, my ouya is bricked, i get tot hte ouya "!" screen, thats it.
So after going from zero knowledge to actually got ADB to work and being able to adb roms to the ouya, im finally stuck.
When i try to install a OTA update rom (.zip file) after ADB over, it stops and says the version number is to low compared to the version on the ouya. does anybody have a room that can be ADB over and after that i can just do a factory reset? Any help is appreciated!
I´ve tried some other stockplus roms etc, but it just starts installing then it says canceled. what am i missing?
Is there any rom out there that can be adb over?!
T
There is some chance of flashing a sbf via PC?
Sent from my MB526 using Tapatalk 2
DiegoxG said:
There is some chance of flashing a sbf via PC?
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
Dont know how to choose location on the ouya, i know how to ADB stuff, (belive me it took 2days of hairpulling to figure that one out).
The problam is that i was in superuser with a fileexplorer i had edit a document and after that i was going to put the "read only" status back on the ouya systemfiles. But accidently unclicked read, so the ouya now just boots in to ouya"!" cause it cant read the system files. Does anyone have a system dump that i can flash? or can i flash a system dump just to get in the system and then do a system update / recovery?
Whould the abominable snowman update work if someone hade the ota rom for that? Since its a lter version than what i got i mean?
Q&A for [RECOVERY] CWM Recovery 6.0.5.1.2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Full backup of one AFTV and restore on another
It's great to see that modstore was able to clone an AFTV.
I dont understand what modstore is saying here:
modstore said:
I'm not sure if anyone has tried backing up one Fire TV and restoring to another, but I just tried it, and all seems good.
Doing the restore though, changed the registered account to that of the backup. So I'm not sure if it would have been registered properly, probably not. But I changed it to the account I wanted it registered too, and all seems good now.
Click to expand...
Click to collapse
Changed what registered account? Does this mean that the new AFTV was setup to have the same amazon account as the backed up AFTV before the restore took place on the new AFTV?
I really want to be able to clone. It sounds like its possible, I just want to avoid the trial and error if possible. I'm sure others are interested in the procedure too.
eville84 said:
It's great to see that modstore was able to clone an AFTV.
I dont understand what modstore is saying here:
Changed what registered account? Does this mean that the new AFTV was setup to have the same amazon account as the backed up AFTV before the restore took place on the new AFTV?
I really want to be able to clone. It sounds like its possible, I just want to avoid the trial and error if possible. I'm sure others are interested in the procedure too.
Click to expand...
Click to collapse
Yes, from what he said that the registration info went over with the backup. If you want to clone machines, then this will work.
he didn't want to clone machines, so he had to put in the correct register info on the machine he put the backup on.
nyder said:
Yes, from what he said that the registration info went over with the backup. If you want to clone machines, then this will work.
he didn't want to clone machines, so he had to put in the correct register info on the machine he put the backup on.
Click to expand...
Click to collapse
There might be a way to make it trigger the initial Registration page after doing a restore of a clone. I'll add it to my list and maybe come up with a special update.zip that will make it happen.
So if you have a FTV set up with xbmc etc you can make a direct copy of it into a stock FTV, thus cloning it as said above?
I've looked around and can't seem to find what to do. I've used adb before but have never ran into this issue yet seems so silly.
When I type "su" in adb shell i get this error "system/bin/sh: su: not found"
I've googled and all I can find is reinstalling the superuser on the phone... I'm trying to unlock the boot loader
hellot1M said:
I've looked around and can't seem to find what to do. I've used adb before but have never ran into this issue yet seems so silly.
When I type "su" in adb shell i get this error "system/bin/sh: su: not found"
I've googled and all I can find is reinstalling the superuser on the phone... I'm trying to unlock the boot loader
Click to expand...
Click to collapse
You need root first. What fw are you on? If it's a rootable version, do that first and then follow the guides for updating here.
Yea figured it out. I'm on 1.3.0 this sucks. I'm trying to sell my amazon box to get a nexus player. Amazon has no idea how to run a home media center.
Thanks!
Bricked mine. Cant boot into recovery anymore using keyboard. Any tips ?
Sent from my SM-N910V using Tapatalk
patt2k said:
Bricked mine. Cant boot into recovery anymore using keyboard. Any tips ?
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
What guide, and which step of said guide, were you running through that you bricked it?
Sent from my TARDIS
0p3nsrc said:
What guide, and which step of said guide, were you running through that you bricked it?
Sent from my TARDIS
Click to expand...
Click to collapse
Guide from AFTVNEWS.
I got recovery to work everything was fine I could reboot from recovery back to recovery again (CWM) but after I did factory reset in CWM it gets stuck on amazon logo.
The reason I did factory reset was because of Error.7 in CWM I had that few times when flashing different roms on different phones/tablets
sometimes getting older cwm or simply factory reset would help.
So now it gets stuck on Amazon logo the keyboard trick to get back into CWM does not work anymore.
Anything else I can try before I call up amazon hoping they replace it ?
I can honestly say if you followed rbox's custom recovery install guide, used his recovery image, and made sure the md5 matched, you shouldn't have had any problems.
Out of curiosity, do you have an external hard drive plugged in?
Sent from my TARDIS
0p3nsrc said:
I can honestly say if you followed rbox's custom recovery install guide, used his recovery image, and made sure the md5 matched, you shouldn't have had any problems.
Out of curiosity, do you have an external hard drive plugged in?
Sent from my TARDIS
Click to expand...
Click to collapse
Yea I did follow instructions correctly. And no I do not only had the usb keyboard plugged in so I could get into recovery.
Almost every device I rooted w/ custom recovery gave me Error 7 tablets phone etc.. I seem to have bad luck with that error lol.
Since I was on the very last step.. flashing rom -> getting error 7 grr
patt2k said:
Yea I did follow instructions correctly. And no I do not only had the usb keyboard plugged in so I could get into recovery.
Almost every device I rooted w/ custom recovery gave me Error 7 tablets phone etc.. I seem to have bad luck with that error lol.
Since I was on the very last step.. flashing rom -> getting error 7 grr
Click to expand...
Click to collapse
I think cwm still has some issues. It works fine for installing rbox's pre-rooted ROMs, but I can't backup my ftv. It always errors out.
Was this the first time you've gone through cwm install? Did you try installing one of his custom ROMs and then got that error? Did you verify that your recovery download went okay? Check the md5 against what's listed on the site.
I know it's a lot of questions, but I'm just trying to delve deeper to see what may have caused your error.
(I'm tech support, so I've always got more questions to ask )
Sent from my TARDIS
0p3nsrc said:
I think cwm still has some issues. It works fine for installing rbox's pre-rooted ROMs, but I can't backup my ftv. It always errors out.
Was this the first time you've gone through cwm install? Did you try installing one of his custom ROMs and then got that error? Did you verify that your recovery download went okay? Check the md5 against what's listed on the site.
I know it's a lot of questions, but I'm just trying to delve deeper to see what may have caused your error.
(I'm tech support, so I've always got more questions to ask )
Sent from my TARDIS
Click to expand...
Click to collapse
Yes sir everything was checked few times. Bunch of times made sure even file size is correct etc...
I did install recovery however at first when I had wrong firmware I installed via ADB SHELL then I Downgraded to unlock bootloader after I downgraded I installed recovery via adbfire I think newest version .17 however it was still the newest firmware of recovery anyway.... and yepp it was stock pre-rooted latest firmware that ends with "0" that did not require the fire tv boot menu.. but now I am thinking if I had the boot menu I could have got into recovery! so AFTVNEWS mis-lead me on this part... the bootmenu would be great on all firmwares actually.
patt2k said:
Yes sir everything was checked few times. Bunch of times made sure even file size is correct etc...
I did install recovery however at first when I had wrong firmware I installed via ADB SHELL then I Downgraded to unlock bootloader after I downgraded I installed recovery via adbfire I think newest version .17 however it was still the newest firmware of recovery anyway.... and yepp it was stock pre-rooted latest firmware that ends with "0" that did not require the fire tv boot menu.. but now I am thinking if I had the boot menu I could have got into recovery! so AFTVNEWS mis-lead me on this part... the bootmenu would be great on all firmwares actually.
Click to expand...
Click to collapse
I'm not sure about adbfire anything. I do all mine through Linux/android terminal/windows command line. The boot menu works on firmware 51.1.4.0. When it's sitting at the logo, have you tried connecting via adb, just to see if it initialized enough to poke around? (not sure if it works that way with ftv, but I'd try, regardless)
Sent from my TARDIS
0p3nsrc said:
I'm not sure about adbfire anything. I do all mine through Linux/android terminal/windows command line. The boot menu works on firmware 51.1.4.0. When it's sitting at the logo, have you tried connecting via adb, just to see if it initialized enough to poke around? (not sure if it works that way with ftv, but I'd try, regardless)
Sent from my TARDIS
Click to expand...
Click to collapse
As far as I saw I could only connect via adb at least when in recovery mode.. otherwise it was a no go... anyways thanks for helping me out. I think there is no rescue in this situation by somehow fixing it. I mean just wanted to have few features like swap storage with a flash drive and have newest FW. But that's ok.
Thanks for your time!
patt2k said:
As far as I saw I could only connect via adb at least when in recovery mode.. otherwise it was a no go... anyways thanks for helping me out. I think there is no rescue in this situation by somehow fixing it. I mean just wanted to have few features like swap storage with a flash drive and have newest FW. But that's ok.
Thanks for your time!
Click to expand...
Click to collapse
Sorry I couldn't be of more help :/ the issue you'll probably see is that unlocking the bootloader voids any warranty with amazon.. So I'm not sure what amazon may or may not do for you.
Sent from my TARDIS
About the possible Lollipop ROM for FireTV,is there a way to get the latest qualcomm Adreno 320 drivers like [email protected] from another device for flashing in proper FTV directories since it is meant for Lollipop?
I am hoping for the fix for Dolphin to be runnable and Reicast to no longer cause reboots,as well as better performance for things like Mupen64Plus AE.
Long story short - Bought an LG D851 off Swappe. It came with CM13. I've been sticking nightlies on it. Currently on 2/14. I tried to put 2/18 and found that TWRP wasn't working - it hangs on TWRP Splace. Then I noticed SuperSU wasn't on the phone. So I installed it. Can't update the binaries. Looks like I don't have root.
Used LG Flash tool and flashed D85120E_00.kdz. Part way through, I get an error that the software cannot communicate with the server and it asks if I want to abort. I let it continue.
The phone reboots, I get the "Android is updating 1/196", etc. After which, it reboots, I get the boot jingle, and then it holds on the T-Mobile screen. I've tried flashing the KDZ a few times with the same result.
So now, I humbly, yet again, ask for help.
The endgoal here, is to have a working ROM with BT and WiFi working. I really don't care what it is at this point. Marshmallow is nice. Lollipop is okay. Whatever. I just need a working phone.
Thanks in advance, as always.
mdphoenix said:
Long story short - Bought an LG D851 off Swappe. It came with CM13. I've been sticking nightlies on it. Currently on 2/14. I tried to put 2/18 and found that TWRP wasn't working - it hangs on TWRP Splace. Then I noticed SuperSU wasn't on the phone. So I installed it. Can't update the binaries. Looks like I don't have root.
Used LG Flash tool and flashed D85120E_00.kdz. Part way through, I get an error that the software cannot communicate with the server and it asks if I want to abort. I let it continue.
The phone reboots, I get the "Android is updating 1/196", etc. After which, it reboots, I get the boot jingle, and then it holds on the T-Mobile screen. I've tried flashing the KDZ a few times with the same result.
So now, I humbly, yet again, ask for help.
The endgoal here, is to have a working ROM with BT and WiFi working. I really don't care what it is at this point. Marshmallow is nice. Lollipop is okay. Whatever. I just need a working phone.
Thanks in advance, as always.
Click to expand...
Click to collapse
Ouch!!! Read my CM13 post...you don't need SuperSU anymore (CM13 has root built in)--I had the same problem a while back--fixed it by flashing the old factory version on the phone & then used Purple Drake to root it & then installed CM13...Was a HARD lesson for me.
Upshot---No SuperSU needed--No BusyBox needed on CM13. If you are used to the old way of doing things--you'll get B0rked big time.
Luck to you!!!!
debianmain1 said:
Ouch!!! Read my CM13 post...you don't need SuperSU anymore (CM13 has root built in)--I had the same problem a while back--fixed it by flashing the old factory version on the phone & then used Purple Drake to root it & then installed CM13...Was a HARD lesson for me.
Upshot---No SuperSU needed--No BusyBox needed on CM13. If you are used to the old way of doing things--you'll get B0rked big time.
Luck to you!!!!
Click to expand...
Click to collapse
I guess trying to push the SuperSU binaries is what effed up TWRP?
I'll check out your CM13 post. But the issue I have is that I can't flash a factory version with LG Flash Utility. I mean, it does, but now it just sits on the Tmobile splash.
Hopefully your post will show me something I missing.
@debianmain1 is this the post you're talking about? http://forum.xda-developers.com/showpost.php?p=65432245&postcount=158
I tried that DD command to no avail last night. I tried everything I could find before reaching out to everyone for help.
mdphoenix said:
I guess trying to push the SuperSU binaries is what effed up TWRP?
I'll check out your CM13 post. But the issue I have is that I can't flash a factory version with LG Flash Utility. I mean, it does, but now it just sits on the Tmobile splash.
Hopefully your post will show me something I missing.
@debianmain1 is this the post you're talking about? http://forum.xda-developers.com/showpost.php?p=65432245&postcount=158
I tried that DD command to no avail last night. I tried everything I could find before reaching out to everyone for help.
Click to expand...
Click to collapse
Yes--the SuperSU binaries B0rked my install real good ( as I understand it--2 different types of SU installed B0rks everything )..... And with CM13, you have to allow ADB & apps to have root. I've been modding phones for years now & CM13 threw me under the bus until I learned what to do... I use to ALWAYS root, install BusyBox & SuperSU---not with CM13
Ya--that won't help you I'd look up fastboot commands & try to flash it that way--sounds like you are stuck in a startup bootloop. I did see some info online about starting the G3 in fastboot--I had a very hard time getting my G3 fixed. Do you have a Linux computer to use? It's easier to work with some of the diag stuff with Linux.
debianmain1 said:
Yes--the SuperSU binaries B0rked my install real good ( as I understand it--2 different types of SU installed B0rks everything )..... And with CM13, you have to allow ADB & apps to have root. I've been modding phones for years now & CM13 threw me under the bus until I learned what to do... I use to ALWAYS root, install BusyBox & SuperSU---not with CM13
Ya--that won't help you I'd look up fastboot commands & try to flash it that way--sounds like you are stuck in a startup bootloop. I did see some info online about starting the G3 in fastboot--I had a very hard time getting my G3 fixed. Do you have a Linux computer to use? It's easier to work with some of the diag stuff with Linux.
Click to expand...
Click to collapse
I can always fire up an Ubuntu flash drive if necessary. I'll get working on Fastboot.
Thanks again!
@debianmain1 Hmmm, Fastboot doesn't seem to be functional. I've got download mode. Can I push something to it that way?
I managed to get somewhere yesterday. I tried flashing D85120e_00.kdz and it failed again. I got the "cannot communicate with server" error, then it rebooted and tried running initial setup and failed.
So I tried flashing D85110C_00.kdz. Much to my surprise, it worked! So I ran through initial setup and got the phone working to make sure all was well. I rebooted and got the Red 2. So now here I am. Guides show that I should be able to put it in download mode and reload factory firmware again. But all I get is the "Download Mode" graphic. It never switches over to the updating mode with the circular arrows. I fear the worst at this point, but I really don't know enough about the LGs to diagnose my own doom just yet.
Someone on Reddit pointed me in the direction of Board Diag. Unfortunately it doesn't appear to work on D851. Running out of options. Looks like it'll end up being an expensive learning experience.
sooo I decided I want to go back to stock, I'm not as technically inclined as I use to be and just want a normal phone I can just easily to updates on .
Currently TWRP - I tried to sideload the .zip but adb says cannot read file (I have tried both 32bit adb and 64bit adb) doesn't seem to effect it any.
I cannot find my files in TWRP so trying to load them from there doesn't work either..... I have put the 2 files the oem stock and the recovery img on my phone but internal storage says 0mb. I was able to manipulate it to finally come up and read info off the internal storage but the files are still not there, yet when I bring up my phone on the computer the files are both there.
can anyone please help me im frustrated and have spent hours trying to fix this and im hitting brick walls......
avs286 said:
sooo I decided I want to go back to stock, I'm not as technically inclined as I use to be and just want a normal phone I can just easily to updates on .
Currently TWRP - I tried to sideload the .zip but adb says cannot read file (I have tried both 32bit adb and 64bit adb) doesn't seem to effect it any.
I cannot find my files in TWRP so trying to load them from there doesn't work either..... I have put the 2 files the oem stock and the recovery img on my phone but internal storage says 0mb. I was able to manipulate it to finally come up and read info off the internal storage but the files are still not there, yet when I bring up my phone on the computer the files are both there.
can anyone please help me im frustrated and have spent hours trying to fix this and im hitting brick walls......
Click to expand...
Click to collapse
Have you tried using the unbrick tools? They are made specifically to return your phone to stock, though it gets wiped in the process
preference said:
Have you tried using the unbrick tools? They are made specifically to return your phone to stock, though it gets wiped in the process
Click to expand...
Click to collapse
i have not tried them I didn't even think to try that...… ill go look for them I appreciate the suggestion!
preference said:
Have you tried using the unbrick tools? They are made specifically to return your phone to stock, though it gets wiped in the process
Click to expand...
Click to collapse
Thank you for this suggestion! it worked for me I was able to get it completely stock again. cant believe I missed such an easy step:good::good::good::good::good::good::good::good::good::good::good: