Database Users

[SOLVED] TWRP 2.6.0.0 & CWM recovery black screen when into recovery

When I go into recovery on my Nexus 4 running Android 4.3. I get no more then a black screen.
It was working before and last thing I did was flashing FOTAKILL.
Now booting in recovery isn't working for me anymore.
My device is rooted and no other problems.
Weird thing is that my device says secure boot = enabled.
Lockstate = locked
I locked the bootloader with "bootunlocker". So for one of those it's true.
This last one should say "disabled" with root access right?
Still device has proper root.
EDIT:
Flashed CWM recovery instead... No use, still getting black screen when booting into recovery.
Both CWM Revocery and TWRP are not working for me anymore.
Still managed to make a NANDROID backup, just in case.
Send from my Nexus 4

DecypherT said:
When I go into recovery on my Nexus 4 running Android 4.3. I get no more then a black screen.
It was working before and last thing I did was flashing FOTAKILL.
Now booting in recovery isn't working for me anymore.
My device is rooted and no other problems.
Weird thing is that my device says secure boot = enabled.
Lockstate = locked
I locked the bootloader with "bootunlocker". So for one of those it's true.
This last one should say "disabled" with root access right?
Still device has proper root.
EDIT:
Flashed CWM recovery instead... No use, still getting black screen when booting into recovery.
Both CWM Revocery and TWRP are not working for me anymore.
Still managed to make a NANDROID backup, just in case.
Send from my Nexus 4
Click to expand...
Click to collapse
You did unlock your bootloader to flash CWM, didn't you?
What version did you flash? You're sure it was for the Nexus 4, right?
What did you use to flash it? Fastboot commands?

Yes i unlocked and then flashed. I was in bootloop after i tried to "OEM Unlock"
I flashed the TWRP 2.6.0.0 Mako version for the N4.
I used Wug's Nexus Toolkit for the flashing.
As typed i just tried CWM Recovery and that one is also not working.
Weirdest thing is that is was working without a flaw. 2 weeks back i booted into recovery and flashed FOTAKILL.
I can't understand why it wouldn't be working anymore now. I didn't mess with system files or anything else.

DecypherT said:
Yes i unlocked and then flashed. I was in bootloop after i tried to "OEM Unlock"
I flashed the TWRP 2.6.0.0 Mako version for the N4.
I used Wug's Nexus Toolkit for the flashing.
As typed i just tried CWM Recovery and that one is also not working.
Weirdest thing is that is was working without a flaw. 2 weeks back i booted into recovery and flashed FOTAKILL.
I can't understand why it wouldn't be working anymore now. I didn't mess with system files or anything else.
Click to expand...
Click to collapse
where did you grab FOTAKILL? it wasnt in the n4 threads, was it?

No it was in one of the treads about the "google data usage".
But i never read anything about different FOTAKILL versions for different phones.
Many people used it and i never read any flaws with FOTAKILL regarding recovery. I doubt FOTAKILL is the issue here.

bump
Send from my Nexus 4

DecypherT said:
bump
Send from my Nexus 4
Click to expand...
Click to collapse
Try flashing a recovery manually through fastboot
fastboot flash recovery path_to_recovery.img

Problem is solved. I flashed it again using the toolkit and miraculously it boots into recovery now.
Maybe it was because i manually re-locked the bootloader that caused the flashing to fail.

DecypherT said:
My device is rooted and no other problems.
Weird thing is that my device says secure boot = enabled.
Lockstate = locked
I locked the bootloader with "bootunlocker". So for one of those it's true.
This last one should say "disabled" with root access right?
Still device has proper root.
Click to expand...
Click to collapse
Secure boot has nothing to do with root or the bootloader. It has to do with the boot chain of the APQ8064 SoC. It will always show enabled (unless someone has figured out how to disable it, which I don't think has happened yet).
Lockstate shows the lock state of the bootloader, and having root or a custom recovery has no impact on that. It will show locked or unlocked.
Sent from my Nexus 4 using Tapatalk 4

Recovery won't flash

I had to do a complete wipe from the computer and flashed clockwork mod recovery. Since it was likely an old version I had the double 0 partition problem which I fixed by manually moving the files. I tried to update the recovery to twrp, but it won't flash using goomanager. It downloads and says it's flashed but it's not there.
I also seem to have a weird problem where I have to push the power button to get it to boot past the Google screen. If I don't push power it gets stuck there forever.
Any ideas?
Sent from my Galaxy Nexus using Tapatalk 4

Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.

SlowCobra96 said:
Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.
Click to expand...
Click to collapse
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4

T-Keith said:
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
This might be an odd question, but have you tried just updating CWM first, and THEN flashing TWRP? Sometimes the flash won't go smoothly with an older version of one recovery to a newer version of a different recovery- not sure why, but that's just been my experience. I would update CWM first then try flashing TWRP.
Also, if goo is not working for you, you could try Rom Manager to update CWM and then flash TWRP. It can flash either. (If you really want to flash via the device).
Otherwise, (me personally) I'd just use adb fastboot to flash a new recovery.
Hope that helps

Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4

T-Keith said:
Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
No problem. Let us know how it works out for you.

Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4

T-Keith said:
Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Ahh, that sucks! How are you *attempting to* access recovery... via reboot menu, via adb, or via 3-button press? It shouldn't matter, but you could try all three methods to see if any way will give you recovery access. Then, if/when you manage to get in, you could reflash again straight from recovery. I'm going to do some digging to see if I can find a better solution. I KNOW I've read about the same issue before, I know there's a solution... I just have to find it again.
Worse comes to worse, you might have to reflash stock recovery then reflash custom recovery. Might be a corrupt recovery img, but I will check and try some things out and let you know what I find.
Edited to add:
Yes. there was a bug in the older bootloader that bypassed/refused access to recovery... so since you restored stock, you probably need to update your bootloader to at least to version 4.18 (via fastboot). THEN you should be able to access recovery. I can't add links, but I can give you a text link once I find just the IMG file instead of the full firmware. Honestly, I never do backups so I don't have the file on hand. However, I may do one backup at least so I can extract my boot img and give it to you.

OK, so I found the info I was looking for.
From Elsewhere:
Steps:
Install latest nexus 7 bootloader.
This fixes the boot loader bug and now you can enter recovery from the bootloader screen.
Update the bootloader to at least 3.18. Make sure NOT TO DELETE THE BOOTLOADER!!!!!!!!!!!!!
I cannot emphasize this enough!!!!!!!!!!! I bricked my first one this way.
Use
fastboot flash bootloader C:\>>>>>>\bootloader-grouper-3.18.IMG***
Click to expand...
Click to collapse
Do NOT erase bootloader before you flash the new one. And after you have flashed the new one type;
fastboot reboot bootloader
Click to expand...
Click to collapse
and check the bootloader version to make sure you succeeded.
Click to expand...
Click to collapse
***Or whatever you name the boot img file!***
https://dl.dropboxusercontent.com/u/19608328/boot.img.zip --> This is from MY Nexus 7. It's Bootloader version 4.23, and works with JB 4.2.2- it does NOT have the recovery access bug.
https://dl.dropboxusercontent.com/u/19608328/recovery.img.zip --> This is a copy of MY CWM, which I just updated to 6.0.3.6 yesterday.
I'd flash the bootloader, then flash your recovery of choice. Not being able to access recovery is a bootloader issue, not a recovery issue. The fact that you restored/reverted an older full firmware put you on an older bootloader that would not allow users to access recovery.
Try the new(er) bootloader, it should work. My device is a 16gb grouper Nexus 7 running 4.2.2. Before that, it ran 4.1.2 without any issues, so it should work to resolve the problem you're having.

Back to Factory with no computer access.

I everyone!
I just tried to connect my Nexus 4 to my windows 8.1 laptop and the phone is not recognised by the PC. It gives me Code 43 error, I tried everything, form fresh driver install to cable change. I also tried on another W7 laptop and nothing pops up there. The phone charges but in Device Manager it is not listed under Google ADB devices but appears with an exclamation mark under USB controllers saying Device Descriptor Request Failed. I fear it is an hardware problem and RMA is the only option left. However, my phone is Rooted, Stock but with modified build.prop, with TW touch recovery and unlocked. Since I have no access to ADB I cannot use the Android SDK tools or anything to flash the factory img. Is there any way in which I could flash back the sock image and lock the bootloader via recovery only?
Thanks everyone :crying::crying:

you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.

Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app

Thibaultvw said:
Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
This was what I was thinking, however, the main issue would be locking the bootloader again
simms22 said:
you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.
Click to expand...
Click to collapse
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time

c0sk said:
This was what I was thinking, however, the main issue would be locking the bootloader again
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time
Click to expand...
Click to collapse
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.

mrhiab said:
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.
Click to expand...
Click to collapse
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?

c0sk said:
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?
Click to expand...
Click to collapse
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.

efrant said:
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.
Click to expand...
Click to collapse
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??

c0sk said:
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??
Click to expand...
Click to collapse
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2

efrant said:
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset

c0sk said:
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset
Click to expand...
Click to collapse
The way you removed SuperSU must have not worked properly. (I've never tried doing it from the SuperSU settings.) In any case, there's nothing more you can do now, so might as well send it in for RMA.

Flashing stock recovery to Homecare TN7

I was able to flash an EVGA ROM successfully and also Shaky156's CWM recovery. Primary reason was to get rid of Chinese notifications completely. Problem is that I cannot get the 1.1 OTA update to install because of the CWM recovery. I tried to flash stock recovery via fastboot but was not successful. Tried different versions even the BAT_CWM_recovery but it won't accept any except Shaky's version. Also tried the Super Tool but it won't recognize the tablet. I have previously installed the SDK and can get fastboot to run. Will try version 1.5 if it works.

Freeje said:
I was able to flash an EVGA ROM successfully and also Shaky156's CWM recovery. Primary reason was to get rid of Chinese notifications completely. Problem is that I cannot get the 1.1 OTA update to install because of the CWM recovery. I tried to flash stock recovery via fastboot but was not successful. Tried different versions even the BAT_CWM_recovery but it won't accept any except Shaky's version. Also tried the Super Tool but it won't recognize the tablet. I have previously installed the SDK and can get fastboot to run. Will try version 1.5 if it works.
Click to expand...
Click to collapse
Always erase the partition beforehand.
fastboot erase boot
then... as an example
fastboot flash boot boot.img
or
fastboot erase recovery
then... as an example
fastboot flash recovery recovery.img
Make sure you are cautious never to loose fastboot ability. Other words if your bootloader can't be obtained from restarting and hold buttons down, then make sure you don't restart till you get a successful flashing. Always have the system ADB enabled and certified with the computer.

e8hffff said:
Always erase the partition beforehand.
fastboot erase boot
then... as an example
fastboot flash boot boot.img
or
fastboot erase recovery
then... as an example
fastboot flash recovery recovery.img
Make sure you are cautious never to loose fastboot ability. Other words if your bootloader can't be obtained from restarting and hold buttons down, then make sure you don't restart till you get a successful flashing. Always have the system ADB enabled and certified with the computer.
Click to expand...
Click to collapse
Did what you said but still no stock recovery installed. When I reboot after erasing the old recover and flashing the stock instead of going to recovery it just boots up. Looks like the recovery never gets flashed. I did check if the tablet is being recognized by the computer before any flashing. After flashing the stock recovery it says okay so I don't know what's happening.

Freeje said:
Did what you said but still no stock recovery installed. When I reboot after erasing the old recover and flashing the stock instead of going to recovery it just boots up. Looks like the recovery never gets flashed. I did check if the tablet is being recognized by the computer before any flashing. After flashing the stock recovery it says okay so I don't know what's happening.
Click to expand...
Click to collapse
Have you done an OEM unlock?
fastboot oem unlock

e8hffff said:
Have you done an OEM unlock?
fastboot oem unlock
Click to expand...
Click to collapse
Yes, tablet is unlocked. Says so when I boot into the bootloader. I have flashed Shaky's CWM and it installed fine. Don't know why the tablet does not like the stock recovery. Even tried BAT-cwm recovery but also failed to install. I'll just have to wait for someone to come up with a flashable ROM if the Kitkat update comes around.

Freeje said:
Yes, tablet is unlocked. Says so when I boot into the bootloader. I have flashed Shaky's CWM and it installed fine. Don't know why the tablet does not like the stock recovery. Even tried BAT-cwm recovery but also failed to install. I'll just have to wait for someone to come up with a flashable ROM if the Kitkat update comes around.
Click to expand...
Click to collapse
Do your best to get Bat_recovery for the recovery parititon and the 4.3.1 boot.img for the boot partition, shared on my Tegra Note Discoveries thread. Never flash the bootloader partition unless you are really know what you're doing. Then possible flash the system partition with Tom's system.img with;
fastboot erase system
fastboot flash system system.img
Tom's image should patch and is an English styled setup so you get all the Google Apps, etc.

e8hffff said:
Do your best to get Bat_recovery for the recovery parititon and the 4.3.1 boot.img for the boot partition, shared on my Tegra Note Discoveries thread. Never flash the bootloader partition unless you are really know what you're doing. Then possible flash the system partition with Tom's system.img with;
fastboot erase system
fastboot flash system system.img
Tom's image should patch and is an English styled setup so you get all the Google Apps, etc.
Click to expand...
Click to collapse
Here's what I did:
1. Erased the system and flashed the 4.3plus system zip.
2. Erased the boot image and flashed the 4.3plus boot image.
3. Erased the recovery and flashed the bat recovery.
4. Rebooted and got stuck on the Tegra Note screen. (flashing on and off).
Tried to experiment and flashed another boot image and this time got stuck on the Tegra Note screen but this time it was not flashing on and off. Turned it off but nothing happened, Pressed the key combination to boot to the bootloader mode but failed. I thought I bricked it and then tried to go the the apx mode and was successful. This time I pressed the bootloader key combination and thankfully was successful. I thought I bricked the tablet.
Is there a way to flash the 4.2.2 ROM? Read somewhere that someone flashed the old ROM and the stock recovery. Once done he was able to update to 4.3plus. I thought there was a flashable 4.2.2 ROM at rootjunky.com but when I clicked on the link I got an error message saying that the file does not exist. I asked the poster where he got the ROM and recovery but never got a reply.
I'll try to flash the 4.3 ROM back

homecare tegra note 7
Freeje said:
Here's what I did:
1. Erased the system and flashed the 4.3plus system zip.
2. Erased the boot image and flashed the 4.3plus boot image.
3. Erased the recovery and flashed the bat recovery.
4. Rebooted and got stuck on the Tegra Note screen. (flashing on and off).
Tried to experiment and flashed another boot image and this time got stuck on the Tegra Note screen but this time it was not flashing on and off. Turned it off but nothing happened, Pressed the key combination to boot to the bootloader mode but failed. I thought I bricked it and then tried to go the the apx mode and was successful. This time I pressed the bootloader key combination and thankfully was successful. I thought I bricked the tablet.
Is there a way to flash the 4.2.2 ROM? Read somewhere that someone flashed the old ROM and the stock recovery. Once done he was able to update to 4.3plus. I thought there was a flashable 4.2.2 ROM at rootjunky.com but when I clicked on the link I got an error message saying that the file does not exist. I asked the poster where he got the ROM and recovery but never got a reply.
I'll try to flash the 4.3 ROM back
Click to expand...
Click to collapse
have you tried extracting the Rom and nvflash into the same folder and running the "download.bat" to fix this? I haven't found a nvflash that works with tegra note 7

Tha T said:
have you tried extracting the Rom and nvflash into the same folder and running the "download.bat" to fix this? I haven't found a nvflash that works with tegra note 7
Click to expand...
Click to collapse
Don't know how to do that.

I've managed to flash a 4.2.2 ROM (tried the deodex version first) but not the stock recovery. Funny thing is that only Shaky156's version can be flashed. The big problem with the ROM is that there's no wifi and that sucks big time. It means I can't update the the firmware. Will try to flash the odex version and see the wifi works. There's no access to the files too. Good thing the bluetooth works.

REcovry
pls, what recovery works best with the homecare tegra note? prefarably one that allows backup/restore with external sd card

Freeje said:
I've managed to flash a 4.2.2 ROM (tried the deodex version first) but not the stock recovery. Funny thing is that only Shaky156's version can be flashed. The big problem with the ROM is that there's no wifi and that sucks big time. It means I can't update the the firmware. Will try to flash the odex version and see the wifi works. There's no access to the files too. Good thing the bluetooth works.
Click to expand...
Click to collapse
so did the odex$.2.2 work fine or what solution did you use? And where did you get your 4.2 rom ?

Freeje said:
I've managed to flash a 4.2.2 ROM (tried the deodex version first) but not the stock recovery. Funny thing is that only Shaky156's version can be flashed. The big problem with the ROM is that there's no wifi and that sucks big time. It means I can't update the the firmware. Will try to flash the odex version and see the wifi works. There's no access to the files too. Good thing the bluetooth works.
Click to expand...
Click to collapse
The no wifi problem is endemic of a broken/mismatched boot.img to system version. Get an original (eg EVGA version) boot.img not a modified rooted version, since SuperSU sideloaded will give proper root later on top of an original boot.img.
I have boot.img shared on Tegra Note Discovery thread.

Try using rootjunkie supertool and get new kit kat or flash another ROM very easy to use
Sent from my Moto G using XDA Premium 4 mobile app

Tha T said:
pls, what recovery works best with the homecare tegra note? prefarably one that allows backup/restore with external sd card
Click to expand...
Click to collapse
I can only get Shakys156 recovery to work but it does not have backup/restore to ext sdcard.

recovery
Freeje said:
I can only get Shakys156 recovery to work but it does not have backup/restore to ext sdcard.
Click to expand...
Click to collapse
ok, thanks. And have you finally fixed your wifi issue? I'm on 4.3+ deodex and mine doesn't even rotate the screen

e8hffff said:
The no wifi problem is endemic of a broken/mismatched boot.img to system version. Get an original (eg EVGA version) boot.img not a modified rooted version, since SuperSU sideloaded will give proper root later on top of an original boot.img.
I have boot.img shared on Tegra Note Discovery thread.
Click to expand...
Click to collapse
Are these the files that you're referring to?
TegraNote_bootimg_4p4rip.zip
TegraNote_bootimg_4p3p1rip.zip
I tried flashing the deodex version of 4.3+ and then flashed the boot image (from TegraNote_bootimg_4p3p1rip.zip) but I still get no wifi.

Tha T said:
ok, thanks. And have you finally fixed your wifi issue? I'm on 4.3+ deodex and mine doesn't even rotate the screen
Click to expand...
Click to collapse
No luck. I tried what e8hfff suggested but still got no wifi. I used to have a Korean version of the Galaxy S3 and I could flash the modded ROMS made for the international version only if it is converted. Some guy came up with a converter and you flash it after you have flashed the modded ROM. We might have to get something similar if we want to flash EVGA ROMs.
Right now I'm not that concerned with getting the Kitkat update since there's something wrong with it (write to SD card). Once they have come up with an update to correct the bug then I'll give it another try. SO for now, I'll stick to the 4.3 ROM.

Freeje said:
Are these the files that you're referring to?
TegraNote_bootimg_4p4rip.zip
TegraNote_bootimg_4p3p1rip.zip
I tried flashing the deodex version of 4.3+ and then flashed the boot image (from TegraNote_bootimg_4p3p1rip.zip) but I still get no wifi.
Click to expand...
Click to collapse
Yes try, TegraNote_bootimg_4p3p1rip.zip first as I haven't tested the 4.4 boot.img, and only use the boot.img within as there is another directory of the uncompress boot.

wifi
Freeje said:
No luck. I tried what e8hfff suggested but still got no wifi. I used to have a Korean version of the Galaxy S3 and I could flash the modded ROMS made for the international version only if it is converted. Some guy came up with a converter and you flash it after you have flashed the modded ROM. We might have to get something similar if we want to flash EVGA ROMs.
Right now I'm not that concerned with getting the Kitkat update since there's something wrong with it (write to SD card). Once they have come up with an update to correct the bug then I'll give it another try. SO for now, I'll stick to the 4.3 ROM.
Click to expand...
Click to collapse
Does shaky156's version have a working wifi or any rom at all, (even 4.2) that has wifi, my TN7 is next to useless without it

Nexus 10 stuck at Fastboot Mode....I think

I have a Samsung Google Nexus 10 (Wi-Fi) GT-P8110HAAPHE Which was running Android 4.4.3 (I think but it is definitely the latest version) and I simply wished to root it.
I started following a video on Youtube and now I am stuck at what I think is called the Fastboot mode where My options are to scroll through START/RECOVERY MODE/RESTART BOOTLOADER/POWER OFF. I was using the Wugs Nexus Root Toolkit v1.8.3.
No matter which I select it returns me to the screen with the START option. When I select POWER OFF it does indeed power off but when I switch it on again it returns to the fastboot mode START option. I can get into download mode if that helps.
I did create a backup but cannot restore it.
I have done some research and downloaded the Android SDK Suite and fastboot/ADB and drivers etc ready to try and recover but I don't know where to start.
I have a Samsung Galaxy S3 which I have rooted and installed a number of different ROMS on so I am familiar with rooting but not sure if I can use Odin or something similar.
I think I have included all the information I have and hope someon can assist.
Thanks.

matrixmainframe said:
I have a Samsung Google Nexus 10 (Wi-Fi) GT-P8110HAAPHE Which was running Android 4.4.3 (I think but it is definitely the latest version) and I simply wished to root it.
I started following a video on Youtube and now I am stuck at what I think is called the Fastboot mode where My options are to scroll through START/RECOVERY MODE/RESTART BOOTLOADER/POWER OFF. I was using the Wugs Nexus Root Toolkit v1.8.3.
No matter which I select it returns me to the screen with the START option. When I select POWER OFF it does indeed power off but when I switch it on again it returns to the fastboot mode START option. I can get into download mode if that helps.
I did create a backup but cannot restore it.
I have done some research and downloaded the Android SDK Suite and fastboot/ADB and drivers etc ready to try and recover but I don't know where to start.
I have a Samsung Galaxy S3 which I have rooted and installed a number of different ROMS on so I am familiar with rooting but not sure if I can use Odin or something similar.
I think I have included all the information I have and hope someon can assist.
Thanks.
Click to expand...
Click to collapse
This is why I tell people not to use toolkits. Since everything is automated, it's hard to tell what went wrong and where. When it comes to Nexus devices, toolkits are entirely unnecessary IMO. These Nexus devices are so super simple to flash manually it's ridiculous. /END RANT
Okay. Sorry about that. Now, back to the issue at hand. The menu you are describing is, in fact, the Bootloader (aka Fastboot mode). Prior to using the NRT, were you completely stock? Was your bootloader already unlocked? To me, it sounds like you may have wiped your OS. Have you tried flashing the 4.4.3 factory image?

I was completely stock. Whilst using NRT I believe I had just succeeded in unlocking the Bootloader and the video then stated that with 4.4.3 a Factory reset was required which is what I did but I did not realise that deleted the O2. I thought that was on a protected partition like my S3 phone.
I can't flash the factory image as I can't get into recovery or is there another way of doing it?
I suppose where tablets are concerned I'm a book but if you could point me to any instructions on how to flash manually I'm hoping I can recover my tablet. Thanks.
Sent from my GT-I9300 using Tapatalk

Sorry, predictive text is rubbish. O2 should read OS and last paragraph I'm a book should read I'm a noob
Sent from my GT-I9300 using Tapatalk

matrixmainframe said:
I was completely stock. Whilst using NRT I believe I had just succeeded in unlocking the Bootloader and the video then stated that with 4.4.3 a Factory reset was required which is what I did but I did not realise that deleted the O2. I thought that was on a protected partition like my S3 phone.
I can't flash the factory image as I can't get into recovery or is there another way of doing it?
I suppose where tablets are concerned I'm a book but if you could point me to any instructions on how to flash manually I'm hoping I can recover my tablet. Thanks.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Dont know how you got your os erased. But im using a custom recovery since I got mine so maybe the stock recovery erses the os when doing a factory reset. A factory image cant be flashed via recovery and must be flashed via fastboot. Its really easy. But it will wipe the entire device. If you dont want to wipe everything you need to edit it..
Sent from my Galaxy Nexus using XDA Free mobile app

Cannot access Recovery Mode. Can Access Download Mode!
mrgnex said:
Dont know how you got your os erased. But im using a custom recovery since I got mine so maybe the stock recovery erses the os when doing a factory reset. A factory image cant be flashed via recovery and must be flashed via fastboot. Its really easy. But it will wipe the entire device. If you dont want to wipe everything you need to edit it..
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
I don't mind wiping the device but I cannot access Recovery Mode. When I select RECOVERY MODE and press the Power button to take me there it just returns me to the START screen.
I don't know if the fiollowing is relevent but it displays the word START vertically in the top left of the screen and next to it
Device Information
Product Name: manta
Variant: wifi
H/W Version: 8
Bottloader Version: MANTAMF01
Carrier Info: None
Serial Number: Don't think I should show that
Lock State: Unlocked
Reboot Mode Flag: None.
I have tried RESTART BOOTLOADER and that brings me back to the Start screen but still cannot access RECOVERY MODE.
Holding down the Power Button and Volume Up/Down brings me back to the Start screen again
I can get into DOWNLOAD MODE
Is there ANY way I can flash anything onto my Nexus 10 without using RECOVERY MODE like using Odin or Heimdall with a Samsung phone?

SORTED
Great news everyone..........well for me that is :laugh:
Thanks to Androidbeat.com I now have a fully operational Nexus 10.
Just in case anyone else was following this I did it by downloading all the necessary files into on folder on my Windows Desktop, opening a Command Prompt from there and followed the instructions.
Thank you to those who offered advice here and although my Nexus 10 is showing itself to be unlocked I think I'll give a miss to rooting it and just suffer the limitations rather than risk bricking it again.

matrixmainframe said:
Great news everyone..........well for me that is :laugh:
Thanks to Androidbeat.com I now have a fully operational Nexus 10.
Just in case anyone else was following this I did it by downloading all the necessary files into on folder on my Windows Desktop, opening a Command Prompt from there and followed the instructions.
Thank you to those who offered advice here and although my Nexus 10 is showing itself to be unlocked I think I'll give a miss to rooting it and just suffer the limitations rather than risk bricking it again.
Click to expand...
Click to collapse
Glad everything worked out for you. Just an FYI for future reference, the stock recovery factory reset does not wipe the OS (at least it shouldn't). By default, AFAIK there are no custom recoveries that will wipe your OS either while doing a factory reset. It must've been something with the toolkit.
Regarding root, it's super easy to get root on this device. All you have to do is download the custom recovery image file of your choice. I prefer Philz, but you can use CWM or TWRP as well. Then, download the latest SuperSU zip file (I believe it's v1.99r4 now). Simply fastboot flash the recovery image, boot into recovery, and install the SuperSU zip, and you're good to go. The whole process takes two minutes, and no toolkit required.

charesa39 said:
Glad everything worked out for you. Just an FYI for future reference, the stock recovery factory reset does not wipe the OS (at least it shouldn't). By default, AFAIK there are no custom recoveries that will wipe your OS either while doing a factory reset. It must've been something with the toolkit.
Regarding root, it's super easy to get root on this device. All you have to do is download the custom recovery image file of your choice. I prefer Philz, but you can use CWM or TWRP as well. Then, download the latest SuperSU zip file (I believe it's v1.99r4 now). Simply fastboot flash the recovery image, boot into recovery, and install the SuperSU zip, and you're good to go. The whole process takes two minutes, and no toolkit required.
Click to expand...
Click to collapse
charesa39 thanks for that. All done so thanks again.