Related
Hi,
I searched the forum but I couldn't find a similar problem, so Please I need some help.
Last week I got the new update 4.1.2 on my Galaxy Nexus gsm, so I went and installed it.
During installation when the device turned off and it was unpacking the update or even a little bit before that, I got a message which I really don't remember very much and didn't understand but i think it was from rom manager asking something maybe about flashing or something similar.
I remember as well, that it said that the action cannot be undone! and since I didn't understand very well what it was asking me, i chose something which seemed to me the safest at the time.
Which means, if it asked me to install something, I chose not to since it can't be undone.
I know I'm not giving as much information as i should but this is what happened.
After the installation was finished, I downloaded root checker to find if i had lost my root or not and it took awfully long time for the app to tell me that my device is rooted.
So, everything was okay and apps which needed root access were getting it from superuser app.
Today I decided to backup my rom so I opened rom manager premium and I was not able to backup the rom or even restart in recovery mode, so i uninstalled it and reinstalled it and I was getting always error that it was not granted superuser access.
So, i figured out that the problem is specifically with the rom manager because other app which needs root access were always getting it, so I went to titanium backup and rebooted through the app into recovery mode and it did but all i got is that black screen with the android icon in the middle having a red triangle on top. I had to take the battery off to restart the phone.
I tried again to reboot into recovery mode using the power and the volume button but I was unable to.
So, I'm asking whats the problem?
Am I still rooted? and how can i fix this problem?
I was thinking of using the nexus kit but I can't reboot in recovery mode at all so I guess it won't be much of a help.
I'm very sorry for the LONG question.
Thanks Guys
clouds73 said:
Hi,
I searched the forum but I couldn't find a similar problem, so Please I need some help.
Last week I got the new update 4.1.2 on my Galaxy Nexus gsm, so I went and installed it.
During installation when the device turned off and it was unpacking the update or even a little bit before that, I got a message which I really don't remember very much and didn't understand but i think it was from rom manager asking something maybe about flashing or something similar.
I remember as well, that it said that the action cannot be undone! and since I didn't understand very well what it was asking me, i chose something which seemed to me the safest at the time.
Which means, if it asked me to install something, I chose not to since it can't be undone.
I know I'm not giving as much information as i should but this is what happened.
After the installation was finished, I downloaded root checker to find if i had lost my root or not and it took awfully long time for the app to tell me that my device is rooted.
So, everything was okay and apps which needed root access were getting it from superuser app.
Today I decided to backup my rom so I opened rom manager premium and I was not able to backup the rom or even restart in recovery mode, so i uninstalled it and reinstalled it and I was getting always error that it was not granted superuser access.
So, i figured out that the problem is specifically with the rom manager because other app which needs root access were always getting it, so I went to titanium backup and rebooted through the app into recovery mode and it did but all i got is that black screen with the android icon in the middle having a red triangle on top. I had to take the battery off to restart the phone.
I tried again to reboot into recovery mode using the power and the volume button but I was unable to.
So, I'm asking whats the problem?
Am I still rooted? and how can i fix this problem?
I was thinking of using the nexus kit but I can't reboot in recovery mode at all so I guess it won't be much of a help.
I'm very sorry for the LONG question.
Thanks Guys
Click to expand...
Click to collapse
Try to flash recovery through fastboot from PC
polimeno said:
Try to flash recovery through fastboot from PC
Click to expand...
Click to collapse
Thanks for the answer.
Flashing recovery using what exactly? Gnexus Kit?
clouds73 said:
Thanks for the answer.
Flashing recovery using what exactly? Gnexus Kit?
Click to expand...
Click to collapse
Yeah, Galaxy nexus toolkit will work fine. You can also download the recovery (it is a .img file) and flash it manually through fastboot (fastboot flash recovery recoveryname.img)
Hello Everybody,
I habe a really big Problem with my GNex.
Today I Copied some Files over to my PC. For this I used for the first time "USB Mass Storage". Because I haven't seen some Files wich i can see under my Phone.
It worked really good. I unplugged my phone and to my things. Some minutes later i Heared the "Pling" from superuser. Then my phone was really slowly and need a bunch of time only to open the Launcher. So i deactivated Superuser. Deinstalled USB Mass Storage and MyMobiler.
After this i rebooted my Phone 2 times and the lag on my screen was gone. But now i'm unable to Access the Device under Android booted as MTP.
Even after reinstalling USB Mass Storage i'm unable to Access the Device via MTP or Mass Storage. My Windows PC and Android don't says anything. My Device is only Loading.
So i Unlocked my Bootloader with "BootUnlocker" and updated my System with offical Google Update 4.2 "fastboot update image-yakju-jop40d.zip" .
But i cann't access my Device now. Only fastboot is working.
So i'm unable to backup all my data and do an Factory Reset.
Have anyone out there an Suggestion how i can fix this Problem.
My Device:
Galaxy Nexus
Stock: 4.2
BL: Unlocked
Root: No Root (But with BL unlocked should this be the smallest problem.
Best regards and Thanks
Chris
P.s Sorrry for the really bad English
P.s.s Fastboot is working ... so it don't seems like an HW error
The nexus doesn't have use mass storage
Sent from my Galaxy Nexus using Tapatalk 2
This point i know, thats why i used the App.
But how can i aceess my Phone with MTP?
It's not even reconigzed under Windows ... and Android also don't set an Logo which tells that USB is Connected.
Chris302 said:
This point i know, thats why i used the App.
But how can i aceess my Phone with MTP?
It's not even reconigzed under Windows ... and Android also don't set an Logo which tells that USB is Connected.
Click to expand...
Click to collapse
have you tried a different usb chord?
simms22 said:
have you tried a different usb chord?
Click to expand...
Click to collapse
Yes i tried another USB-Cord.
Same thing -> Phone is Charging but not resposing over ADB.
And also i can't see it in the Explorer.
Same thing at my GF PC (Win Vista)
are you trying to use adb in the bootloader? if so, that will never work. ever.
Zepius said:
are you trying to use adb in the bootloader? if so, that will never work. ever.
Click to expand...
Click to collapse
No i'm using Fastboot when i was in BL to confirm that i have no HW error.
I try to ADB when i booted my Phone.
Or to access the My Device via Explorer
Have you tried removing and re-installing the drivers from your PC?
Have you checked the Android SDK to see if there is a 4.2 specific version of adb?
danger-rat said:
Have you tried removing and re-installing the drivers from your PC?
Have you checked the Android SDK to see if there is a 4.2 specific version of adb?
Click to expand...
Click to collapse
I Don't think hat There is my Problem, because under Windows i can Not even See my device it is not even recognized.
I can test driver uninstalling but i can not see my device under the device manager
:/ it seems like my android is f****ed up because root is also not working :/
When you update to a stock image you over write your/system partition (which is where you enabled root access) - that is most likely how you lost root access.
Also, since you updated your device, it is possible that your PC no longer sees it as the same device, which is why I suggested removing and reinstalling the driver...
danger-rat said:
When you update to a stock image you over write your/system partition (which is where you enabled root access) - that is most likely how you lost root access.
Also, since you updated your device, it is possible that your PC no longer sees it as the same device, which is why I suggested removing and reinstalling the driver...
Click to expand...
Click to collapse
I want to clear some things.
Don't think i want to shame you, i really thankfull for your help . Also it is the Best forum for Android Development and everything around it wo i have ever seen.
I was always on Stock. I updated the Offical 4.2 to 4.2 with an Stock image, it is now working again, i think the Update cleaned the Things up. Only Thing (shame me) i have forgotten to check after update is under-> settings -> storage -> Menu -> USB-Connection -> and check there "MTP".
So now my Device says connecting as "MTP" and my PC also recognize it again.
Before that my Device don't even say connecting as MTP.
I know that i will loose root when i update my Device -> but with my unlocked BL I just Booted to CWM and flashed Superuser.
Maybe (i hope) you are willing to help me again.
I am unable to update my SU binary and also i dont see a Message from Superuser, where i can allow Root access.
Even if i set under Settings -> Security -> Automated Answer -> "Allow"
I don't see the Message where i can say "allow" to Root access. I cannot even install SuperSU.
Have you any idea why it seems like i cannot access Root. For me it's seems like my app's don't recognize root.
When i Start SuperSu he says "Su-binary" must be updated" and next step is "Installation failed".
Have you any Idea where this came from?
But the good thing is at this point i'm abel again to access my Device via Explorer Thank you really really much for your Help You can't belive how glad i'm not to do a Factory reset and loose all my data.
Thank oyu for your great help
Chris
P.s. Root is working from Shell
Please read forum rules before posting
Questions and issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Okay i will read the Rules again.
Thank you for moving the Thread.
I hope in the right section someone can tell my why my Root isn't working ?
P.s. or should i make a new thread for that problem ?
Chris302 said:
Okay i will read the Rules again.
Thank you for moving the Thread.
I hope in the right section someone can tell my why my Root isn't working ?
P.s. or should i make a new thread for that problem ?
Click to expand...
Click to collapse
Use SuperSu instead of Superuser.
Sent from my i9250
bk201doesntexist said:
Use SuperSu instead of Superuser.
Sent from my i9250
Click to expand...
Click to collapse
Sorry for the long delay.
I had no time to check this thread. And also my Email Notification hasen't worked.
So I hope you still look at this and can also suggest something.
I tried SuperSU but supersu says.
He need to install the Binaries.
After roundabout 15 seconds i get an Error message which says: "Installation failed".
My Super user tells me that the Binary is outdated.
And i get this Error Message in SuperSU even when i say "Answer every Permission Request with Allow".
I Even tried to remount the System as RW and the say update. But Both of them Seems to fail to install the Binary.
I flashed Superuser Through Temp Booted CWM.
Is their another Zip that i can try ?! or have i done something wrong while Flashing ?
Or can i theoretically flash SuperSU through CWM and then get Root Access?
Thank you for your help
Chris
Chris302 said:
Or can i theoretically flash SuperSU through CWM and then get Root Access?
Thank you for your help
Chris
Click to expand...
Click to collapse
Correct; you will be rooted again. Just boot a custom recovery and flash.
Sent from my i9250
bk201doesntexist said:
Correct; you will be rooted again. Just boot a custom recovery and flash.
Sent from my i9250
Click to expand...
Click to collapse
Hello
And again a dumb question.
Could you please provide me a download link for a zip. Which is working under 4.2 ?
I have seen zip's around for Superuser but not for SuperSU.
An i only Mention that maybe Superuser have a Problem with 4.2 but i cannot Prove it.
Thanks again
Chris :]
Sent from my ASUS Transformer Pad TF300T using xda app-developers
oasad92 said:
Yeah SuperSU should do the trick
Click to expand...
Click to collapse
Thank you for the Reply.
But how i have written 2 post ago. SuperSU also did not work.
He keeps saying "Installation Failed" thats why i asked for an Flashable Version which is working under 4.2.
I recently reverted back to stock 4.2.1 (just to try it)
My Win7 computer was unable to see my phone when connected in MTP mode. Nothing showed in the computer at all, However when I selected PTP I could acess the DCIM folder.
In the end I couldn't be F**Ked with it so I pushed a custom rom to data/media/ and every thing was normal again.
I spoke to a friend who had the same issue I had, and he just enabled debugging (which a custom rom has enabled by default) to solve the issue.
Chris302 said:
Hello
And again a dumb question.
Could you please provide me a download link for a zip. Which is working under 4.2 ?
I have seen zip's around for Superuser but not for SuperSU.
An i only Mention that maybe Superuser have a Problem with 4.2 but i cannot Prove it.
Thanks again
Chris :]
Sent from my ASUS Transformer Pad TF300T using xda app-developers
Click to expand...
Click to collapse
oasad92 said:
Yeah SuperSU should do the trick
Click to expand...
Click to collapse
I have not tried Superuser again since Chainfire released Supersu and all those issues rose with JB.
Chris302 said:
Thank you for the Reply.
But how i have written 2 post ago. SuperSU also did not work.
He keeps saying "Installation Failed" thats why i asked for an Flashable Version which is working under 4.2.
Click to expand...
Click to collapse
http://www.google.co.uk/search?q=xd...&sugexp=chrome,mod=0&sourceid=chrome&ie=UTF-8
would take you to:
http://forum.xda-developers.com/showthread.php?t=1538053
flash that
p.s: on the supersu thread says you need to be rooted... for us, of course, it's not quite true, rather we need unlocked bootloader and custom recovery.
I followed a utube instruction to route Nabi 2 however I ran into a problem with keyboard, the error message that came up is: "Unfortunately, Android keyboard has stopped". I could not enter any text. At this point I was in child mode and could not get access to Mommy mode to allow me to change settings. I decided to do a factory reset thinking it would clear keyboard error...it didn't. When you do a factory reset it brings you to set-up screen that needs text entry which I cant do. I've been advised to return it to stock but when I try run the return to stock zip file (filed is called fuhu_nabi2_back_to_stock_from_scratch) via SD card it comes up with this message:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Any help with this would be appreciated.
Thanks
Virgil
vpporter said:
I followed a utube instruction to route Nabi 2 however I ran into a problem with keyboard, the error message that came up is: "Unfortunately, Android keyboard has stopped". I could not enter any text. At this point I was in child mode and could not get access to Mommy mode to allow me to change settings. I decided to do a factory reset thinking it would clear keyboard error...it didn't. When you do a factory reset it brings you to set-up screen that needs text entry which I cant do. I've been advised to return it to stock but when I try run the return to stock zip file (filed is called fuhu_nabi2_back_to_stock_from_scratch) via SD card it comes up with this message:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Any help with this would be appreciated.
Thanks
Virgil
Click to expand...
Click to collapse
Not sure which technique you used to root. Did you also install the Google play store? If so, it sounds like you installed the wrong gapps.
I would boot to twrp and install the 1011 gapps.
Sent from my One X using xda app-developers app
NABI 2 Keyboard Problem
GuyIncognito721 said:
Not sure which technique you used to root. Did you also install the Google play store? If so, it sounds like you installed the wrong gapps.
I would boot to twrp and install the 1011 gapps.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Hi There,
Unfortunately I can only get to the Nabi Set-up screen. I can't get to the TWRP screen. I can't enable developers options (USB Debugging) as I cant get into the device (This I think is the biggest problem as I cant see the NABI through PDA net and can run any recovery apps from SD as developer option is not enabled). I seem to be stuck in a loop and not sure where to go from here!
Any help or thoughts much appreciated.
Thanks
Virgil
vpporter said:
Hi There,
Unfortunately I can only get to the Nabi Set-up screen. I can't get to the TWRP screen. I can't enable developers options (USB Debugging) as I cant get into the device (This I think is the biggest problem as I cant see the NABI through PDA net and can run any recovery apps from SD as developer option is not enabled). I seem to be stuck in a loop and not sure where to go from here!
Any help or thoughts much appreciated.
Thanks
Virgil
Click to expand...
Click to collapse
Turn off the device. Power on the device by holding the power and volume up. At the option menu press volume down to get to recovery kernel and press volume up. This will get you to twrp.
Sent from my One X using xda app-developers app
GuyIncognito721 said:
Turn off the device. Power on the device by holding the power and volume up. At the option menu press volume down to get to recovery kernel and press volume up. This will get you to twrp.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Hi,
Thanks for that. I now have access to TWRP and though I would be OK. However when I try to install GAPPs or a Keyboard zip file it continuallys comes up with this error:
E: Unable to mount '/data' (tw_mount)
E: failed to mount /data (Invalid argument)
E: failed to mount /data (Invalid argument)
Any thoughts on this one? It seems to be related to SD card but I have tried a couple to no avail. Can the tablet reject SD cards?
THanks again for your help.
Virgil
vpporter said:
Hi,
Thanks for that. I now have access to TWRP and though I would be OK. However when I try to install GAPPs or a Keyboard zip file it continuallys comes up with this error:
E: Unable to mount '/data' (tw_mount)
E: failed to mount /data (Invalid argument)
E: failed to mount /data (Invalid argument)
Any thoughts on this one? It seems to be related to SD card but I have tried a couple to no avail. Can the tablet reject SD cards?
THanks again for your help.
Virgil
Click to expand...
Click to collapse
have you tried going into the MOUNT sub-menu and trying to mount the data partition?
Sent from my One X using xda app-developers app
GuyIncognito721 said:
have you tried going into the MOUNT sub-menu and trying to mount the data partition?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Hi There,
That seemed to work and I now have GAPPS installed and the keyboard working. Unfortunately the only problem remaining is that Wi-Fi is not working. It previously seen my Wi-Fi connection point and now it will not turn on i.e. I try to switch on Wi-Fi but it keeps going back to the Off position? Very strange. I'm on Android 4.0.4 and have tried the change in Mammy and Daddy mode! I appreciate your help with this and don't want to take up your time so I may post this issue under a new heading.
Thanks again for all your help and giving me the solution.
V
vpporter said:
Hi There,
That seemed to work and I now have GAPPS installed and the keyboard working. Unfortunately the only problem remaining is that Wi-Fi is not working. It previously seen my Wi-Fi connection point and now it will not turn on i.e. I try to switch on Wi-Fi but it keeps going back to the Off position? Very strange. I'm on Android 4.0.4 and have tried the change in Mammy and Daddy mode! I appreciate your help with this and don't want to take up your time so I may post this issue under a new heading.
Thanks again for all your help and giving me the solution.
V
Click to expand...
Click to collapse
Hope you updated the tablet software to 1.9.37 before you did everything or you will be starting over from scratch
Sent from my cm_tenderloin using xda app-developers app
When I first rooted mine, probably some time in late Feb the consensus seemed to be to install the latest OTA software upgrade before rooting in order to avoid WiFi problems. I did this and I have not had WiFi problems. Just recently there has been yet another software and interestingly the bullet point summary of what has changed claims fixes for WiFi issues.
To install the upgrade from the rooted state you need to:
* Use the TWRP recovery to restore the backup you took when rooting to return the main OS to stock.
* Use adb fastboot flash to restore the original recovery.
* Boot normally, connect to WiFi, parent mode, settings/about/update and download/install the update.
[The OTA update works by downloading a file which is then installed by the stock recovery in a reboot cycle.]
* Use adb fastboot flash to flash TWRP recovery.
* Use TWRP recovery to backup the latest stock, install root.zip and gapps.zip.
There is more than one version of TWRP and I found the older one worked for me and the newer one had touch screen problems but you may find otherwise. The various versions are discussed here: http://forum.xda-developers.com/showthread.php?t=2074501
HELP
GuyIncognito721 said:
Hope you updated the tablet software to 1.9.37 before you did everything or you will be starting over from scratch
Sent from my cm_tenderloin using xda app-developers app
Click to expand...
Click to collapse
I see you helped this other person and hope you can me too. I like they did, followed the youtube video on how to root and install google play. It worked great when I did this last year on my kids nabi. I tried to do it again this year with a friends and kinda fell into a hole. My keyboard stopped work as well. I went back and tried to fix it by putting the gapps 1011. Well I didnt delete the old one (didnt know how) and now I cant get into TWRP. I have tried getting the recovery kernal and now when I push vol + it starts to load then gives me the dead android guy. Any suggestions on how to fix this. I sure hope so. Thanks
vpporter said:
I followed a utube instruction to route Nabi 2 however I ran into a problem with keyboard, the error message that came up is: "Unfortunately, Android keyboard has stopped". I could not enter any text. At this point I was in child mode and could not get access to Mommy mode to allow me to change settings. I decided to do a factory reset thinking it would clear keyboard error...it didn't. When you do a factory reset it brings you to set-up screen that needs text entry which I cant do. I've been advised to return it to stock but when I try run the return to stock zip file (filed is called fuhu_nabi2_back_to_stock_from_scratch) via SD card it comes up with this message:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Any help with this would be appreciated.
Thanks
Virgil
Click to expand...
Click to collapse
Uncheck signature enforcement or whatever it's called in TWRP?
Rooted Nabi JR with wrong Root
I have been working on my step-sons nabi for a week now. I rooted three Tabeos fine but then i thought i could do the Nabi JR and it would go perfect...i was wrong. I accidently rooted it with the same package for the Tabeo and now when i boot it up the keyboard forces close and i cant do anything. I can not get to daddy mode, can not usb debug. there is no TPK or whatever installed to boot with. Im at a loss, all i can do is load from usb in the stock bootload menu but i cant seem to get it to work. I need help please...i voided the warranty and now he has no nabi! this is also the Nick JR version of the Nabi, i cant be sure what else is in it considering im stuck at the enter daddy password and no keyboad...
d.marie.1490 said:
I have been working on my step-sons nabi for a week now. I rooted three Tabeos fine but then i thought i could do the Nabi JR and it would go perfect...i was wrong. I accidently rooted it with the same package for the Tabeo and now when i boot it up the keyboard forces close and i cant do anything. I can not get to daddy mode, can not usb debug. there is no TPK or whatever installed to boot with. Im at a loss, all i can do is load from usb in the stock bootload menu but i cant seem to get it to work. I need help please...i voided the warranty and now he has no nabi! this is also the Nick JR version of the Nabi, i cant be sure what else is in it considering im stuck at the enter daddy password and no keyboad...
Click to expand...
Click to collapse
Which Nabi JR? There are 2 versions. 4GB with tegra 2, or 16GB with tegra 3. Makes a difference in how we can help you. Probably need to put TWRP on device and restore a stock ROM. Then use TWRP to root it.
are the ROMs out there? I didn't see anything on the wiki page
http://forum.xda-developers.com/wiki/Fuhu_nabi_Jr
I have to admit though, I don't follow the Jr very much, so for all I know the ROMs are all over the place.
need to fix nabi JR
how can i get twrp without entering debug mode..i cant even get into the nabi to get debug on...i can only access bootloader
aicjofs said:
Which Nabi JR? There are 2 versions. 4GB with tegra 2, or 16GB with tegra 3. Makes a difference in how we can help you. Probably need to put TWRP on device and restore a stock ROM. Then use TWRP to root it.
Click to expand...
Click to collapse
2girlzdad said:
are the ROMs out there? I didn't see anything on the wiki page
http://forum.xda-developers.com/wiki/Fuhu_nabi_Jr
I have to admit though, I don't follow the Jr very much, so for all I know the ROMs are all over the place.
Click to expand...
Click to collapse
I think the 16GB tegra 3 is posted. Maybe the TWRP thread? Can't remember. Mr. Karz usually helps people that need the Nabi JR 4GB tegra 2. I think I have both ROM's but they aren't my creation and I don't have the devices to test so I don't post them.
d.marie.1490 said:
how can i get twrp without entering debug mode..i cant even get into the nabi to get debug on...i can only access bootloader
Click to expand...
Click to collapse
You would use fastboot to flash TWRP from the bootloader. That's why I asked which Nabi you have. 2 different TWRP versions, and the tegra3 version has a locked bootloader, so you have to wipe the device to unlock the bootloader to install TWRP.
break it down for me
can you break that down on how i do that. i deleted everything out of it its in stock but keyboard does not work to access anything, i know its still rooted but i dont know how to fix it.
aicjofs said:
I think the 16GB tegra 3 is posted. Maybe the TWRP thread? Can't remember. Mr. Karz usually helps people that need the Nabi JR 4GB tegra 2. I think I have both ROM's but they aren't my creation and I don't have the devices to test so I don't post them.
You would use fastboot to flash TWRP from the bootloader. That's why I asked which Nabi you have. 2 different TWRP versions, and the tegra3 version has a locked bootloader, so you have to wipe the device to unlock the bootloader to install TWRP.
Click to expand...
Click to collapse
Hey guys, this is my last attempt to fix my sons nabi. It has the same issues as the original poster. I basically cant get anything to work on it.
GuyIncognito721 said:
Turn off the device. Power on the device by holding the power and volume up. At the option menu press volume down to get to recovery kernel and press volume up. This will get you to twrp.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
When I follow these steps it goes to the android with the red exclamation point. I can't access the Nabi with my laptop. only a sd card. Is there anything I can do to save this thing? Thanks to anyone with advice and sorry for the thread necro but it was relevant.
nitetimemc said:
Hey guys, this is my last attempt to fix my sons nabi. It has the same issues as the original poster. I basically cant get anything to work on it.
When I follow these steps it goes to the android with the red exclamation point. I can't access the Nabi with my laptop. only a sd card. Is there anything I can do to save this thing? Thanks to anyone with advice and sorry for the thread necro but it was relevant.
Click to expand...
Click to collapse
What version of the Nabi software were you on? Was the tablet stock or had you rooted it, gapps, etc? Can you boot Android but just the keyboard doesn't work? Or are there more issues besides the keyboard. Are your just trying to fix the one problem or are you trying to wipe the device and start fresh?
Likely you will need to get TWRP on the tablet, or at least be able to boot to TWRP. Answer those questions and I can have a better idea of what we can do.
aicjofs said:
What version of the Nabi software were you on? Was the tablet stock or had you rooted it, gapps, etc? Can you boot Android but just the keyboard doesn't work? Or are there more issues besides the keyboard. Are your just trying to fix the one problem or are you trying to wipe the device and start fresh?
Likely you will need to get TWRP on the tablet, or at least be able to boot to TWRP. Answer those questions and I can have a better idea of what we can do.
Click to expand...
Click to collapse
The Nabi wouldn't take the latest update and it was apparently rooted to gain access to the google play store. It now appears the OS and everything else has been erased. I told my wife I would take a look at it and I immediately regret that decision, this is beyond my scope.
The only thing i have been able to access is the android screen which gives me access to the sd card. My laptop does not recognize it. I found this thread after a lot of searching and reading, some of the nabi threads are insanely long, and when I googled 'signature verification failed' to see if I could find someone stuck at the same point I am,
"I've been advised to return it to stock but when I try run the return to stock zip file (filed is called fuhu_nabi2_back_to_stock_from_scratch) via SD card it comes up with this message:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Any help with this would be appreciated.
Thanks"
Everything I have tried to run from the sd has returned this message. There's no keyboard, there's only the android screen. Anything else I try to do just freezes it. I was hoping to get it back to stock and let it update itself. So I guess the first thing I need to do I figure out how to get twrp on it.
Hi, I recently got ATT note 2. I tried to root it and did the CF root from chainware and also tried galaxynote2root.com root. both didnt work, well it gave me root but I cant install a recoveery. I flashed it multiple times like 10 I think because my binary coutner says 10. idk what to do.Can someone help. plz post links if i need to download something. I do have all the drivers and stuff. its just that no recovery. im running 4.1.2 jelly bean
Not in any way am I trying to be rude or condescending. ...but
You need to stop and read the steps again. ...before you accidentally do damage to the device partitions or worse. ..
Custom recovery images are pushed to the device via Odin when the stock recovery still exists. ...and if done incorrectly. ..you can brick the device.
Please explain the method you are using to attempt the recovery flash. .and we can help correct the problem.
But by all means. ..don't attempt another flash of recovery until the problem is found.
Recovery is essential to do exactly as the term states. ..."recovery"...and without it. ..you will be in trouble with no way back but JTAG service.
Read and read again the recovery steps. ..and go slow here...
Your on the edge at the moment....g
gregsarg said:
Not in any way am I trying to be rude or condescending. ...but
You need to stop and read the steps again. ...before you accidentally do damage to the device partitions or worse. ..
Custom recovery images are pushed to the device via Odin when the stock recovery still exists. ...and if done incorrectly. ..you can brick the device.
Please explain the method you are using to attempt the recovery flash. .and we can help correct the problem.
But by all means. ..don't attempt another flash of recovery until the problem is found.
Recovery is essential to do exactly as the term states. ..."recovery"...and without it. ..you will be in trouble with no way back but JTAG service.
Read and read again the recovery steps. ..and go slow here...
Your on the edge at the moment....g
Click to expand...
Click to collapse
well first i downloaded the galaxynote2root zip file from the website. it gave the odin and a file to flash. then I put phone in download mode and flashed. successfully got root. I think its because I have the latest software. 4.1.2 everyone got root in 4.1.1 and the old one doesnt work anymore. what did u use to root.? I did all the steps exactly what max did. and he got root like that and installed cwm. i followed video and blog post. this is the video : http://www.youtube.com/watch?v=NFHZ535L7is
Is it better to use the toolkit that to use this method? toolkit users have had less problems.
ALSO NOW ITS DOWNLOADING SOME UPDATES WHEN I CONNECT TO WIFI. im already rooted so does that mean im going to brick if i update so im not even using the phone now plzz someone help me
thanks for reply
FIRST thing you need ro do is check and make sure you have a recovery.
Imo the number one reason noobs break there phones is with out realizing it they borked their recovery and try to root , flash a custom rom, OR take an ota.
No recovery = no ota or any other flashing.
Check you recovery by:
Power off> press vol up, menu, and home.
This is done all at once. As soon as you see the text appear in the top right corrner release. It takes a bit of practice but its not a biggie.
Now.. do you see recovery or are you in a boot loop?
If you have a boot loop while trying to get into recovery...it means u no have recovery!!!
Secondly Stop flashing root!!
Lol pick a single root method that has been verified to work by others. And stick to it.
Its sooo important to read.
In fact with some phones one variant of root wont work if you have an update and hence a different android version.
So you need to read.
If you have recovery click factory restore.
You can do this from the os or.. I prefer going into recovery and hitting factory restore. iTS THE SAME.
If you have a boot loop while trying to get into recoveru
Click my signature in web view.
Go do the kies efr thing as I explain it my tut. Get your phone back to a nice clean start.
Kies efr IS THE FASTEST AND SAFEST way for newbs to get back to stock.
Newbs should NOT be using odin unless they are 100% sure they know what they are doing and are comfortable doing so. My efr tutorial in my sig will teach you how to use KIES EFR (Emergency Firmware Recovery)
I prefer to send people the gn2 toolkit.
Its easy and also has plenty of options.
Just remember to uninstall kies first.
There are numerous ways to root.
Pick one. Lol.
sent from my T.A.R.T.I.S
(Time And Relative Tarts In Space)
Freakboy hit it on the head...
I won't try to add more into the responses, as this will just confuse the issue more...
Follow his lead, and his advice.....g
ok thanks a lot, i flashed twrp recovery now running jellybam rom, i was wondering if it supports transparent status bar? not just in one app in all of them.
The answer to that question is found in the respective thread for the rom you are using. .
Check there first. ...
General searches also yield great results. ...g
im going to switch to pac man rom soon, bc xda banned jellybam for not giving credits i think. anyway whats a good kernel to use? now im using the one that came with jellybam. im guessing u experminented a lot and give me some suggestions. i dont wanna overclock just looking for smooth performance.
For pac.....
Use the preloaded kernel ..
It is optimized for the build and you can get support ...
If you change kernels ...you may not get support ...g
Hello,
New to the forums, I've come across a Nexus 5X that has got me stumped. I haven't had to create and post on xda-developers before because I could always find a solution. But this phone...I've even got the book (xda-developers Android Hackers Toolkit)
So I needed a Nexus 5 for a project. I went to ebay and ordered one from China/Hong Kong.
I've got TWRP installed but the device asks for a password. I've tried different versions of twrp. in the more recent version TWRP asks for a password. In earlier versions it just runs a script and reboots.
I cannot yet post links to images, being a new member.
I'm not sure what I'm doing wrong. I can run fastboot oem unlock and unlock the device. Then, if I try and flash a stock good android Nexus ROM the bootloader locks itself and reboots.
Is there something obvious I am missing? I just want to wipe the phone and install a stock nexus ROM. It's like the people who sold it have it loaded with something the prevents the phone from being wiped/modified.
I've never come across an Nexus phone that I couldn't wipe. I don't care about the data on the phone. I cannot securely use a phone if I cannot wipe it first. I can get to the bootloader and TWRP recovery. But there is no
point with TWRP because when it prompts for a password and I click cancel it runs a script, reboots and then locks the bootloader again.
Thanks
internetdenizen said:
Hello,
New to the forums, I've come across a Nexus 5X that has got me stumped. I haven't had to create and post on xda-developers before because I could always find a solution. But this phone...I've even got the book (xda-developers Android Hackers Toolkit)
So I needed a Nexus 5 for a project. I went to ebay and ordered one from China/Hong Kong.
I've got TWRP installed but the device asks for a password. I've tried different versions of twrp. in the more recent version TWRP asks for a password. In earlier versions it just runs a script and reboots.
I cannot yet post links to images, being a new member.
I'm not sure what I'm doing wrong. I can run fastboot oem unlock and unlock the device. Then, if I try and flash a stock good android Nexus ROM the bootloader locks itself and reboots.
Is there something obvious I am missing? I just want to wipe the phone and install a stock nexus ROM. It's like the people who sold it have it loaded with something the prevents the phone from being wiped/modified.
I've never come across an Nexus phone that I couldn't wipe. I don't care about the data on the phone. I cannot securely use a phone if I cannot wipe it first. I can get to the bootloader and TWRP recovery. But there is no
point with TWRP because when it prompts for a password and I click cancel it runs a script, reboots and then locks the bootloader again.
Thanks
Click to expand...
Click to collapse
"bootloop_after_lg_replaced_mainboard_bootloader reddit"
google it
https://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
This is the droids guide you are looking for...
Hope this helps anyone else who lands here with the same issue.
First sorry my bad english. I guess you took wrong way.
I suggested safety and easy solution. TWRP needs password due to encrypted data partition.
If you can format userdata,TWRP require no password and you can flash any Rom.
I wish you success with your way.
Thank you for your reply.
I am following the instructions here; https://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
I am stuck at the google logo. The bootloader is locked and I cannot unlock it because I cannot get the system up to enable developer tools and allow unlocking.
I don't really know what else to do.
The last resort
h ttps://ja.aliexpress.com/item/32846103543.html?spm=a2g0o.cart.0.0.74743c004Bny1g&mp=1
There is no longer anything that I can do for that.
I've managed to recover the phone using a combination for LGUP + tot files and sideloading an OTA from google.
I want to turn off encryption though... not sure how to do that..
Can you manage bootloader unlock?
O.K. following the tut of reddit thread and use fastboot tool this ver.
h ttps://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader/
h ttps://androiddatahost.com/265a2
Hiroki.S said:
Can you manage bootloader unlock?
O.K. following the tut of reddit thread and use fastboot tool this ver.
h ttps://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader/
h ttps://androiddatahost.com/265a2
Click to expand...
Click to collapse
I've tried to follow the reddit instructions. There are some missing files in the instructions where he links to xda-developers https://forum.xda-developers.com/nexus-5x/general/modified-boot-imgs-android-n-t3495169
The files are not available. Same goes with Magisk Compatible phh's SuperUser not being available
Thank you though for taking the time to try and help me
h ttps://forum.xda-developers.com/nexus-5x/general/modified-boot-imgs-android-n-t3495169/page17
Hiroki.S said:
h ttps://forum.xda-developers.com/nexus-5x/general/modified-boot-imgs-android-n-t3495169/page17
Click to expand...
Click to collapse
I have that boot img and tried to flash it but nothing happens.. The phh-superuser-magisk is marked as obsolete here -> https://forum.xda-developers.com/apps/magisk/magisk-phh-s-superuser-android-pay-t3435921
thanks mate
Majisk latest
Probably no problem
Hi mate,
I managed to flash TWRP. I booted into TWRP and selected to keep the system read only. I then used 'adb push' to push Magisk to the SDCARD and successfully flashed Magisk. I can boot back into the system and I have root access. Where do I go from here? I would like to install a custom ROM
thanks mate.
OK.
So. I installed Magisk successfully. I setup the phone and rebooted into recovery. It no longer asks for a password. I was able to push a custom ROM to the SDCARD and flash using TWRP.. I have learned alot about android and the 5X in just a couple of days.
Thanks
internetdenizen said:
OK.
So. I installed Magisk successfully. I setup the phone and rebooted into recovery. It no longer asks for a password. I was able to push a custom ROM to the SDCARD and flash using TWRP.. I have learned alot about android and the 5X in just a couple of days.
Thanks
Click to expand...
Click to collapse
Everyone goes through the same thing.
Cheers.