Related
Hi,
Last night i was playing with my N4 (with some root applications) and an app asked for a reboot. I just pressed yes so that the phone will reboot (I have done this earlier without any issues). Suddenly the device doesn't boot up. My N4 is stuck at a black screen. While trying to boot up, the Google logo appears and then a black screen. It doesn't advance to the 'X' logo. I'm running on stock, rooted phone (used N4 toolkit by Wugfresh to root).
I'm able to boot into recovery although. I tried all the possible means, wiped cache, dalvik cache, did a factory reset, backed up the system and tried to restore the same. Nothing happened.
Then i tried the "Back to Stock" option in the N4 toolkit and chose the option "Soft-brick/Bootloop" to recover my N4. These are what happened:
Downloaded the 4.2.2 image from Google servers and tried to flash in the device with prior instruction from the toolkit. Everything went fine until the flashing process. In the last step the CMD window opens up saying it is unrooting and flashing stock and immediately it'll bring up a complete message saying the flashing is complete and to wait until the device boots up. But nothing happens again.
I tried the automatic flashing and on the downloading window it saying download failed and hash checks failed meaning its not downloading.
I searched all the possible threads in a day to find a similar problem but in vain. I'm not a noob but i'm too lazy . But i would do anything to bring my N4 back to life. Anyone please show me a direction.
In short:
Status: Soft-Bricked (guess so), black screen after Google logo
Version: Stock 4.2.2 (rooted+busybox+supersu+twrp)
Able to boot to recovering: Yes, bootable to recovery and bootloader.
Tried Nexus toolkit recovery: Yes but in vain.
Gave up: No and never, I'm searching and searching for answers and I'm worried if I'll end up in a hard brick. :crying:
Guys, please help.
Thank You!
Aghil
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
ameinild said:
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
Click to expand...
Click to collapse
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
aghilvr said:
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Click to expand...
Click to collapse
No, my suggestion would require that the ROM is still on the phone, so you should restore your ROM prior to my suggestion. And I'm by no means an expert (therefore the disclaimer), but I *think* that since it's a bootup problem, it could be solved by flashing a new boot.img (which is essentially flashing a new kernel to the system).
But yeah, let's see if others think this might help, haven't researched it, is at work right now. Just throwing in a suggestion, that's all...
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
I *think* (again, I'm totally not sure about this, as I haven't tried it) that you can sideload a ROM via zip file from recovery, but since I haven't tried it I'm not sure - can anybody confirm???
EDIT: Chromium's suggestion is better, by pushing the ROM.zip to the device and flashing from recovery (check md5 first, just in case).
aghilvr said:
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
Yes there is. Your nexus is not bricked and this is why you shouldnt use toolkits to do things. This is honestly an extremely easy and simple fix. Use adb to push a rom onto the n4.
Code:
adb push \path\to\rom.zip /sdcard
Boot into recovery, do a full wipe, and flash the rom.
You said you downloaded the Google images.
Just boot your phone into the bootloader and run the flashall.bat that is in the Google image folder.
Note this will probably fully wipe you're phone in the process
Sent from my Nexus 4 using xda app-developers app
try this it may help u this toolkit is damn easy to use :
http://forum.xda-developers.com/showthread.php?t=1995688
Okay, thanks guys. I'm on it. Will let you know when I'm done.
That same thing happened to me once. I had to extract the google file and look for the 4 img files(bootloader, system, userdata, recovery) and flash them with toolkit manually and it fixed it, but it erased everything on my sd
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
aghilvr said:
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
Click to expand...
Click to collapse
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
chromium96 said:
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
Click to expand...
Click to collapse
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
aghilvr said:
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
chromium96 said:
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
Click to expand...
Click to collapse
Oh that's why it didn't work all the time
Thanks chromium :fingers-crossed:
Hey thanks guys, my device is back to normal. Chromium a special thanks for you for helping me out. See you guys with my next problem/queris!
Hey guys I could really use some help...I have twrp recovery but unfortuunately when i try to flash stock recoveryy back, it will not change. I have tried fastboot, nexus toolkit by wug, flashify, image flash gui, etc. Do you guys have any suggestions? Thanks so much!
Are you still unlocked or did you relock?
sfhub said:
Are you still unlocked or did you relock?
Click to expand...
Click to collapse
I am still unlocked
I don't think twrp recovery has the option to restore recovery (or I might have missed it last time I looked)
Are you doing
fastboot flash recovery stock-recovery.img
sfhub said:
I don't think twrp recovery has the option to restore recovery (or I might have missed it last time I looked)
Are you doing
fastboot flash recovery stock-recovery.img
Click to expand...
Click to collapse
Yea i did that put recovery.img in platform tools folder and executed the command....its almost like the recovery is flashed permanently...cant even flash cwm
Did you enable usb debugging in developer options before trying to flash recovery?
geckocavemen said:
Did you enable usb debugging in developer options before trying to flash recovery?
Click to expand...
Click to collapse
yes i did that...have you guys tried it? maybe its just a problem for everyone idk
slamdunksaliby said:
yes i did that...have you guys tried it? maybe its just a problem for everyone idk
Click to expand...
Click to collapse
Ive tried to reflash the stock recovery image and ended up with the same problems, anyone able to reflash the stock recovery after flashing twrp?
chuck313 said:
Have tried to reflash the stock recovery image and ended up with the same problems, anyone able to reflash the stock recovery after flashing twrp?
Click to expand...
Click to collapse
I even did a factory reset and still its sticking....i even tried to rename recovery-from-boot.bak back to .p and still nothing
I guess ill just flash cleanrom for now since the recovery is here forever lol
slamdunksaliby said:
I even did a factory reset and still its sticking....i even tried to rename recovery-from-boot.bak back to .p and still nothing
I guess ill just flash cleanrom for now since the recovery is here forever lol
Click to expand...
Click to collapse
I had a similar problem flashing the one that has "for razor" in its name. Found a different one and it worked fine.
TG2708 said:
I had a similar problem flashing the one that has "for razor" in its name. Found a different one and it worked fine.
Click to expand...
Click to collapse
interesting mine was from one of the stickies above...but ive tried multiple recoveries too...did you use fastboot? If you could maybe link the working one that would be much appreciated
slamdunksaliby said:
interesting mine was from one of the stickies above...but ive tried multiple recoveries too...did you use fastboot?
Click to expand...
Click to collapse
Yes i did use fastboot.
TG2708 said:
Yes i did use fastboot.
Click to expand...
Click to collapse
Hmm well if you could link to the working one that would be greatly appreciated I like twrp no doubt but i feel like this recovery may not even be updatable let alone changed if I ever needed to
update: after some testing It looks like the stock recovery file in the sticky above is actually twrp recovery...if someone can upload the real stock recovery file that would be great
slamdunksaliby said:
update: after some testing It looks like the stock recovery file in the sticky above is actually twrp recovery...if someone can upload the real stock recovery file that would be great
Click to expand...
Click to collapse
I've found three recoveries floating around on the forum so far. Two are in this thread -- one is in the first (1st) post under the "recovery" subtitle and the second is in the seventh (7th) post.
The other one is in this post. You have to download the Nexus_7_Restore_F.zip file and unzip it. Once you do that you will find a recovery.img file in it.
Hope one of these works. My bet is the last one will at the very least. Let us know how it turns out for you.
Thank you so much I'll let you know! Ah it looks like the stock kernel is in the last one too that's good..hopefully sometime soon we can get factory images to make things easier haha
geckocavemen said:
I've found three recoveries floating around on the forum so far. Two are in this thread -- one is in the first (1st) post under the "recovery" subtitle and the second is in the seventh (7th) post.
The other one is in this post. You have to download the Nexus_7_Restore_F.zip file and unzip it. Once you do that you will find a recovery.img file in it.
Hope one of these works. My bet is the last one will at the very least. Let us know how it turns out for you.
Click to expand...
Click to collapse
I tried flashing all of the above. With the third one (contained within the Nexus_7_Restore_F.zip), when I reboot to recovery, I get the Android with the red exclamation mark, no go. So I manually flashed TWRP back. It seems that until we get an official factory image from Google (if ever), we're stuck on TWRP. Unless there's something I haven't considered.
minazaki said:
I tried flashing all of the above. With the third one (contained within the Nexus_7_Restore_F.zip), when I reboot to recovery, I get the Android with the red exclamation mark, no go. So I manually flashed TWRP back. It seems that until we get an official factory image from Google (if ever), we're stuck on TWRP. Unless there's something I haven't considered.
Click to expand...
Click to collapse
Unless I'm mistaken the Android with a red exclamation is what you should see if you have the stock recovery installed...which means it was successful. At that point there is some combination of buttons that must be pressed to restore the recovery but I don't remember what it is (I think it might be Vol up + Power but I don't know for certain so I wouldn't try that until someone else confirms it).
minazaki said:
I tried flashing all of the above. With the third one (contained within the Nexus_7_Restore_F.zip), when I reboot to recovery, I get the Android with the red exclamation mark, no go. So I manually flashed TWRP back. It seems that until we get an official factory image from Google (if ever), we're stuck on TWRP. Unless there's something I haven't considered.
Click to expand...
Click to collapse
That is what you are supposed to see.
Please see this post for instructions:
[Info] Guide to entering safe mode, bootloader, stock recovery
geckocavemen said:
Unless I'm mistaken the Android with a red exclamation is what you should see if you have the stock recovery installed...which means it was successful. At that point there is some combination of buttons that must be pressed to restore the recovery but I don't remember what it is (I think it might be Vol up + Power but I don't know for certain so I wouldn't try that until someone else confirms it).
Click to expand...
Click to collapse
sfhub said:
That is what you are supposed to see.
Please see this post for instructions:
Info] Guide to entering safe mode, bootloader, stock recovery
Click to expand...
Click to collapse
Oh right. I actually knew that too. Been so long since I had seen stock recovery.
If you haven't seen yet, from 9/6-9/7 causes bricks on some devices.
I can still get into TWRP recovery, but it's not recognizing my device in ADB, and the kernel is probably corrupted too.
How can I push a new kernel to my device and install an older rom?
When attempting to manually install the drivers, I get "The hash for the file is not present in the specified catalog file."
ThomasBags said:
If you haven't seen yet, from 9/6-9/7 causes bricks on some devices.
I can still get into TWRP recovery, but it's not recognizing my device in ADB, and the kernel is probably corrupted too.
How can I push a new kernel to my device and install an older rom?
When attempting to manually install the drivers, I get "The hash for the file is not present in the specified catalog file."
Click to expand...
Click to collapse
Try to get into recovery and do a adb sideload install in TWRP, here is the how to http://www.google.nl/url?sa=t&rct=j...=Vp_GX8CUK5C4PSCnBss8Yw&bvm=bv.51773540,d.Yms If that doesn`t work reflash the factory image in fastboot.bootloader mode.
I have the same issue... TWRP adb sideload is not working for me. Is there any way I can fastboot flash an older version of CM (i.e. 9/05)?
kino1122 said:
I have the same issue... TWRP adb sideload is not working for me. Is there any way I can fastboot flash an older version of CM (i.e. 9/05)?
Click to expand...
Click to collapse
You guys need to flash a factory image from here https://developers.google.com/android/nexus/images in fastboot.
kino1122 said:
I have the same issue... TWRP adb sideload is not working for me. Is there any way I can fastboot flash an older version of CM (i.e. 9/05)?
Click to expand...
Click to collapse
CM 9/05 isn't in a fastboot image format. Its a flashable zip so no.
Your best case is to do a ADB sideload as what gee2012 said. Always have a trusted backup or older flashable zip to work off of.
As a last resort, flash factory image but you'll have to start all over
Hey guys I found a solution.
For those unable to get ADB sideload to work, be sure to install the drivers here: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Following that you can do the TWRP sideload thing and then it'll just tell you it's starting it up. Go into your adb command and under adb devices you will see your device in sideload mode. With that, it's just a simple command of adb sideload ROM.zip and it'll install the .zip for you and you are good to go!
That happened to me too, you can try to use adb pull and install the 9/5 cm update that is not corrupted.
Guys there is a way to alert other people to not install those updates? Always is a pain in the ass to get your phone bricked
by the way, sorry for my bad english.
one day people will learn the difference between what a brick and a soft brick is. if you can get into the bootloader, the device is not bricked, it can be fixed. even if you can't get into the bootloader, sometimes it can be fixed. doing a little research/reading before rooting your device can save you lots of hassle later on, like in this situation. even just making a backup of your current set up in your recovery before flashing anything can save you hours of stress afterwards.
simms22 said:
one day people will learn the difference between what a brick and a soft brick is. if you can get into the bootloader, the device is not bricked, it can be fixed. even if you can't get into the bootloader, sometimes it can be fixed. doing a little research/reading before rooting your device can save you lots of hassle later on, like in this situation. even just making a backup of your current set up in your recovery before flashing anything can save you hours of stress afterwards.
Click to expand...
Click to collapse
I just a matter of name bro, but, anyways, you know what have gove wrong with these nightlies?
lwkkazz said:
I just a matter of name bro, but, anyways, you know what have gove wrong with these nightlies?
Click to expand...
Click to collapse
nightlies by definition are not stable, nor are meant to be. tbey are just tbe most recent upload with whatever code was added. new code will not play nice many times, especially with other stuff included. that why they build the nightlies, to test out how the newest code will behave. whats wrong with this nightly i dont know, i don't run cm. normally, after a bad nightly, flashing tge ladt nightly tgat was good would fix the non booting problem, or restoring a nandroid backup. anyways, its a good idea to keep the last good rom(or kernel) in your storage at all times, just in case of situation like this.
simms22 said:
nightlies by definition are not stable, nor are meant to be. tbey are just tbe most recent upload with whatever code was added. new code will not play nice many times, especially with other stuff included. that why they build the nightlies, to test out how the newest code will behave. whats wrong with this nightly i dont know, i don't run cm. normally, after a bad nightly, flashing tge ladt nightly tgat was good would fix the non booting problem, or restoring a nandroid backup. anyways, its a good idea to keep the last good rom(or kernel) in your storage at all times, just in case of situation like this.
Click to expand...
Click to collapse
I do that too, you know if that a way to sinalize that the last two nightlies are not bootable?
lwkkazz said:
I do that too, you know if that a way to sinalize that the last two nightlies are not bootable?
Click to expand...
Click to collapse
if they arent bootable, then whomever compiles them already probably knows. the thing to do will be to flash the last good nightly and wait for the next nightly.
kino1122 said:
Hey guys I found a solution.
For those unable to get ADB sideload to work, be sure to install the drivers here: plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Following that you can do the TWRP sideload thing and then it'll just tell you it's starting it up. Go into your adb command and under adb devices you will see your device in sideload mode. With that, it's just a simple command of adb sideload ROM.zip and it'll install the .zip for you and you are good to go!
Click to expand...
Click to collapse
Thank you!
It worked!
An update for whoever is looking for an update: I have tried 20130918 build and it's working fine.
Well, I did something stupid and accidentally wiped system without backing up and now I don't have a ROM installed. When I try sideloading a ROM in recovery, I get the verification failed. I believe I am somehow back on android default recovery.
Can someone help me get a ROM pushed onto the device?
Thanks
phazey12 said:
Well, I did something stupid and accidentally wiped system without backing up and now I don't have a ROM installed. When I try sideloading a ROM in recovery, I get the verification failed. I believe I am somehow back on android default recovery.
Can someone help me get a ROM pushed onto the device?
Thanks
Click to expand...
Click to collapse
have you tried Odin'ing the stock tar back on?
i thought that usually fixes it, but please do a lil searching first before trying that
evilbeef54 said:
have you tried Odin'ing the stock tar back on?
i thought that usually fixes it, but please do a lil searching first before trying that
Click to expand...
Click to collapse
I ended up going back into download mode and using odin to install TWRP recovery. I guess that doesn't have problems with ADB sideload. Its sending now.. so I will see if it works. Had to do a few battery pulls =\ hope that didnt harm my device too much
TWRP ADB sideload worked. Weird... wonder why CWM adb sideload was having errors
phazey12 said:
I ended up going back into download mode and using odin to install TWRP recovery. I guess that doesn't have problems with ADB sideload. Its sending now.. so I will see if it works. Had to do a few battery pulls =\ hope that didnt harm my device too much
TWRP ADB sideload worked. Weird... wonder why CWM adb sideload was having errors
Click to expand...
Click to collapse
great, i was pretty sure flashing recovery or stock .tar with odin would work, but i am not 100% lol
Hi I'm looking for the recovery of the stock LG G PAD tablet 7 "LTE I am root backup with TWRP but I can not go back to Recovery Stock.
Before flashing the TWRP I forgot to make a backup of Recovery
Sorry for my bad English.
thanks
exebuera said:
Hi I'm looking for the recovery of the stock LG G PAD tablet 7 "LTE I am root backup with TWRP but I can not go back to Recovery Stock.
Before flashing the TWRP I forgot to make a back of Recovery
Sorry for my bad English.
thanks
Click to expand...
Click to collapse
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
jason2678 said:
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
Click to expand...
Click to collapse
hey @jason2678 thanks, but how did i flash this if i dont have twrp installed? can i use fastboot or adb?
dreamtheater17 said:
hey @jason2678 thanks, but how did i flash this if i dont have twrp installed? can i use fastboot or adb?
Click to expand...
Click to collapse
I'd recommend flashify to flash recovery images. You can download it from the play store. So easy to make a typo and mess things up with adb and dd.
You could do it with a terminal or adb shell. Say you store the image in /sdcard
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p14
Verify mmcblk0p14 is recovery before you try this. I'm pretty sure that's right, but I don't have my tablet right now and you can make a serious mess of your device this way if you overwrite the wrong partition. Check it by listing your partitions with this:
Code:
su
ls -al /dev/block/platform/*/by-name
By default this little tablet does not have fastboot, but you can enable it with this method. I've zeroed out my laf partition and verified I can boot into fastboot mode, but I've never actually used it to flash anything. It just seemed like a good idea to have fastboot available to fall back on rather than LG download mode since there was no kdz available for the V410 for a long time.
jason2678 said:
I'd recommend flashify to flash recovery images. You can download it from the play store. So easy to make a typo and mess things up with adb and dd.
You could do it with a terminal or adb shell. Say you store the image in /sdcard
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p14
Verify mmcblk0p14 is recovery before you try this. I'm pretty sure that's right, but I don't have my tablet right now and you can make a serious mess of your device this way if you overwrite the wrong partition. Check it by listing your partitions with this:
Code:
su
ls -al /dev/block/platform/*/by-name
By default this little tablet does not have fastboot, but you can enable it with this method. I've zeroed out my laf partition and verified I can boot into fastboot mode, but I've never actually used it to flash anything. It just seemed like a good idea to have fastboot available to fall back on rather than LG download mode since there was no kdz available for the V410 for a long time.
Click to expand...
Click to collapse
Thank you! the thing is i bricked my g pad, i really dont know much about the tab because the lack of support it has. I was using it with cm12.1 and i use a stock recovery founded in Android central to revert back to stock, but in TWRP i flashed the img as recovery and also as boot, so the g pad entered in a bootloop were only enters in stock recovery, my Windows 10 laptop doesn't recognize the tab when in adb sideload, and doesn't know much about adb Shell, i'm following the comandas you wrote but i'm always getting error: closed.
i know how to get back to stock using the kdz, but using the kdz will make the partition issue and will have to folllow a looong looong process.
If you could give me a hand with this i would really apprecciate it
Sorry I've never encountered the adb closed problem myself, but I have heard about it before. Some people have reported the following series of commands fixes it:
Code:
adb usb
adb devices
adb kill-server
adb start-server
The first two commands normally don't really do anything and its pretty obvious what the second two do, but some people have reported success doing this.
Some people have reported the closed error was fixed by updating their adb binary. If you're using the android-sdk update platform-tools, or if you're using a standalone adb consider looking for an update for it.
Good luck. That procedure to get things back to normal following using the kdz to restore sounds messy.
dreamtheater17 said:
Thank you! the thing is i bricked my g pad, i really dont know much about the tab because the lack of support it has. I was using it with cm12.1 and i use a stock recovery founded in Android central to revert back to stock, but in TWRP i flashed the img as recovery and also as boot, so the g pad entered in a bootloop were only enters in stock recovery, my Windows 10 laptop doesn't recognize the tab when in adb sideload, and doesn't know much about adb Shell, i'm following the comandas you wrote but i'm always getting error: closed.
i know how to get back to stock using the kdz, but using the kdz will make the partition issue and will have to folllow a looong looong process.
If you could give me a hand with this i would really apprecciate it
Click to expand...
Click to collapse
hi, i have the same problem than u, i wanna know if i can flash the US CELLULAR kdz for solve the partition issue? because i already flash the kdz test from ATT
jason2678 said:
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
Click to expand...
Click to collapse
I flashed stock rooted 4.4.2, and I want to OTA to Stock Lollipop, but it says there is no update. Any ideas of how I can get back to fully stock? Would flashing this stock recovery make it work? Is being rooted blocking the OTA update from seeing an available update?
mxpxboi said:
I flashed stock rooted 4.4.2, and I want to OTA to Stock Lollipop, but it says there is no update. Any ideas of how I can get back to fully stock? Would flashing this stock recovery make it work? Is being rooted blocking the OTA update from seeing an available update?
Click to expand...
Click to collapse
If you applied an OTA with a custom recovery installed it might soft brick your tablet, but I don't see why that would stop it from detecting and downloading the update. It is always safest to flash stock recovery, fully unroot, and undo any modifications you've made to /system before taking an OTA, but some devices are more picky than others. With what you're describing I'm afraid that even if you do unroot and flash stock recovery your tablet still won't find the OTA.
Do you have a nandroid backup of an unmodified stock ROM you could restore?
And just so you know that lollipop bootloader is not vulnerable to the bump exploit, so no custom recovery or ROMs if you get it to apply.
Whenever I type "reboot recovery" in terminal emulator, it boots straight to factory reset. I have tried this multiple times with both dd and flashify. Do you know what causes this? I'm downloading the OTA right now, I hope it doesn't wipe then too...
please help
i was a dumbass and accidently flashed my boot instead of recovery do you by chance have a boot.img that i can use to reflash my boot.img please help as im really stuck..thanks in advance
Devil911 said:
i was a dumbass and accidently flashed my boot instead of recovery do you by chance have a boot.img that i can use to reflash my boot.img please help as im really stuck..thanks in advance
Click to expand...
Click to collapse
Download the timmytim stock ROM, and extract the boot.img from it. There are probably quicker ways, but having the stock ROM on hand is a good idea.
Sent from my Amazon Fire using XDA Labs
Thank you...
I resolved my issue i had forgotten in my haste i posted the same question in two different sections. However after fixing everything my tablet was broke not the out glass but the inner display. I cant afford another one or a replacement part to even fix mine. So unless i can find one someone who bricked theirs completely or get a handme down im tabless for awhile.... Thank you though for the reply. The original boot file wouldnt work properly i had to use the boot file from the stock rooted rom and not the timmytim deoxedized rom.. i dont know why unless the bootfile is specific to each rom. Maybe i did something wromg during the flash. But i had gotten it fixed nevertheless.
Devil911 said:
I resolved my issue i had forgotten in my haste i posted the same question in two different sections. However after fixing everything my tablet was broke not the out glass but the inner display. I cant afford another one or a replacement part to even fix mine. So unless i can find one someone who bricked theirs completely or get a handme down im tabless for awhile.... Thank you though for the reply. The original boot file wouldnt work properly i had to use the boot file from the stock rooted rom and not the timmytim deoxedized rom.. i dont know why unless the bootfile is specific to each rom. Maybe i did something wromg during the flash. But i had gotten it fixed nevertheless.
Click to expand...
Click to collapse
The stock rooted is by timmytim ?
I forgot about deodexed, actually.
Glad you fixed boot, shame your tablet broke ?
Sent from my Amazon Fire using XDA Labs