Related
I hope I'm posting in the correct place.
I think I've bricked my Nook Touch (tell me it isn't so!). The problem is as stated in the subject line. Now it won't turn off or respond at all to hardware or touch. Is there at least a way to get the screen back to "Read Forever"?
Please help, and let me know if you need more information!
I'll be so grateful if this problem can be at least partially solved.
try to remove sd-card and reboot it
I tried that; the Nook Touch will not reboot. Thanks for replying.
Would the zip file Nook Simple Touch Full_Factory_Restore.zip work for me in this scenario? If so, where can I get the file?
Its almost impossible to brick this device. Try this first.
Hold power firmly for 30 seconds.
let it go
Wait 10 seconds
Hold power again for about 10 or so seconds the screen should change and you should reboot.
Try this with the SD card in and out. You can also try and repeat the step of writing the .img to your SD card. Download the file again or verify the checksum in case you got a bad download.
The screens will not necessarily change if you are stuck in a boot loop and power down. Regardless if it doesn't boot 8 times it will revert its pretty much impossible to brick the unit. You can also try to power off via ADB and or try the script that forces the 8 failed reboots.
____________________
Edit I missed that it appears you intentionally formatted the device? What exactly did you do?
Also if you made a back up of the partition prior to formatting (not sure exactly what you did or why you did it) but that should have been your first step prior to doing anything exotic so you can replace the files necessary. I'm not at home otherwise I'd post the partition contents for your restore I'm sure you can find them on the net somewhere or here. I think the nook color root wiki may have the Nook touch back up files I'm not sure though. Either way its trivial to pull them and post them. Those of you that may do this make sure your account information is wiped first prior to making the back up for him.
Exactly which partition you formatted? The one normally exposed during USB connection? In this case power it off (by holding the power button for few seconds and selecting power off) and then do a hard reset
Hold power button and the bottom two side buttons until the screen starts to flicker. Release power button but hold the side bottom buttons until you see a hard reset screen
After reset the data partition will be as good as new.
Rooted Foreve screen - the brick
Hello everyone. I'm from Russia. And I have the same problem: Rooted Forever on the screen (I have formatted sd card by Mini Tool Partitition Wizard - Delete all partititions) when the SD card was into Nook and my Nook is the brick. And i can't send my Nook to B&N. None of your advices did not work. But I still have some hope. Maybe my experience will be usefull for you.
I have pushed 2 bottom buttons & power button for 30 seconds. Then 10 seconds pause. Then I have pushed 2buttons+pwr for 30 seconds again. And Nook has turned off. But the screen was completely dark. Then I turned it on and saw Rooted Forever. After that I repeated 3 buttons holding and turned the nook off. Right now my screen is completely white.
And one other thing. I also have tried nookrestorer program . I've mount an image on SD. Put it into nook. Turned it on. Script on the screen: wait for 10 sec, turn off yor nook. Take out SD. But it does not work.
I managed to lock my Nook up on boot right after I rooted it, but got it to unlock and revert to factory settings. Mine was frozen on the "Read Forever" screen and would only flash when I turned it off (something I've not read anywhere else) but this may help some of you... Don't try to do a factory reset and immediately root it again, because you may have to update the Nook again first!
First, remove the SD card, then power it off (hold the power button for 20 seconds until the screen flashed) then, letting go of the power button and immediately pressing and holding the power button again and the two bottom side buttons (I think for 10 seconds?)
The Nook would still sit on the "Read Forever" screen a minute or so, then started doing a factory reset, wiped everything including the data section and the updated software.
I had to re-update the Nook to 1.1 and then could re-root it.
---
Edit:
I realized after I posted this that I lied. Sorry. That didn't work for me, but I discovered that I could still access ADB over USB with my Nook while it was frozen on the loading screen... so I did this from my PC:
adb shell
echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt
reboot
Credit to page nookdevs dot com/Flash_back_to_clean_stock_ROM (Not enough posts to post links yet, sorry!)
Note that you do have to have the ADB installed, but I think that's key to a lot of the root methods...
Aridon said:
Its almost impossible to brick this device. Try this first.
Click to expand...
Click to collapse
Bricking the NST is quite easy, just boot with Noogie and write some garbage onto the flash.
Lots of people do this by trying to write incomplete backups back to their NST.
If what you write is big enough to reach the /rom partition you're basically hosed.
Aridon said:
I'm not at home otherwise I'd post the partition contents for your restore I'm sure you can find them on the net somewhere or here. I think the nook color root wiki may have the Nook touch back up files I'm not sure though. Either way its trivial to pull them and post them. Those of you that may do this make sure your account information is wiped first prior to making the back up for him.
Click to expand...
Click to collapse
This is a very bad advice, the /rom and /factory partition contains data unique to every NST such as MAC address, serial, board serial, EAN, private and public keys, etc..
Using a backup from another NST can and will cause troubles for you and the person owning the NST the backup came from.
My NST was bricked as well, after a Salsicha-image write session failed. Permanently stuck in the "Rooted forever" screen no matter what I pressed. Prior to the write, I have deleted ALL the partitions on my NST and then it wouldn't boot, so it seemed gone forever.
Yet it turned out that my NST can still boot with the Nookie image on a microSD
( from the BACKUP/RESTORE N2E Win7 thread). Connect it via USB to the PC and managed to restore it using my backup image. Eventually I did did the Salsicha root successfully. My NST is now rooted with 1.1.
I don't have specific advices, but the NST does seemed hard to be properly bricked. Given my experiences, I actually wonder if the NST hardware could bootstrap itself entirely from the microSD, irrespective of the state of its internal flash.
Just solved this thing: formatted microSD with Noogie Image, then deleted all partitions and than flashed my backup image back and Nook is working fine now!
jack ng said:
I actually wonder if the NST hardware could bootstrap itself entirely from the microSD, irrespective of the state of its internal flash.
Click to expand...
Click to collapse
Yes it can.
Bricked Nook
I've also formatted my Nook when I was thinking that I was formatting the sdc. I've tried installing the nookRestore img and nT2-Recovery but both of these get to the screen where it says to wait but then the Nook won't reboot. My Nook can no longer be seen by my computer so isn't showing up in device manager. I've also tried the various boot tricks manually. I also lost my backup of my Nook when I had to reinstall Windows a week ago. If anyone could help that would be great!
Thanks.
Edit---
I've found my backup image but it says Install Failed: Please power off and back on. I do this but it says the same thing. It shows up for a few seconds in device manager right after I power it on but the device id is wrong, USBSTOR\DISK&VEN_B&N&PROD_EBOOK_DISK&REV_0100\11223344556677&0. And then it disconnects in a few seconds.
aknas22 said:
I've also formatted my Nook when I was thinking that I was formatting the sdc. I've tried installing the nookRestore img and nT2-Recovery but both of these get to the screen where it says to wait but then the Nook won't reboot.
Click to expand...
Click to collapse
If you formatted your NST, Factory Restore (and thus n2T-Recovery) will not work as you removed the partition containing the actual Restore image (partition 3)
aknas22 said:
Edit---
I've found my backup image but it says Install Failed: Please power off and back on. I do this but it says the same thing. It shows up for a few seconds in device manager right after I power it on but the device id is wrong, USBSTOR\DISK&VEN_B&N&PROD_EBOOK_DISK&REV_0100\11223344556677&0. And then it disconnects in a few seconds.
Click to expand...
Click to collapse
What size is your backup image?
The unknown device you see for a split second at boot can be ignored, this is normal behavior.
It's 77.5 megabytes, I made it with Roadkill but I'm not sure if I did it right. I got it best the install fail screen. I'm not absolutely sure that I formatted the Nook but since none of the recovery methods or other images work that's the only thing I can think of. Also its no longer communicating with my computer properly.
Thank you for your reply.
I remember that there was a file(image) that works on the same principle as Noogie, but it will start the factory reset instead. Have you tried that ??? Unfortunately I don't know whether it uses/refers to the "formated" factory partition or it makes it's own. I think yo might find it in one of the threads, about rooting the Nook.
P.S. : the size of your backup file is too small ... it has to be about 1.8G
aknas22 said:
It's 77.5 megabytes, I made it with Roadkill but I'm not sure if I did it right. I got it best the install fail screen. I'm not absolutely sure that I formatted the Nook but since none of the recovery methods or other images work that's the only thing I can think of. Also its no longer communicating with my computer properly.
Thank you for your reply.
Click to expand...
Click to collapse
Your backup is worthless, don't bother with it.
Also Factory Restore, n2T-Recovery etc won't help you.
Check your PM in a few mins.
zholy said:
I remember that there was a file(image) that works on the same principle as Noogie, but it will start the factory reset instead. Have you tried that ??? Unfortunately I don't know whether it uses/refers to the "formated" factory partition or it makes it's own. I think yo might find it in one of the threads, about rooting the Nook.
P.S. : the size of your backup file is too small ... it has to be about 1.8G
Click to expand...
Click to collapse
Thanks for your reply, yea my backup is missing something, I thought I found a my good one but it doesn't seem to be. I found those other images but as ros87 said they don't work either.
Keep getting "Install failed" screen
Well, I seem to have bricked my NST as well.
I was trying to unroot from TouchNooter by restoring what I now know was a bad backup image (only 77MB). I am also certain that the NST was reformatted as well.
When there is no SD card in the NST it is stuck in the "Install Failed" screen. It can reboot but just goes back to the "Install Failed" screen.
I have located the original backup image of the NST when it was fresh out of the box and think it's a good one (1.92GB), but I am unable to restore it while the nookie image is mounted in the SD drive. I have also tried the two manual restore images (NST-Recovery) and although they ran succesully they did not fix the problem.
Is there anything else I can try to get my NST working again or is it bricked forever?
UPDATE: SUCCESS!
Just in case anyone else runs into this problem:
I was using roadkil's disk image program to restore the known good backup image and kept getting an error message: "Error #5 occured while writing to disk at sector 0". A google search of that error turned up a in a blog where I learned that roadkil doesn't play well with windows 7. What you have to do is run a program called lockdismount.exe version 0300 (google it), lock that physical drive, and leave that program running. THEN run disk imager and restore the backup image to the NST. When disk imager is done, exit that program, go back to lockdismount, unlock that drive, and then exit lockdismount.
Note: When disk imager was finished restoring it gave me an error, but I went ahead and booted up the NST anyways. My Simple Touch is back to it's factory-fresh state and all is well again
*Many* thanks to everyone who posts in this forum. Going through all the posts helped me troubleshoot and eventually unbrick my Nook SimpleTouch.
Life saver!!!! Thank you!!!
ajjdowning said:
Well, I seem to have bricked my NST as well.
I was trying to unroot from TouchNooter by restoring what I now know was a bad backup image (only 77MB). I am also certain that the NST was reformatted as well.
When there is no SD card in the NST it is stuck in the "Install Failed" screen. It can reboot but just goes back to the "Install Failed" screen.
I have located the original backup image of the NST when it was fresh out of the box and think it's a good one (1.92GB), but I am unable to restore it while the nookie image is mounted in the SD drive. I have also tried the two manual restore images (NST-Recovery) and although they ran succesully they did not fix the problem.
Is there anything else I can try to get my NST working again or is it bricked forever?
UPDATE: SUCCESS!
Just in case anyone else runs into this problem:
I was using roadkil's disk image program to restore the known good backup image and kept getting an error message: "Error #5 occured while writing to disk at sector 0". A google search of that error turned up a in a blog where I learned that roadkil doesn't play well with windows 7. What you have to do is run a program called lockdismount.exe version 0300 (google it), lock that physical drive, and leave that program running. THEN run disk imager and restore the backup image to the NST. When disk imager is done, exit that program, go back to lockdismount, unlock that drive, and then exit lockdismount.
Note: When disk imager was finished restoring it gave me an error, but I went ahead and booted up the NST anyways. My Simple Touch is back to it's factory-fresh state and all is well again
*Many* thanks to everyone who posts in this forum. Going through all the posts helped me troubleshoot and eventually unbrick my Nook SimpleTouch.
Click to expand...
Click to collapse
THANK YOU soooo much!!! lockdismount.exe save my NOOK. Couldn't restore my backup img using roadkil's utility but after reading your post I'm all set.
Thanks again.
overwritten rom and factory partition
ros87 said:
Bricking the NST is quite easy, just boot with Noogie and write some garbage onto the flash.
Lots of people do this by trying to write incomplete backups back to their NST.
If what you write is big enough to reach the /rom partition you're basically hosed.
This is a very bad advice, the /rom and /factory partition contains data unique to every NST such as MAC address, serial, board serial, EAN, private and public keys, etc..
Using a backup from another NST can and will cause troubles for you and the person owning the NST the backup came from.
Click to expand...
Click to collapse
Hello, i am one of those unlucky/incompetent user who overwrite those partition. My experience is this: I can use (read, browse etc) other device's ROM (with different serial etc) on my NOOK, but if I want to deregister/or re-register my device at B&N, the process leads me to an ERROR message at the end.
I have no idea how to solve this problem. Maybe editing several files on Boot partition and Factory partition. Or maybe there is a way to erease these data from these file (resetting) I d not know. Or maybe there is an ORIGINAL rom without any device specific data, I don't know... and I am a bit hopeless.
Do You have any idea?
People at B&N do not understand the problem at all...
Thanks in advance for any help!
Tamas
I just upgraded my unrooted nst to 1.1.2, it succeeded and I can enter into the system.
Then I backup my nst and restore to an old image in win7, using DiskImage 1.6, but it failed and report "failed to write section 0" or sth like that.
Seeing that error, I unplugged the usb and removed SD, then the nst stuck on "Rooted Forever", and cannot access the disk from win7 anymore.
I have tried:
1. hold on pwb 30s, release, wait 5s, hold on again -- no response, even no a flash
2. hold pwb, left, rigth -- nothing
What else can i do to recover my nst?
Thanks very much for any help.
You arent stuck on the Root Forever screen, probably you killed your nooks boot partition, so it just wont refresh the screen, nor boot.
Try the normal procedure to restore a backup, it should work.
http://forum.xda-developers.com/showthread.php?t=1142983
Thanks for reply.
It solved, I just put SD back to nook and it is able to restart and enter into the unroot system.
Thanks anyway
Hello. I have an Acer Iconia Tab A200, and recently I tried a factory reset. However, due to my meddling with system files, it won't reset.
I've tried to do a hard reset (Power on, Volume+, Orientation lock switch) but it says the following:
Erasing Userdata...
Erasing Cache...
It then reboots, and does nothing. It hangs on the Acer logo.
When trying to go into recovery (Power On, Volume-), it says the following:
Erasing Cache before SD update...
SD update cmd: recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
Recovery verified fail ...
Now, I mentioned that I meddled with the System Files. Here is what I did:
1. Removed unwanted Vendor Apps
2. Removed the DEFAULT LAUNCHER <-- I think this plays a big part in this
3. Placed a CUSTOM LAUNCHER in the VENDOR APPS FILE
4. Did a FACTORY RESET
My brother is more techy than me, so he tried to fix it. However, he somehow re-locked the bootloader and even replaced the bootloader with a newer version.
I talked to Acer Support claiming it's system files corrupted itself, but they won't fix it unless I also pay to fix my cracked screen. I'm willing to do so, but hey, I'd like to see if I could save $120. I don't mind the cracked screen.
NOTES:
The Acer Iconia Tab A200, along with their other tablets, has a USB port. I can probably load stuff from there somehow, but not sure.
It is a 16GB model with a 32GB Class 10 MicroSD card in it.
Any ideas? All help is appreciated.
Vuciz said:
Hello. I have an Acer Iconia Tab A200, and recently I tried a factory reset. However, due to my meddling with system files, it won't reset.
I've tried to do a hard reset (Power on, Volume+, Orientation lock switch) but it says the following:
Erasing Userdata...
Erasing Cache...
It then reboots, and does nothing. It hangs on the Acer logo.
When trying to go into recovery (Power On, Volume-), it says the following:
Erasing Cache before SD update...
SD update cmd: recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
Recovery verified fail ...
Now, I mentioned that I meddled with the System Files. Here is what I did:
1. Removed unwanted Vendor Apps
2. Removed the DEFAULT LAUNCHER <-- I think this plays a big part in this
3. Placed a CUSTOM LAUNCHER in the VENDOR APPS FILE
4. Did a FACTORY RESET
My brother is more techy than me, so he tried to fix it. However, he somehow re-locked the bootloader and even replaced the bootloader with a newer version.
I talked to Acer Support claiming it's system files corrupted itself, but they won't fix it unless I also pay to fix my cracked screen. I'm willing to do so, but hey, I'd like to see if I could save $120. I don't mind the cracked screen.
NOTES:
The Acer Iconia Tab A200, along with their other tablets, has a USB port. I can probably load stuff from there somehow, but not sure.
It is a 16GB model with a 32GB Class 10 MicroSD card in it.
Any ideas? All help is appreciated.
Click to expand...
Click to collapse
Do you have access to any a200 Update roms? Sometimes, you can pull the update.zip from the rom, place it on your ext sd card, reboot holding Vol+ and PWR, and it might install.
MD
Moscow Desire said:
Do you have access to any a200 Update roms? Sometimes, you can pull the update.zip from the rom, place it on your ext sd card, reboot holding Vol+ and PWR, and it might install.
MD
Click to expand...
Click to collapse
I have searched for some A200 ROMs, but can't find any that work using that method. I'm open for ANY Acer A200 official ROM, then simply updating using OTA. I tried an Acer A200 Recovery Pack I found. It is the exact stock Honeycomb image, but it didn't go. It always says recovery verified fail. I cannot unlock the BootLoader either.
Stockimage flashable while having bricked /DATA Partition
Hi Vuciz,
do you still have the issue with your bricked A200 ?
I got the same problem with mine, the only solution was to send it to repair, it seems the storage controller chip has some bug which destroyed the /DATA partition unrecoverable.
if you need to revert your Tablet to an locked bootloader you have to download an StockRom and modify it by removing the partition check (called "assert") in the update script.
please send me an message if you need further assistance.
regards and good luck with your tab.
Nickbert said:
Hi Vuciz,
do you still have the issue with your bricked A200 ?
I got the same problem with mine, the only solution was to send it to repair, it seems the storage controller chip has some bug which destroyed the /DATA partition unrecoverable.
if you need to revert your Tablet to an locked bootloader you have to download an StockRom and modify it by removing the partition check (called "assert") in the update script.
please send me an message if you need further assistance.
regards and good luck with your tab.
Click to expand...
Click to collapse
Yes I do. However the screen is also cracked so they want me to pay for that. Which I'm unable to do at this time.
anything I do, fails
Vuciz said:
Yes I do. However the screen is also cracked so they want me to pay for that. Which I'm unable to do at this time.
Click to expand...
Click to collapse
I also have this tablet. I bought it for 20 bucks because the screen was cracked. replaced the screen and then found out that the bootloader was trashed. I've done almost everything I can think of to fix it. Used APX mode to get UID from ubuntu, tried to use that UID to get sbk, got the SBK and then tried using blackthunder's tool got connection failure, tried using babsector same thing, even went in ubuntu, with tablet in manual apx mode for all three and when I attempt to reflash the bootloader, all I get is that command failure message with a nvflash connection failed nv error 0x30011 message and when that happens in windows, the tablet disappears from device manager, and in ubuntu when I run nvflash with the sbk function --sbk XXXX and so on, I get the command sent failure message, and then when i rerun lsusb, the nvidia device that represents my tablet in apx mode that showed before is no longer listed unless i reboot the tablet in apx mode again. If i boot it normally, the acer logo appears and then goes to the little animation and then the iconia tab screen and thats it. I've tried attempting to flash the bootloader from that screen which i know probably wasn't going to work anyways. If anyone has any advice on something I've missed, or anything that could help, i'll all eyes. thanks in advance.
twanhines said:
I also have this tablet. I bought it for 20 bucks because the screen was cracked. replaced the screen and then found out that the bootloader was trashed. I've done almost everything I can think of to fix it. Used APX mode to get UID from ubuntu, tried to use that UID to get sbk, got the SBK and then tried using blackthunder's tool got connection failure, tried using babsector same thing, even went in ubuntu, with tablet in manual apx mode for all three and when I attempt to reflash the bootloader, all I get is that command failure message with a nvflash connection failed nv error 0x30011 message and when that happens in windows, the tablet disappears from device manager, and in ubuntu when I run nvflash with the sbk function --sbk XXXX and so on, I get the command sent failure message, and then when i rerun lsusb, the nvidia device that represents my tablet in apx mode that showed before is no longer listed unless i reboot the tablet in apx mode again. If i boot it normally, the acer logo appears and then goes to the little animation and then the iconia tab screen and thats it. I've tried attempting to flash the bootloader from that screen which i know probably wasn't going to work anyways. If anyone has any advice on something I've missed, or anything that could help, i'll all eyes. thanks in advance.
Click to expand...
Click to collapse
Just so you know, I was never able to resolve this issue.
Hello,
I search help for my Acer Iconia Tab A200.
During a flash with TWRP, it block and I have to set my A200 off using Power.
And then, my A200 don't work, don't vibrate.
I try :
Reset + Power : nothing, no vibration
Power + Vol- : nothing, no vibration
Power + Vol+ + switch : same result
Connected to PC : adb devices : nothing
All commands adb or fastboot : waiting for device
I don't know what to do...
where can I send my Acer tablet to fixed stuck on bootloader
hello I have an acer iconia 200 stuck bootloader cant find anyone to fix it. Acer wont touch it unless its under warrenty! my 90 day store warrenty has been way past! taken to 2 local computer tech both told me I needed to send it back to acer but I cant! so what can ido i or where can I send it?? anyones time and effort would greatly appreicated!!! thanx for your time
Hello Fellows,
First I'd like to explain my situation in details.
my phone fell while i was walking on the street and it got some dirt on it, so ( foolishly ) I decided to clean it.... and yeah... i washed my phone like washing a dish... i like rinsed the phone in water and in other cleaning liquids for no more than 3 seconds it was all quick thingy... anyway after washing it.... i directly powered it ON and it powered but the screen was OFF ( so i decided to power it OFF, solder it and to remove any clues of water inside on the board or something... after that i used a hairdryer ( which is not recommended ) but i used it at a descent distance so that no harm would be caused to the board... as i was only subjecting air to let water if any existed to dry..
i put the phone in rise and kept it for 1 day... after 1 day i wanted to check out how stuff went.. so i powered it ON and the screen actually turned ON and the vibrator, even the hardware back-light lighted up perfectly but here's the problem I'm facing.
the phone only boots into TWRP 3.1.0.0 no matter what i do.. things i tried:
1- flashed some ROM, through TWRP
2- used "Fixed Contexts" in TWRP
3- Repair File System "System partition" through TWRP
4- used file manager inside TWRP and checked if the internal storage is working and indeed i can show all my files, through TWRP
5- also used the file manager to access "System" Partition and everything was there, through TWRP
6- change File System into EXT4 "System partition" through TWRP
7- Resize File System "System partition" through TWRP
8- Wiping all Partitions "Excluding the internal storage"
and NON WORKED..
note that whenever i attempt to flash a ROM the result shows successful with no errors ..
so whats the problem in here?
i have a guess but i need help in order to apply it.. i think the VOL- is pressed and stuck somehow Electrically on the board ( but no physically as i can press the volume down and hear its tap or whatever you call it.. i even managed to boot into fast-boot and it worked.
is there anyway i can disable the vol- button temporary to see if its causing the problem?
the only thing is i cant see my ROM booting... not even the boot animation showing... just the boot-loader and automatically it goes into the recovery
also i have kernel log attached below followed by the recovery log
EDIT: i also forgot to mention that my PC recognize the phone and i have access to my internal storage.. no problems with transfer speed as well
after tons of attempts and searching online and flashing stuff and blablabla... (i flashed every recovery image op2 support )
FINALLY
I found the solution my self, and everything is back to normal...
the phone was stuck at the early stage of the booting process and maybe couldn't find the boot image in order to boot up the android OS, so all i did was i plugged in the phone into the PC, i started everything in fastboot mode on phone and on PC then i just sent the following command to my phone.
Code:
fastboot continue
fastboot then(meaning after the command) wasnt able to recognize the phone anymore so i knew that its now trying to search for partitions other than recovery.. i waited like 10 seconds and booom it booted into the best ROM i've ever used ( and actually missed ) which is Official RR from our great maintainer "nicesoni_ash"
P.S: the vol- as i said was really stuck and i noticed it not working while on RR ROM, so i just clicked it many times and tried mixing vol+ with vol- .. after many many attempts vol- worked and i then rebooted to make sure if everything is back to normal and no recovery auto boots and indeed it smoothly booted up :laugh:
thanks a lot for all who tried to help out in here or on oneplus forums :highfive:
#back_to_resurrect_and_will_always_remix
Did you try reverting to stock ?
Try getting files from here..
https://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
I would consider it as bricked, after all attempts failed and go with the unbrick guide here on xda or oneplus forums, maybe this way it can be ressurected.
You probably have already backed up your data..
Damn, that hurts..
mithu.creative said:
Did you try reverting to stock ?
Try getting files from here..
https://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
Click to expand...
Click to collapse
sorry for this late reply but yes i have tried flashing every ROM from stock to Custom ones even i flashed EVERY SINGLE RECOVERY IMAGE OUR PHONE SUPPORTS XD and non worked... first aid.. qualcomm toolkit... non...
hello bro, i updated a magisk module v4android and when i reboot, it boots up in twrp. and since then it keeps booting into twrp. So, i used fastboot continue and when it boot int the home i deleted that module.
but fastboot continue only works once. After that if i switch-off and switch-on the phone, it goes into twrp. it needs fastboot continue everytime.
please provide me a permanent solution. few other users are facing this too. plz reply i'm waiting.
Hey,
with the help of some others in a Discord server (thanks @thesanjayp#6251 on discord) i managed to find the issue. Appearantly there was a change in /dev/block/bootdevice/by-name/misc for some reason. There was a similar problem on the old LG Optimus G Pro which i owned, so i remembered this.
As I'm not sure if we can just wipe the partition or not, i got a working misc.img attached.
In any terminal (adb shell, twrp terminal or an terminal app in a rom) make sure you have su rights, and then execute the following command:
Code:
dd if=/path/to/misc.img of=/dev/block/bootdevice/by-name/misc
Make sure to adapt the path to the misc.img though to the location you saved it to.
The misc.img I used is attached to this post.
PS: Im not responsible for any broken phones if this didnt work for you.
Hello everyone, just wanted to say a quick thanks, after successfully rooting and installing custom roms on two phones thanks to the information on these forums, third time turns out to be a charm and I managed to hard brick my new P10 lite.
The situation right now:
no charge light, no combination of buttons will do anything, phone is dead and will not boot or vibrate.
my computer will recognize that a phone is connected, for example Hisuite will pop up when i connect the phone, and in device manager, it shows Lemobile android device and the submenu says Android bootloader interface.
how i got here:
i was trying to install lineage 14.1 from this haky86
https://forum.xda-developers.com/p8...m-lineageos-14-1-huawei-p8-lite-2017-t3649292
but before i did that, i used this guide to install twrp and supersu:
https://forum.xda-developers.com/p10/how-to/twrp-how-to-root-p10-lite-t3617418
everything went fine, on the stock operating system i had root and system was running.
when i installed lineage, i lost root and couldnt figure out how to get it back. so i used this guide to restore the stock system and was going to try again from the beginning.
https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097
however, when i tried to reinstall lineage for the second, third and fourth time, i kept getting stuck in a bootloop with the lineage animation. it seemed to me that i needed to flash the vendor image, and i found a guide on xda how to do it, but it wouldnt let me flash to the vendor partition. (sorry, i dont recall the exact error and i cant get there anymore :/)
so in massive frustration and desperation, i tried to use this method:
https://forum.xda-developers.com/p8...uide-unbrick-huawei-p8-lite-2017-pra-t3713574
which i know is for a p8 and i never should have tried to install it, but it went through the whole download process and at about 50-60% on the recovery the phone went black and never turned on again.
i have read that perhaps disconnecting the battery for a few minutes might help? or is this something that dc unlocker can help with?
any advice would be greatly appreciated. if more information is needed, please let me know.
Hi,
Have you tried completely turning off your phone (pressing on/off button for roughly 20 seconds) and then booting into recovery (pressing Volume Up and Power key simultaneously for rouhgly 10 seconds)?
Best,
Kenny
Thanks for the reply, but as I said, no button combinations elicit any response. The only sign that the phone is not completely dead is that it will be recognized by my computer as an android phone, but adb (for example) says no device is connected.
lineage gives you bootloop due to wrong data partition format
bricked my p10 lite several times same ending
only way that always gets the phone back to life is flashing lineage, i took haazan's one
BUT BEFORE flashing the lineage 14.1 zip check partition format is ext4
when back on lineage and stock ROM is wanted boot into twrp and re change format to f2ts or how it is named and flash the stock zip
unbricked
edit:
saw your second post too late
if the phone does not response on any button(s) maybe adb sideload command for change partition format and then sideloading the lineage zip is a way?
I have a similar problem, I have a custom rom (Elemental) but I flash another custom rom, it was normal, in the reboot it not turn on, only is in fastboot mode, i flash original system, cust, boot, and another but it is the same, help me please