i want help from some1 experienced to help me unbricking my phone
collisiion said:
i want help from some1 experienced to help me unbricking my phone
Click to expand...
Click to collapse
What happened what model pro 3 do you have.
Sent from my LEX727 using xda premium
mchlbenner said:
What happened what model pro 3 do you have.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
my phone only vibrates i cant turn it on, i have x720 model
collisiion said:
my phone only vibrates i cant turn it on, i have x720 model
Click to expand...
Click to collapse
Do you have fastboot working?
What is the last thing you flashed?
Sent from my LEX727 using xda premium
mchlbenner said:
Do you have fastboot working?
What is the last thing you flashed?
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
do u think you can help me? it is better to speak in teamspeak or something
If all you can access is fastboot, then check this guide out: https://forum.xda-developers.com/le-pro3/how-to/guide-unbrick-le-pro3-tested-t3622340
Your device has a QFIL file you can use to resurrect it. Also, provide us with information, like what you were doing before you bricked your device, and so on. Can't help you without knowing your basic situation.
sk8223 said:
If all you can access is fastboot, then check this guide out: https://forum.xda-developers.com/le-pro3/how-to/guide-unbrick-le-pro3-tested-t3622340
Your device has a QFIL file you can use to resurrect it. Also, provide us with information, like what you were doing before you bricked your device, and so on. Can't help you without knowing your basic situation.
Click to expand...
Click to collapse
i had a MIUI rom from a chinese forum for a few days and it was very stable and fluid, but when the battery ran out my phone shut down and I cant turn it on anymore. i tried to charge it for a few hours and it didnt turn on. only vibrates. I tried qfil unbrick method. it said success but i still cant turn it on, only vibrates.. my pc recognizes the phone but i dont know what do do.
collisiion said:
i had a MIUI rom from a chinese forum for a few days and it was very stable and fluid, but when the battery ran out my phone shut down and I cant turn it on anymore. i tried to charge it for a few hours and it didnt turn on. only vibrates. I tried qfil unbrick method. it said success but i still cant turn it on, only vibrates.. my pc recognizes the phone but i dont know what do do.
Click to expand...
Click to collapse
Well, you should have mentioned the situation in your first post. Sounds like a hardware issue. Never ever ever let a lithium-ion battery, like those in smartphones, drop to less than 5%. Never let them run out to less than 1% either. That's a surefire way to destroy a battery.
Plug your phone in using a certified USB-C cable (NOT the original LeEco cable that came with your phone) and wait a couple of days. It may begin charging after a while. But since you let the battery deplete to 0%, you might have to replace it.
sk8223 said:
Well, you should have mentioned the situation in your first post. Sounds like a hardware issue. Never ever ever let a lithium-ion battery, like those in smartphones, drop to less than 5%. Never let them run out to less than 1% either. That's a surefire way to destroy a battery.
Plug your phone in using a certified USB-C cable (NOT the original LeEco cable that came with your phone) and wait a couple of days. It may begin charging after a while. But since you let the battery deplete to 0%, you might have to replace it.
Click to expand...
Click to collapse
really? i didnt know that. is it possible to replace a battery on this phones? do you think i can still revive it?
collisiion said:
really? i didnt know that. is it possible to replace a battery on this phones? do you think i can still revive it?
Click to expand...
Click to collapse
Yeah, it should be pretty easy. Before doing that, look through this sub-forum for similar issues. A couple people here had the same issue--they let their battery drain to zero and wanted to revive their phones. I don't know if they managed to or not.
Just look for a Pro3 disassembly guide on Google. It's not hard. The Pro3's interior is similar to other LeEco phones, like the Le 2.
And Google is your friend. Google your issues instead of immediately making a thread here or wherever. This is a common issue on Android.
sk8223 said:
Yeah, it should be pretty easy. Before doing that, look through this sub-forum for similar issues. A couple people here had the same issue--they let their battery drain to zero and wanted to revive their phones. I don't know if they managed to or not.
Just look for a Pro3 disassembly guide on Google. It's not hard. The Pro3's interior is similar to other LeEco phones, like the Le 2.
And Google is your friend. Google your issues instead of immediately making a thread here or wherever. This is a common issue on Android.
Click to expand...
Click to collapse
i didnt know man, im sorry.. i thought it was really dead. thanks for your help
Can you get your phone into fastboot?
Let your phone for 5 hours then push down power button and connect to USB.
Never let your battery go under 15% especially a pro 3.
Your not first to have this problem and posting this issue is alright!
Sent from my LEX727 using xda premium
mchlbenner said:
Can you get your phone into fastboot?
Let your phone for 5 hours then push down power button and connect to USB.
Never let your battery go under 15% especially a pro 3.
Your not first to have this problem and posting this issue is alright!
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
thanks man i thought it was something worse than this, im going to investigate
collisiion said:
thanks man i thought it was something worse than this, im going to investigate
Click to expand...
Click to collapse
Let us know how you fix it, so other people that has same issue can read this, ok ?
Sweden.33 said:
Let us know how you fix it, so other people that has same issue can read this, ok ?
Click to expand...
Click to collapse
ok no problem
collisiion said:
thanks man i thought it was something worse than this, im going to investigate
Click to expand...
Click to collapse
You battery is not necessarily dead, you phone is just hard bricked, the symptoms you are having is exactly what happened to a friends phone and we were able to revive it. Just following the steps in the unbrick guide. https://forum.xda-developers.com/le-pro3/how-to/guide-unbrick-le-pro3-tested-t3622340 If you check the last post you will see that someone just recently unbricked their phone.
Worst case there are services for repairing a bricked phone:
I have attached my notes below: The information came from multiple post by various people and my own research combined. Its unedited, I had planned on posting a more polished guide. So I am just copy pasting what I have so far. But the methods listed definitely works unless you do in fact have a hardware issue.
This Thread dedicated to unbricking The Leeco variants X720 and X727
These instructions may not work if you flashed with wrong firmware and you are stuck in Qualcomm Mode 9008.
* I plan to create a post that will share these thorough instructions with the public.
* After spending over an hour typing all of this out for you. I found this video that you can use a companion tutorial to walk your through the steps visually. https://www.youtube.com/watch?v=iN9Ce3hKlRA
* While there are s a couple of differences. For example, The person in the video is flashing a different phone.Most of the steps are the same.
https://forum.xda-developers.com/le-pro3/how-to/guide-unbrick-le-pro3-tested-t3622340
1. Download Flash 2( Tool) here: https://mega.nz/#!ex5nmQxB!qXLIg3wpeQwuiTShdOz_DEStXFiKUPfSoXNLjomn4ag
2. Download the Qfil file for Lex Pro 3 file here: https://mega.nz/#!BJ52CApB!8lFCesula...e=DonanimHaber
3. Make sure you place and run this file from the root of your PC I.E : C:/
4. Do not unzip, when selecting it needs to stay a zip file
5. Keep these files. In case you ever need them again and if it works for you.
Instructions
* QFIL mode: Press on vol+ and vol- simultaneously while holding power
* Alternate way to get into edit mode ( Press vol+ and vol- while plugging usb into pc. enter in edl mode.
* Then start flash one
* Advance option Get HSCT
* Flash Type: Flash dead phone
* To Flash Developer Rom: rename of rom to 1.zip
* After completing the flash press and hold the power-button down for 30+ seconds and the phone will vibrate
* Release the power-button, it will vibrate again after 10-20 seconds*
After you have performed all of the steps
* Your Le Pro 3 will have the temporary repair version of EUI.
* The phone may not boot automatically.
* Press and hold the Power Button for two minutes or longer.
* iIt will leave the QFIL Mode, and will vibrate continuously for 20 seconds or longer.
* The phone could take as long as 15 minutes to start.
* Immediately you will notice that part of your storage is missing.
*
* Restore the storage back to default by going to Backup/Restore in Settings and Factory Resetting the Phone with the "Format Virtual SD Card" Option selected.
* *Next install the latest Official EUI download EUI 21S ( do mot load anything above this)
* Rename the file to Update.zip and place on OTG drive or into phone storage using file manager.
* Go to check for update and click hamburger icon in top corner and select you Update.zip file to upgrade
* If it doesn’t work retry steps,, If you have an issue from here let me know, also let me know if it works.
Worst Case after restoration attempt to resolve size issue.
* if you still have a problem install Twrp and Flash via TWRP install.,
* Wipe EVERYTHING... and flash the ROM using a usb Flash Drive and after mounting USB OTG Storage.*
* To Flash TWRP simply shut down the phone and By Keeping the Volume Down Button Pressed Hit the Power Button to Enter the Fastboot Mode.*
* flash TWRP Recovery...
* Boot into TWRP Recovery...
* Restart TWRP Recovery... I
* insert the USB Flash Drive
* Using USB OTG Adapter... and flash the ROM using the Install Tab in TWRP Recovery.
Addendum:
As far as I know the X725, has the exact hardware requirements as the X720 and X727 and many parts suppliers list hardware components being compatible with all three devices.*
Have you tried removing and reinstalling Qualcomm drivers, turning off firewall and antivirus, reinstalling and rebooting? Sometimes the most basic steps are the solution.
Here is a link that might provide additional things to try:*http://www.androidbrick.com/unbrick-...usb_dload_edl/
Stock Rom and drivers can be found here:*https://devsjournal.com/download-let..._Pro_Stock_ROM
I will look around and see if I can help you find anything else that may be useful.
BTW, the X720 and X727 are pretty much the same phone so it doesn't matter, it can be easily fixed. At this most my X727 thinks its a X720 because I just flashed a newly released X720 test Rom.*
Here is a link to a Stock Rom that will not ask for a key and the drivers can be found here as well.*https://devsjournal.com/download-let..._Pro_Stock_ROM*( This should definitely work I know that several people have used this file recently with success)
I will look around and see if I can help you find anything else that may be useful.
_____________________________________________________________________________________
Addendum:
Re: Instructions for unbricking your phone
Okay so you were able to download the files but Windows is not recognizing the file. Okay, I read the message in the middle of being focused on something else and misunderstood,thinking that you couldn't download it.*
So It seems that Windows has damaged the file or Qfil installation.
1. Do you have more then one copy of the file? Here is an alternative copy:*https://androidfilehost.com/?w=files&flid=244213
2. You will need to uninstall and reinstall Qfil
If you are on Windows 10, you will need to turn off antivirus, and all the block-ware that Microsoft has installed within Defender which may delete files or neuter files that it doesn't like. Perhaps this is what happened to your Qfil installation? ( I have a new laptop and dealt with this issue recently attempting to install Viper Audio mods for PC) So unfortunately, you may also need to uninstall and reinstall Qfil, ensure that you install as admin.
Go through your settings and make sure under apps >>apps and features>> the dropdown box installing apps and turn off installing apps from store only.
Go to Apps & features in Settings.
Under “Installing apps,” there is a drop-down menu with three options: make sure “Allow apps from anywhere” is on.
Although the Qfil tool is used universally to repair all Qualcomm boards. Windows 10 may cause issue and disable functions that allow root level changes to your attached device. Yes, this will flag Windows Defender
Defender
* Open Windows Defender Security Center from your Start menu, desktop, or task-bar.
* Click on the App and browser control button on the left side of the window.
* Check Off in the Check apps and files section.
* Make sure that Defender and any other antivirus or malware blocker is turned off.
* Unfortunately, from now on you will always need to turn these things off if you are installing drivers or programs that did not come from Windows store.
* Make sure all defender settings are toggled off.
* Turn off the controlled folder access .
Worst case: Other potential ways to resolve
This sucks ( If you will never use it otherwise) but you may even need to enable developer mode
https://docs.microsoft.com/en-us/win...or-development
You can return everything back to normal after you unbrick your phone.
The link below explains how to resolve additional potential issues caused by the Microsoft OS,
https://flashfiletool.com/qualcomm-usb-driver-download*The full setup option, on this page will download all drivers ( download only if needed) for all supported phones.
Hopefully, this finally resolve it for you. I am keeping notes. So once this is resolved. We can provide some updated cohesive steps to help other people that have the same
Related
DISCLAIMER
Here goes the cyanogenmod disclaimer. The same applies here.
"CyanogenMod members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find here before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software."
1. Turn on usb debugging from developer settings.
2. Install drivers like this.
3. Download and install this.
4. Open and click Root(Make sure you're connected to the internet).
And...you're done!
To unroot press the remove root button in the same application.
A1000F USERS PLEASE READ
Some A1000F users have reported that the device will turn off after rooting and won't start until you plug in the charging cable. After that it works fine. Refer to the comments below. If your device fails to start after rooting, please try this.
Keep in mind Lenovo will have an absolute right to deny your warranty claim(you are of course free to try, they may not even notice) if you give them a rooted device. So make sure you unroot the device before taking it to the service center, unless the device is completely dead.
UPDATE
Lenovo has finally rolled out an update for A1000G that increases the internal storage to 1.5gb.
That worked for me thanks.
Thanks! Thanks! Thanks! Thanks!
rishabh22 said:
1. Turn on usb debugging from developer settings.
2. Install drivers like this.
3. Download and install this.
4. Open and click Root.
And...you're done!
Click to expand...
Click to collapse
Thank You Very Much Friend.....Thank You So Much.
It Works Great. Thank You Once Again
rishabh22 said:
1. Turn on usb debugging from developer settings.
2. Install drivers like this.
3. Download and install this.
4. Open and click Root.
And...you're done!
Click to expand...
Click to collapse
Worked like a charm :good: I successfully rooted my ideatab A1000. You are like god here
rishabh22 said:
DISCLAIMER
Here goes the cyanogenmod disclaimer. The same applies here.
"CyanogenMod members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find here before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software."
1. Turn on usb debugging from developer settings.
2. Install drivers like this.
3. Download and install this.
4. Open and click Root.
And...you're done!
You should also be able to unroot the device using the same application but i haven't tried it and it may or may not work.
Keep in mind Lenovo will have an absolute right to deny your warranty claim(you are of course free to try, they may not even notice) if you give them a rooted device. So make sure you unroot the device somehow before taking it to the service center, unless the device is completely dead.
Click to expand...
Click to collapse
It worked on my Lenovo A1000F.
Thank you very much :victory:
HELP!!!!!
I tried rooting my Lenovo A1000-F --- followed the instructions, installed PDANet and ran Kingo, which said the root was complete. When I clicked FINISH the screen on the tab went blank and now I can't get it to start.
Here's what I'm seeing after unplugging and plugging the USB back into the tab, which I hope isn't bricked.
Icersman said:
I tried rooting my Lenovo A1000-F --- followed the instructions, installed PDANet and ran Kingo, which said the root was complete. When I clicked FINISH the screen on the tab went blank and now I can't get it to start.
Here's what I'm seeing after unplugging and plugging the USB back into the tab, which I hope isn't bricked.
Click to expand...
Click to collapse
that wasn't supposed to happen. Did you have sufficient charge before rooting and are you sure your usb cable isn't damaged or anything?
Here's what you can try
1. Charge the device for around 1/2 hr and then try switching it on.
2. Restart your pc, make sure kingo root isn't started and then connect the usb
Otherwise try searching Google for such problems and as a last resort you can take the device to the service center and tell them this happened while you were trying to update or something. I would have tried to help you myself but Im busy with my exams for the next 20-25 days. Sorry
Do post what happens. I'll try to help as much as i can
rishabh22 said:
that wasn't supposed to happen. Did you have sufficient charge before rooting and are you sure your usb cable isn't damaged or anything?
Here's what you can try
1. Charge the device for around 1/2 hr and then try switching it on.
2. Restart your pc, make sure kingo root isn't started and then connect the usb
Otherwise try searching Google for such problems and as a last resort you can take the device to the service center and tell them this happened while you were trying to update or something. I would have tried to help you myself but Im busy with my exams for the next 20-25 days. Sorry
Do post what happens. I'll try to help as much as i can
Click to expand...
Click to collapse
same thing happened today to me aswell trying to figure out how to fix it by the way does the case behind open?
BLSbeerzerker said:
same thing happened today to me aswell trying to figure out how to fix it by the way does the case behind open?
Click to expand...
Click to collapse
haven't tried opening it yet. Take a look at this http://m.youtube.com/watch?v=oM6Ccqe97NY. Might help.
btw you also with a1000f?
rishabh22 said:
haven't tried opening it yet. Take a look at this http://m.youtube.com/watch?v=oM6Ccqe97NY. Might help.
btw you also with a1000f?
Click to expand...
Click to collapse
yeah i have a a1000f, after leaving it overnight without a plugged charger, plugging it in this morning booted up normally and rooted
rishabh22 said:
that wasn't supposed to happen. Did you have sufficient charge before rooting and are you sure your usb cable isn't damaged or anything?
Here's what you can try
1. Charge the device for around 1/2 hr and then try switching it on.
2. Restart your pc, make sure kingo root isn't started and then connect the usb
Otherwise try searching Google for such problems and as a last resort you can take the device to the service center and tell them this happened while you were trying to update or something. I would have tried to help you myself but Im busy with my exams for the next 20-25 days. Sorry
Do post what happens. I'll try to help as much as i can
Click to expand...
Click to collapse
Thanks for the info. I did the root procedure with close to a full battery and didn't think that was a problem. Plugged in the charger last night and it fired right up! I see SuperSU is on my list of apps, so I assume that it's rooted. :silly:
Plz HELP
I tried rooting as you said but the tablet is dead
please help me what to do!!!
dr_ams2008 said:
I tried rooting as you said but the tablet is dead
please help me what to do!!!
Click to expand...
Click to collapse
A1000g or A1000f?
rishabh22 said:
A1000g or A1000f?
Click to expand...
Click to collapse
A1000g as i think
forgive me i can`t remember but it is the updated with 1.5 internal storage
---------- Post added at 08:13 PM ---------- Previous post was at 07:59 PM ----------
rishabh22 said:
a1000g or a1000f?
Click to expand...
Click to collapse
please help me
dr_ams2008 said:
A1000g as i think
forgive me i can`t remember but it is the updated with 1.5 internal storage
---------- Post added at 08:13 PM ---------- Previous post was at 07:59 PM ----------
please help me
Click to expand...
Click to collapse
If the total internal storage is16gb it is f and if it is 4gb then g. Anyway some users have reported a problem initially but the tab comes back to life after plugging in the charger. Please read all the posts in this thread.
rishabh22 said:
If the total internal storage is16gb it is f and if it is 4gb then g. Anyway some users have reported a problem initially but the tab comes back to life after plugging in the charger. Please read all the posts in this thread.
Click to expand...
Click to collapse
Yes I`ve read the posts and left the tab on charger for nearly 2 hours but still nothing
I am sorry for bothering you but I `ve bought the tab only one week ago
You can imagine how I feel
dr_ams2008 said:
Yes I`ve read the posts and left the tab on charger for nearly 2 hours but still nothing
I am sorry for bothering you but I `ve bought the tab only one week ago
You can imagine how I feel
Click to expand...
Click to collapse
Yes i can completely understand and I'm really sorry i won't be help you much till the 29th at least. You will have to look around for a solution by yourself or take it to the service centre. Otherwise you will have to wait till the 29th and then maybe i can help figure it out
PS in my experience I've never really seen or heard of an android device being COMPLETELY dead. There is usually a way or another to revive it. So please don't give up on your hope even if you can't find a way
Thanks for nice info,1st try kingo just failed to connect.
2nd try with internet connected success,just want to make it clear.i managed to root by installed kingoapp and internet connection.it need sdk driver from phone offical site to successfully connect and root any phone listed.
bahar_b said:
Thanks for nice info,1st try kingo just failed to connect.
2nd try with internet connected success,just want to make it clear.i managed to root by installed kingoapp and internet connection.it need sdk driver from phone offical site to successfully connect and root any phone listed.
Click to expand...
Click to collapse
oh yes! I forgot to mention the net connectivity requirement.
And the model for which i've posted does not have any driver support from the OEM. That is why it requires the pdanet drivers.
And for those having a problem after rooting please take a look at this:
http://forums.lenovo.com/t5/Idea-An...OVO-A1000-ROM-RECOVERY-ETC/m-p/1307595#M26034
dr_ams2008 said:
Yes I`ve read the posts and left the tab on charger for nearly 2 hours but still nothing
I am sorry for bothering you but I `ve bought the tab only one week ago
You can imagine how I feel
Click to expand...
Click to collapse
Hi, i too was rooting the device with Kingo. The software showed that the root was successful but the tablet screen went off. I tried restarting but nothing happened. The tablet seemed to be on as my laptop showed USB device connected.
Then i rest the tablet by pressing the reset button using a pin.
Please search the instruction on how to reset the tablet if you dont know how to do it. I am unable to post any external link to show you that.
Hope this helps... Now i am trying to connect Pen Drives and 3G dongle to the tablet...
Bricked OP2 ...
Hi all
I bought the oneplus 2 4 days ago.
I rooted it, installed twrp and flashed nethunter2.0 CM12 then wiped cache , well the flash didn't go very successfully as the os still oxygen but i had all applications from nethunter installed and fully functional.
I decided to use the nethunter installer provided by the official site but not including the onplus2 version, i included the custom rom in replacement of the choosed one
.. but accidentally in the process of this tool it flashed stok for nexus which completely bricked the phone... nothing works, not boot no charge no sound...
I plugged again the phone and pressed for 20 seconds the power + volume up button and i got the bulk usb driver as it was a oneplus one .. i changed the driver settings to accept the unsigned drivers and updated the unkown device to the qualcomm 9008 ( as it was like a oneplus one ) .
The issue is that oneplus two has a Qualcomm MSM8994 Snapdragon 810 and the version i found for ColorOS is only for MSM8794 .. so i couldn't do anything
please can anyone help me?
any hint please?
Thank you in advance
If you flashed a ROM that's not for you're phone you're more than likely screwed
Could you try the following:
1, plug the phone back in recovery/fastboot mode
2, Open Computer Management and delete the drivers the OS finds for the phone
3, Download the ADB driver tool from here: http://forum.xda-developers.com/showthread.php?t=2588979
Try follow the steps and let me know if u get the drivers needed for the recovery
If the tool on the above link dont work, try this one: http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi
Bhups said:
Could you try the following:
1, plug the phone back in recovery/fastboot mode
2, Open Computer Management and delete the drivers the OS finds for the phone
3, Download the ADB driver tool from here: http://forum.xda-developers.com/showthread.php?t=2588979
Try follow the steps and let me know if u get the drivers needed for the recovery
If the tool on the above link dont work, try this one: http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi
Click to expand...
Click to collapse
Thank you for your response, the issue is that it's hard bricked, so no recovery mode no led , nothing ..
i uninstalled the drivers ( even that i had the adb working before ) and the device is detectable now only with as QHSUSB_BULK
the installation of any adb usb driver don't change anything, only qualcomm usb drivers work ( i have the 9008 only but i'm think it's not compatible with OP2) i could manually change it to adb ( mobistel Cynus f4 ADB interface ) but nothing new..
Help plz
thanks again
mG!X said:
Hi all
I bought the oneplus 2 4 days ago.
I rooted it, installed twrp and flashed nethunter2.0 CM12 then wiped cache , well the flash didn't go very successfully as the os still oxygen but i had all applications from nethunter installed and fully functional.
I decided to use the nethunter installer provided by the official site but not including the onplus2 version, i included the custom rom in replacement of the choosed one
.. but accidentally in the process of this tool it flashed stok for nexus which completely bricked the phone... nothing works, not boot no charge no sound...
I plugged again the phone and pressed for 20 seconds the power + volume up button and i got the bulk usb driver as it was a oneplus one .. i changed the driver settings to accept the unsigned drivers and updated the unkown device to the qualcomm 9008 ( as it was like a oneplus one ) .
The issue is that oneplus two has a Qualcomm MSM8994 Snapdragon 810 and the version i found for ColorOS is only for MSM8794 .. so i couldn't do anything
please can anyone help me?
any hint please?
Thank you in advance
Click to expand...
Click to collapse
Two problems here. The first problem is that you didn't wipe properly when flashing Nethunter, that's why you ended up with Nethunter apps on your stock ROM. When flashing a ROM you must perform a full wipe, this consists of system, data, cache, and dalvik cache. This isn't what bricked your phone though. We know what bricked your phone; flashing a ROM for a completely different device. I'm not sure why you would flash a ROM from another device, maybe due to inexperience, but that's the last thing you should be doing, as you now know. Don't use the recovery tool that you have, it isn't for your chipset, it will only make matters worse. I honestly don't think there's any way to revive your device, you've pretty much rendered it useless. I'd strongly suggest you do a lot of research before deciding to mess with another phone, if you don't know what you're doing then don't do it. Venturing into unknown lands like this only ever ends in disaster.
Heisenberg said:
Two problems here. The first problem is that you didn't wipe properly when flashing Nethunter, that's why you ended up with Nethunter apps on your stock ROM. When flashing a ROM you must perform a full wipe, this consists of system, data, cache, and dalvik cache. This isn't what bricked your phone though. We know what bricked your phone; flashing a ROM for a completely different device. I'm not sure why you would flash a ROM from another device, maybe due to inexperience, but that's the last thing you should be doing, as you now know. Don't use the recovery tool that you have, it isn't for your chipset, it will only make matters worse. I honestly don't think there's any way to revive your device, you've pretty much rendered it useless. I'd strongly suggest you do a lot of research before deciding to mess with another phone, if you don't know what you're doing then don't do it. Venturing into unknown lands like this only ever ends in disaster.
Click to expand...
Click to collapse
Thanks for your response.
I made a full wipe with Twrp ( as mentionned in your tutorial ) and al steps run without issues.
The issue is that the next day i used the nethunter install tool instead of manually installing, in the steps for one plus one ( not oneplus 2) i mentionned the specific rom which can run on the phone but suddenly when i pushed next it was flashing stock for nexus ( and yes it's in the steps of oneplus1 :/ i verified ) , well i know that it's inadmissible and can brick it seriously
now i have the bulkusb when linked to windows8 and pressing on poweron+volumeup, what do you recommend please? there is no compatible driver for snapdragon 810?flashing to colorOS won't solve the issue please?
Thanks in advance
mG!X said:
Thanks for your response.
I made a full wipe with Twrp ( as mentionned in your tutorial ) and al steps run without issues.
The issue is that the next day i used the nethunter install tool instead of manually installing, in the steps for one plus one ( not oneplus 2) i mentionned the specific rom which can run on the phone but suddenly when i pushed next it was flashing stock for nexus ( and yes it's in the steps of oneplus1 :/ i verified ) , well i know that it's inadmissible and can brick it seriously
now i have the bulkusb when linked to windows8 and pressing on poweron+volumeup, what do you recommend please? there is no compatible driver for snapdragon 810?flashing to colorOS won't solve the issue please?
Thanks in advance
Click to expand...
Click to collapse
Well flashing ColorOS using the tool you have will attempt to flash ColorOS for the OnePlus One, because that tool is not for your device. As I said, don't use it, it's not for your device so it will only do more harm. I don't know if there's a recovery tool for the Two yet, I certainly haven't seen one.
Heisenberg said:
Well flashing ColorOS using the tool you have will attempt to flash ColorOS for the OnePlus One, because that tool is not for your device. As I said, don't use it, it's not for your device so it will only do more harm. I don't know if there's a recovery tool for the Two yet, I certainly haven't seen one.
Click to expand...
Click to collapse
Ok, i will search maybe the drivers come out or someone find a solution, i ill contact support and seek their help also. Thanks and i will keep you updated if i find something
mG!X said:
Ok, i will search maybe the drivers come out or someone find a solution, i ill contact support and seek their help also. Thanks and i will keep you updated if i find something
Click to expand...
Click to collapse
I just can say, your device is not hard bricked and will be recoverable.
You just need to be a bit patient. For the OPO, there was the ColorOs emergency recovery available (which helped me already 2x unbricking my OPO after I compiled a faulty kernel).
I just have not yet seen something similar for the OP2. But as you get the bulk_device still recognized via USB, this means the Qualcomm emergency boot loader is still intact and once the recovery stuff leaks somewhere, you will be able to fully recover your OP2.
Don't ask me when this will be available, think it also took weeks for the OPO before it was posted somewhere.
All the best!
Andi
mG!X said:
Thank you for your response, the issue is that it's hard bricked, so no recovery mode no led , nothing ..
i uninstalled the drivers ( even that i had the adb working before ) and the device is detectable now only with as QHSUSB_BULK
the installation of any adb usb driver don't change anything, only qualcomm usb drivers work ( i have the 9008 only but i'm think it's not compatible with OP2) i could manually change it to adb ( mobistel Cynus f4 ADB interface ) but nothing new..
Help plz
thanks again
Click to expand...
Click to collapse
You can try this (but with oxygenos), but I'm not sure if it works with OP2 snapdragon 810
https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/
EDIT: It seems you will need fastboot image of oxygenos and list of partitions ... anyway, good luck
yanick76 said:
You can try this (but with oxygenos), but I'm not sure if it works with OP2 snapdragon 810
https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/
EDIT: It seems you will need fastboot image of oxygenos and list of partitions ... anyway, good luck
Click to expand...
Click to collapse
It probably isn't the smartest idea in the world to recommend using a recovery tool from for an entirely different device unless you're 100% sure it's safe, which it probably isn't.
Heisenberg said:
It probably isn't the smartest idea in the world to recommend using a recovery tool from for an entirely different device unless you're 100% sure it's safe, which it probably isn't.
Click to expand...
Click to collapse
It's Qualcomm tool, but sadly OP2 is new device and there are no guides specific to OP2. He probably can resurrect his phone using QHSUSB_BULK device(*1)
EDIT: (*1) - It depends on correct driver and firmware files (images)
yanick76 said:
It's Qualcomm tool, but sadly OP2 is new device and there are no guides specific to OP2. He probably can resurrect his phone using QHSUSB_BULK device(*1)
EDIT: (*1) - It depends on correct driver and firmware files (images)
Click to expand...
Click to collapse
Yes, I'm aware that there is nothing specific available for the OP2. My point is that you're not even sure if this isn't going to damage the device further, let alone even help in any way.
Heisenberg said:
Yes, I'm aware that there is nothing specific available for the OP2. My point is that you're not even sure if this isn't going to damage the device further, let alone even help in any way.
Click to expand...
Click to collapse
His device is almost dead and this kind of damage is not covered by warranty. I think in this situation is not much to lose
Just to assure you that the hard brick issue on OPT is completely curable since I've revived two OPTs. No panic needed. I will update the complete procedure as well as the necessary files later today.
yanick76 said:
His device is almost dead and this kind of damage is not covered by warranty. I think in this situation is not much to lose
Click to expand...
Click to collapse
His device is not almost dead, it's in a bricked "like" state right now but it can be easily fixed with the correct tool. What you're suggesting is not the correct tool for this device at all. If you're comfortable with being so reckless with someone else's device, good for you, I'm certainly not.
Heisenberg said:
His device is not almost dead, it's in a bricked "like" state right now but it can be easily fixed with the correct tool. What you're suggesting is not the correct tool for this device at all. If you're comfortable with being so reckless with someone else's device, good for you, I'm certainly not.
Click to expand...
Click to collapse
Yes I understand you but my post was meant as suggestion to way how to fix it, not guide. If you think my post can lead him to kill his device you can delete my post (because I can't), I have no problem with it
yanick76 said:
Yes I understand you but my post was meant as suggestion to way how to fix it, not guide. If you think my post can lead him to kill his device you can delete my post (because I can't), I have no problem with it
Click to expand...
Click to collapse
I know you were trying to help, but that advice is the wrong advice. I don't want/need to delete your post. My point here is to try to help you to understand why giving advice when you're not 100% understanding the situation properly isn't a great idea. On a site like this, accuracy and knowledge are paramount because it can be the difference between helping someone revive their device or completely killing it.
mG!X said:
Hi all
I bought the oneplus 2 4 days ago.
I rooted it, installed twrp and flashed nethunter2.0 CM12 then wiped cache , well the flash didn't go very successfully as the os still oxygen but i had all applications from nethunter installed and fully functional.
I decided to use the nethunter installer provided by the official site but not including the onplus2 version, i included the custom rom in replacement of the choosed one
.. but accidentally in the process of this tool it flashed stok for nexus which completely bricked the phone... nothing works, not boot no charge no sound...
I plugged again the phone and pressed for 20 seconds the power + volume up button and i got the bulk usb driver as it was a oneplus one .. i changed the driver settings to accept the unsigned drivers and updated the unkown device to the qualcomm 9008 ( as it was like a oneplus one ) .
The issue is that oneplus two has a Qualcomm MSM8994 Snapdragon 810 and the version i found for ColorOS is only for MSM8794 .. so i couldn't do anything
please can anyone help me?
any hint please?
Thank you in advance
Click to expand...
Click to collapse
Tutorial posted here http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Heisenberg said:
I know you were trying to help, but that advice is the wrong advice. I don't want/need to delete your post. My point here is to try to help you to understand why giving advice when you're not 100% understanding the situation properly isn't a great idea. On a site like this, accuracy and knowledge are paramount because it can be the difference between helping someone revive their device or completely killing it.
Click to expand...
Click to collapse
From this point I agree it was wrong advice.
I hope I never will be in situation like this But if, I will try to fix it based on what I suggest him + hours of google for correct files, correct drivers and correct download tool. I think this "misunderstood" was based on my advice like "here is direction and google for more", this is forum if he can find answer himself (google) he need not to ask for help here
Hello xda members, yes you heard right, OnePlus bricked my device, did you had a problem with the OnePlus support too?
Here's a sum up what happened:
> I buyed the one in january 2015
> batterylife on Cyanogen OS was terrible, so I switched like many other users to custom roms
> the batterylife was better, but not good not bad, normal
> many users are saying that Oxygen OS has amazing battery life
> so i searched and found out that there isn't an official flashable version, i found out that the support flash it by every user manually with a remote session
> so i contacted the support, made a meeting
> the support was nice, but then...
> 12pm (est) on monday 28.03.16
> the remote session started, there standed that it will get recorded on my windows vista pc(does anyone know where? i dont find it, but i have the chat between me and the tecnicer, see the attached file
> the technicer installed drivers and flashed afaik per adb, but it dont found my device, he did something with drivers and said i need to reboot my pc
> i did it
> still dont work
> my phone was ok
> so he used a chinese tool
> then he wrote he's very sorry and that my device has a hardware issue and that he will send me to their RMA/RRR(he wrote both, its afaik the devicechange support)
> I was sad looked to my phone: dead, hardbrick, idk how, he just hardbricked it, but ok its not full dead just hardbrick, its able to fix(i found athread on xda, but the problem is that my device got bricked by flashing oxygen OS, so I think I need to give my device to the support, they need to fix what they did)
>I was only sad, not angry, he did his best, so i waited for an email from the support
> I got one with my adress and they asked if its true
> it's #sotrue
> after 2 days i still didn't got an email, so i am now angry af
> many of you are thinking now 'just chill dude they are humans too and you are not the only one which need the device change support, but guys, you need to know that this guys which need the support to droped for example their device in water and want that 1+ fix it, but i didnt dropped it and didnt bricked it, so oneplus need to care about me, its their fault, but they still dont answered after 2 days, guys i need my device, they know that i am angry because they bricked my device, ok 12 hours before i get an answer is ok they are humans too, but not 2 damn days, they bricked my device, not I.
I dont wanna hate against oneplus, i just write this because i am very angry that THEY bricked my device and don't give a ****, that's not a good support!!
so please dont remove this thread admins, if something is not ok contact me i will edit it
Had you guys a problem with the support too? Write it and vote in the survey!
I'm sorry that you are unhappy with the phone.
I'm own of the same device since rough about the same date like you.
First of all I've install an own recovery menu (TRWin) and use uo from this time CM 5 / 5.1 and now 6.x
I couldn't say that I've the same problems like you. The battery life is independent of the OS and which apps are are used. At minimum the akku reached for 3 day's or more( look how much % does you display used).
In the case that I'll have your issue : boot into the recovery at make a wipe of = cache / Dalvik cache and data ( factory reset). After that reinstall your apps fresh from the market.
Also install Aps Ops to control the access of the apk's. If a Apk check every. 5 Min something of an update, the battery drains... thats normal.
Mad07 said:
I'm sorry that you are unhappy with the phone.
I'm own of the same device since rough about the same date like you.
First of all I've install an own recovery menu (TRWin) and use uo from this time CM 5 / 5.1 and now 6.x
I couldn't say that I've the same problems like you. The battery life is independent of the OS and which apps are are used. At minimum the akku reached for 3 day's or more( look how much % does you display used).
In the case that I'll have your issue : boot into the recovery at make a wipe of = cache / Dalvik cache and data ( factory reset). After that reinstall your apps fresh from the market.
Also install Aps Ops to control the access of the apk's. If a Apk check every. 5 Min something of an update, the battery drains... thats normal.
Click to expand...
Click to collapse
Sorry bro i already tried everything, bbs(there were gservice wakelocks which cant get killed, i installed other roms there were again other wakelocks and more), elixier 2, gsam, this what you said that if a app drains every 5 minutes and more, at least the batterylife was normal. At least only 3 hours on screen time. Thats the reason why i wanted to try out oxygen os.
In this moment I use the TRWin Recovery ( wipe Cache / Dalvik / Data) ; CM 13 ( Android 6.0) and Google Apk ( not the big one / Small or medium packages) for marshmallow.
I've ~ 170 Apps on the phone - without any issues ( ok, the batteryife was a little bit better with 5.0, but that's all ( here the compare is not 100%, because more Apps : but at the beginning the phone was running around 6-7 day's)
Does the PC see something, if you connect the Phone via USB?
If yes, you can bring it back to life
Mad07 said:
In this moment I use the TRWin Recovery ( wipe Cache / Dalvik / Data) ; CM 13 ( Android 6.0) and Google Apk ( not the big one / Small or medium packages) for marshmallow.
I've ~ 170 Apps on the phone - without any issues ( ok, the batteryife was a little bit better with 5.0, but that's all ( here the compare is not 100%, because more Apps : but at the beginning the phone was running around 6-7 day's)
Does the PC see something, if you connect the Phone via USB?
If yes, you can bring it back to life
Click to expand...
Click to collapse
Hi, yes, i already tested it, its a hardbrick and the pc detect it.
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
I am thinking about to fix it self, but then i wont have Oxygen OS because i think it will do again a full brick. But i need my phone on monday because i am then 3 weeks on a work placement and need my phone. :/
If your PC see an unknown Device, the phone is ot hardbricked. Its a hard Softbrick
If I remember right, you will find a link in the Oneplus forum for the needed driber. With this one, you can bring back your phone to life. A recovery menu is in a normal case enough.
( like Twrp (that's tbe right name )
https://www.androidfilehost.com/?fid=24399994186369589
Bacon is the pseudonym for the Oneplus one
---------- Post added at 02:16 AM ---------- Previous post was at 02:15 AM ----------
pls have a look to the description
http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136
Mad07 said:
If your PC see an unknown Device, the phone is ot hardbricked. Its a hard Softbrick
If I remember right, you will find a link in the Oneplus forum for the needed driber. With this one, you can bring back your phone to life. A recovery menu is in a normal case enough.
( like Twrp (that's tbe right name )
https://www.androidfilehost.com/?fid=24399994186369589
Bacon is the pseudonym for the Oneplus one
---------- Post added at 02:16 AM ---------- Previous post was at 02:15 AM ----------
pls have a look to the description
http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136
Click to expand...
Click to collapse
Thanks guy i think i'll unbrick it self
sorry for not helping and ur post had just made it clear we should know what we r doing with our phone eveyrtime.
If the pc can identify the phone in fastboot mode, then there is hope.
https://www.reddit.com/r/oneplus/comments/31sf0x/guide_how_to_return_from_oxygenos_to_stock_cm11s/
or follow the guide you linked to
kenboyles72 said:
If the pc can identify the phone in fastboot mode, then there is hope.
https://www.reddit.com/r/oneplus/comments/31sf0x/guide_how_to_return_from_oxygenos_to_stock_cm11s/
or follow the guide you linked to
Click to expand...
Click to collapse
bruh, its a hard softbrick, there's no fastboot.
PlayersHeaders said:
bruh, its a hard softbrick, there's no fastboot.
Click to expand...
Click to collapse
Brah, try this method. It's a ported tool for the OPO that I used to restored my OPT when I was about to use it as a paperweight LOL.
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Also have a look to the post #40 on the same thread
http://forum.xda-developers.com/showpost.php?p=58074662&postcount=40
Hope this helps!
Hellfireworks said:
Brah, try this method. It's a ported tool for the OPO that I used to restored my OPT when I was about to use it as a paperweight LOL.
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Also have a look to the post #40 on the same thread
http://forum.xda-developers.com/showpost.php?p=58074662&postcount=40
Hope this helps!
Click to expand...
Click to collapse
Is it for the problem what i have? I have no fastboot, boot, recovery, is this tool for bricks which I have?
PlayersHeaders said:
Is it for the problem what i have? I have no fastboot, boot, recovery, is this tool for bricks which I have?
Click to expand...
Click to collapse
Yep, if you connect the OPO to a PC is it recognized something like "Qualcomm device"? If it is, this tool is for you. Once you have the tool opened and the phone connected to the PC, press Volume up + Power, the phone should vibrate and then it should appear under Device Manager. Here's additional information of this process, found on the OPT thread:
qwsdert4 said:
First step, turn off drive signature enforcement in windows 8/8.1/10. Tutorial Here
Second step, hold the power key for 20 seconds to force turn off power. connect OPT to usb, hold volume+ and power until your PC finds a new hardware (if it doesn't work, try hold volume+ and volume- together)
Third step, go to device manager in your PC, find the new "QUALCOMM-HS USB Diagnostics 9006" device. Update its driver in property page using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder).
Fourth step, when the driver is installed properly, run MSM8994DownloadTool.exe in the recover tools folder, using admin privileges . Clear start in top left corner and wait for it to finish.
Click to expand...
Click to collapse
Check the post #40 on the URL provided early:
Consan said:
Second note about drivers if that I had the worst time trying to get things to work on my Windows 7 computers. Both Windows 7 and 8 block unsigned driver installations. I've tried overwriting these settings and spent half a day messing with it, and I never go the next steps to work properly. I ended up trying installing the drivers from Setup.exe and the following steps on my Windows 2003 server and things worked properly first time. I am not saying that you won't get this to work on Window 7 or 8, but if you're having troubles try Windows XP, that might make a difference.
I also deactivate unsigned driver installation but still same fail... I found a Qualcomm HS-USB QDLoader 9008 2.1.0.5 for Windows 7 that I used. I opened the Device Manager, I found my device named QHSUSB_BULK with an yellow triangle. I pressed udate drivers , choose from computer and installed that Qualcomm HS-USB QDLoader 9008 2.1.0.5 I donwloaded. AFTER THAT the tool found my phone and I was manage to flash ROM took me half a day. I cant have done wrong , somethnig must be wrong with the drivers in the tool for w7 64bit or something . this was the first time I have hard bricked a phone EVER and I have flashed a lot . But im glad it worked out with that Qualcomm HS-USB QDLoader 9008 driver since that guy also had same problem as me and later got it to work with that driver. Qualcomm HS-USB Drivers
Click to expand...
Click to collapse
Hope this helps man. Greetings!
EDIT: just noticed I linked the same as @Hellfireworks, disregard. Hope you get it fixed up.
This tool had been out for the one plus one specifically for the longest time. I wouldn't use the one plus two tool because it is for the op two.
http://forum.xda-developers.com/showthread.php?t=2991851
I haven't had to use this myself, but others have, and the forum is full of success stories. I have however fixed my buddies one plus two via an unbrick tool, and was almost the exact same process.
This tool has the proper firmware specifically for the one plus one, hence why i recommend it over the op two tool.
Sent from my A0001 using Tapatalk
So, as this is my first ever thread to this website and the reason why i have created this account, I am somewhat new to the XDA forums...
Nevertheless, i will state my problem here:
Right now, my phone and my limited knowledge about it have come to an dead end. with the help of online tutorials and so on, (I have downloaded almost 40 gigabytes worth of space to do stuff to my phone), i was able to only get the fastboot mode to work again.
It started with me uninstalling a system app from google (I don't know which one exactly, but i had the resurrection remix 5.69 or something like it, and in that ones system app remover it was one of the lowest google apps). I don't know if this is important, but at the time i did that i was in plane mode.
After some time i ran into some loading issues with games and restarted my phone. the first time i got in, i booted up normally and could do my pattern normally, but then there was only a black screen and i could pull that info bar thing down. as soon as i wanted to open the settings, everything froze and i decided to restart the phone. Once it was shut down i then got greeted by a bootloop which i aborted by shutting down after about 3 minutes. then nothing was working anymore, so i wanted to see if the fastboot mode was still available. it was, but after shutting down from that and trying again ( just to be sure) even that was gone.
so i went online and downloaded basically everything you can find online to recover a harbricked op2.
turns out, after i got my fastboot working again, the OEM and the device were locked (still not sure if those are different things or the same) and because i couldnt get in the android system, i could not enable it.
the ADB commands do not work at all because there is no device detected for it, though it is detected for fastboot. the command fastboot OEM unlock does not work because OEM unlocking is disabled...
so far i have been able to connect my phone in 3 modes and names for those, them being:
Android Bootloader interface (Fastboot)
Qualcomm HS-USB Diagnostics 900E (Connected while holding VolUp)
RELINK HS-USB QDLoader 9008 (Connected while holding VolUp + VolDown)
I am also unable to flash anything on the phone because the OEM is locked
I will not be able to answer for some time (probably 2-3 weeks) but i wanted to start this thread so I could already have an answer when i come back home again (traveling with fam, and its somewhat hard to take a PC tower with you on trips)
Thanks for helping me! :fingers-crossed:
I'm having the exact same issue as OP.
I'm not sure exactly what I did, but I can only boot to fastboot. Typing fastboot continue does not work, I can't flash ANYTHING or use any of the recovery tools, because my device is locked, and there's no system to boot to so I can run fastboot oem unlock (have to turn on debugging, which I can't do). I have read just about every guide there is, and also downloaded a boatload of purported "fix" tools/drivers/packages. My phone remains able to boot only into fastboot, and I can't get anything working.
Installing the device drivers did work for me, so I'm about half a step ahead of some other people with this issue, but none of the tools or scripts I've found, or manual methods, have brought my OP2 back to life.
I'm really, really hoping someone here is able to help with this.
Only way is restore with Qualcomm tool
Sent from my SM-N920C using Tapatalk
Coolmfarshard said:
Only way is restore with Qualcomm tool
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
Sorry, but could you link us that?
Also,does this really work with a locked device and locked OEM? Please do not tell us things if you don't know if they work.
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Lonemaster said:
Sorry, but could you link us that?
Also,does this really work with a locked device and locked OEM? Please do not tell us things if you don't know if they work.
Click to expand...
Click to collapse
Its working bro tried several phones with this tool
You cant know its working or not without trying
Coolmfarshard said:
Its working bro tried several phones with this tool
You cant know its working or not without trying
Click to expand...
Click to collapse
Ok, Thanks. Don't know what i was thinking back then.
I will reply again when i am Home and tried it. (Currently i am just using Internet cafes.)
MickyFoley said:
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Click to expand...
Click to collapse
Oh, it is that one. I had already tried this one, in all listed modes posted above. The problem with that one is that everytime I hit the start button, the green progress bar does not show up and it does not a single thing... because I am staying at a place with a internet café for 3 days, I can download some stuff and try it again.
EDIT: I don't know if that was the reason It didn't work, but I may or may not have forgotten to install the driver because it was deleted off the onedrive page and I just forgot about it afterwards. if I can find a replacement for it, I will ink it here for future users with the same problem. otherwise, I would be GLaD if someone would do that for me...
Have you tried flashing a stock ROM with the qcom download tool
abdur10567 said:
Have you tried flashing a stock ROM with the qcom download tool
Click to expand...
Click to collapse
I am not sure if it is that one (it gets pretty messy wehen you have downloaded 50 gigs), but i think it wouldn't let Me because of the locked OEM.
Lonemaster said:
So, as this is my first ever thread to this website and the reason why i have created this account, I am somewhat new to the XDA forums...
etc. etc.
Thanks for helping me! :fingers-crossed:
Click to expand...
Click to collapse
For some reason, after doing it for the what felt like the billionth time whith the restore tool it finally worked (I have NO ****ING IDEA why tho.)
Thanks for everybody who helped me.
I flashed the extracted aiomobilestuff.com BNTV460-v1.0.0_20180724.zip using spflash tool. However, the tablet now barely runs. The barnes and noble settings and apps crash if I try log in. The startup wizard crashes the first time, and I sometimes get a red border around every time I tap something.
Is there a way to fix this tablet or is it a dud now?
Ive tried factory reset, clear cache, nothing works. Interestingly, if I go to the normal settings app, nothing appears under serial number, etc. So it's no longer being able to read some of the hardware I'm guessing.
hassanhassan said:
I flashed the extracted aiomobilestuff.com BNTV460-v1.0.0_20180724.zip using spflash tool. However, the tablet now barely runs. The barnes and noble settings and apps crash if I try log in. The startup wizard crashes the first time, and I sometimes get a red border around every time I tap something.
Is there a way to fix this tablet or is it a dud now?
Ive tried factory reset, clear cache, nothing works. Interestingly, if I go to the normal settings app, nothing appears under serial number, etc. So it's no longer being able to read some of the hardware I'm guessing.
Click to expand...
Click to collapse
Hey, if you still have this device laying around somewhere, could you try updating from that firmware to see what happens?
turtleletortue said:
Hey, if you still have this device laying around somewhere, could you try updating from that firmware to see what happens?
Click to expand...
Click to collapse
I can't update, every time I try to access the barnes and noble settings app it crashes, every time I try to open the B&N app to log in, once I enter my username and password it crashes also.
hassanhassan said:
I flashed the extracted aiomobilestuff.com BNTV460-v1.0.0_20180724.zip using spflash tool. However, the tablet now barely runs. The barnes and noble settings and apps crash if I try log in. The startup wizard crashes the first time, and I sometimes get a red border around every time I tap something.
Is there a way to fix this tablet or is it a dud now?
Ive tried factory reset, clear cache, nothing works. Interestingly, if I go to the normal settings app, nothing appears under serial number, etc. So it's no longer being able to read some of the hardware I'm guessing.
Click to expand...
Click to collapse
I've been experimenting with my own since I bricked mine as well, and I was able to bring mine to full functionality. Here are a few things I learned. The scatter file in the firmware on the internet is messed up. They made the scatter file incorrectly, so as a result, whenever you flash the device with it you have to completely flash it. Their firmware has also been tampered with and probably doesn't have a serial number in it. So, I bet you wiped all of your partitions, including ones that potentially had the serial number. I dunno how to fix it, maybe see if you can get a new one from B&N for no extra cost. Unless you have a full sp flash tool backup of the device before you bricked it, I'm unsure of what to do for you. I was able to help myself because I only messed up system.img, which I took a backup of before modifying it, and I used the wwr_mtk + sp flash tool guide to make a proper scatter file so I could flash my system.img using download in sp flash tool. (Also sorry that it's been a few months since I've responded, I just thought up how I could fix my own device last night and successfully did it). Also, here is my scatter file.
hassanhassan said:
I can't update, every time I try to access the barnes and noble settings app it crashes, every time I try to open the B&N app to log in, once I enter my username and password it crashes also.
Click to expand...
Click to collapse
So here is the only solution I can think of (if you still have this device).
Download the latest boot.img and system.img (available here https://androidfilehost.com/?fid=4349826312261752630 ) and use the scatter file to flash them to the device (download mode and check system and boot and select both of the files). Let me know if you encounter any errors if you try this. NOTE: This rom is only for the Oreo version of this device, BNTV460, so for anybody with the BNTV450/Marshmallow device, your device likely will get messed up by this.
turtleletortue said:
So here is the only solution I can think of (if you still have this device).
Download the latest boot.img and system.img (available here https://androidfilehost.com/?fid=4349826312261752630 ) and use the scatter file to flash them to the device (download mode and check system and boot and select both of the files). Let me know if you encounter any errors if you try this.
Click to expand...
Click to collapse
I'm getting an error, "S_DL_GET_DRAM_SETTING_FAIL - Obtain DRAM Failed" when trying to flash any firmware files. I've tried a few different versions of SP Flasher and drivers... any input on that? How did you power on your device for flashing? My battery is completely dead and I'm plugging it in after hitting Download of SP Flasher... it recognizes the device and begins flashing, but fails.
xKroniK13x said:
I'm getting an error, "S_DL_GET_DRAM_SETTING_FAIL - Obtain DRAM Failed" when trying to flash any firmware files. I've tried a few different versions of SP Flasher and drivers... any input on that? How did you power on your device for flashing? My battery is completely dead and I'm plugging it in after hitting Download of SP Flasher... it recognizes the device and begins flashing, but fails.
Click to expand...
Click to collapse
Questions I have for you that may influence how you should handle this:
- Is the tablet you are on the Marshmallow Nook Tablet 7 (BNTV450) or the Oreo Nook Tablet 7" (BNTV460)? Ignore the rest of my questions and my advice if it is the Marshmallow BNTV450 one.
- Did you flash the stock rom that the original author of this thread flashed (the shady one that messed his device up) before trying this?
- Are you able to boot into any kind of OS? If so, let it charge and then go into that OS and finish charging before doing anything
That error sounds like a result of the shady stock firmware, since it has a different scatter file. Flashing that rom makes people lose some specific device identifiers that make it so the original firmware from B&N won't work anymore as I have seen so far.
Here is my advice if you have the Oreo Nook Tablet 7": Charge the BNTV460 as much as you can, and follow this guide to make a backup of the exact firmware on that Nook Tablet 7" https://forum.hovatek.com/thread-21970.html If the readback step gives you that same dram setting error, your device is likely a brick if it cannot boot into any OS, and you should try to exhaust any type of warranty or replacement plan with B&N that you have to get a replacement, otherwise you can continue with the rest of the guide to make a proper scatter file and rom backup for your device. I will try to guide you to my best of my ability, but this is a really confusing area due to all of the things that can go wrong and all of the risks of bricking the device permanently.
turtleletortue said:
Questions I have for you that may influence how you should handle this:
- Is the tablet you are on the Marshmallow Nook Tablet 7 (BNTV450) or the Oreo Nook Tablet 7" (BNTV460)? Ignore the rest of my questions and my advice if it is the Marshmallow BNTV450 one.
- Did you flash the stock rom that the original author of this thread flashed (the shady one that messed his device up) before trying this?
- Are you able to boot into any kind of OS? If so, let it charge and then go into that OS and finish charging before doing anything
That error sounds like a result of the shady stock firmware, since it has a different scatter file. Flashing that rom makes people lose some specific device identifiers that make it so the original firmware from B&N won't work anymore as I have seen so far.
Here is my advice if you have the Oreo Nook Tablet 7": Charge the BNTV460 as much as you can, and follow this guide to make a backup of the exact firmware on that Nook Tablet 7" https://forum.hovatek.com/thread-21970.html If the readback step gives you that same dram setting error, your device is likely a brick if it cannot boot into any OS, and you should try to exhaust any type of warranty or replacement plan with B&N that you have to get a replacement, otherwise you can continue with the rest of the guide to make a proper scatter file and rom backup for your device. I will try to guide you to my best of my ability, but this is a really confusing area due to all of the things that can go wrong and all of the risks of bricking the device permanently.
Click to expand...
Click to collapse
Thanks for the quick response. It is the BNTV450/Marshmallow, which may be part of the problem. I do get the same error on the readback. It may be time to just retire the thing and grab a new ereader, I got a few years out of it and it was cheap.
EDIT: To respond to your question, I did use the shady ROM above. So note to others: don't do that...
xKroniK13x said:
Thanks for the quick response. It is the BNTV450/Marshmallow, which may be part of the problem. I do get the same error on the readback. It may be time to just retire the thing and grab a new ereader, I got a few years out of it and it was cheap.
EDIT: To respond to your question, I did use the shady ROM above. So note to others: don't do that...
Click to expand...
Click to collapse
Yeah, your device may be completely bricked. The Nook Tablet 7's are confusing due to the two of them being only slightly different, but different enough for disaster to happen.