So, last night I decided to update to one of the CM 10.1 nightlies. I haven't updated in a while and thought why the heck not? So I used the option built in the Settings app to update. I pressed download and waited for it to finish, then hit install and went to sleep while it installed. When I woke up I had no signal. Not even 2g. No calls, texts, data, you name it. Gone.
So I have spent at least 6 hours re installing old versions and scouring the internet and no one has an issue exactly like mine.
Here's a screenshot of what the settings look like:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This might be an obvious question but have you tried reflashing one of the available modems?
JBeXX said:
This might be an obvious question but have you tried reflashing one of the available modems?
Click to expand...
Click to collapse
Thanks for the quick reply. No I haven't tried that yet actually. I can't find anything on google. Could you point me in the direction to flashing a modem?
Lepryy said:
Thanks for the quick reply. No I haven't tried that yet actually. I can't find anything on google. Could you point me in the direction to flashing a modem?
Click to expand...
Click to collapse
Just flash in recovery. Probably best to use the newer which is the VRALL4. If this doesn't fix it you may want to try a clean flash with a full wipe.
http://forum.xda-developers.com/showthread.php?t=2108510
JBeXX said:
Just flash in recovery. Probably best to use the newer which is the VRALL4. If this doesn't fix it you may want to try a clean flash with a full wipe.
http://forum.xda-developers.com/showthread.php?t=2108510
Click to expand...
Click to collapse
Wait why would I use the VRALL4 and not the VRALLJB?
Lepryy said:
Wait why would I use the VRALL4 and not the VRALLJB?
Click to expand...
Click to collapse
It's the newer of the 2. It was part of the first vzw ota after release.
JBeXX said:
It's the newer of the 2. It was part of the first vzw ota after release.
Click to expand...
Click to collapse
Alright, here goes nothing. I'll post back the results.
JBeXX said:
It's the newer of the 2. It was part of the first vzw ota after release.
Click to expand...
Click to collapse
Umm. So it seems this update did a lot more than mess up my data. It completely wiped my Recovery and removed my Play Store completely. I have no way to even flash this modem.
Lepryy said:
Umm. So it seems this update did a lot more than mess up my data. It completely wiped my Recovery and removed my Play Store completely. I have no way to even flash this modem.
Click to expand...
Click to collapse
Very odd. What recovery were you using? I'm not on cm 10.1 so I'm not familiar with the updater but did it give you options to wipe any data or caches? And did you reflash gapps after updating?
If you can get a wifi connection you could always try and flash TWRP through the goo manager app. Just a thought.
JBeXX said:
Very odd. What recovery were you using? I'm not on cm 10.1 so I'm not familiar with the updater but did it give you options to wipe any data or caches? And did you reflash gapps after updating?
If you can get a wifi connection you could always try and flash TWRP through the goo manager app. Just a thought.
Click to expand...
Click to collapse
I get an error when using the goo manager app. It says no current recovery installed. I am seriously ****ing stuck. Just one harmless update has demolished all the stuff on my phone.
Lepryy said:
I get an error when using the goo manager app. It says no current recovery installed. I am seriously ****ing stuck. Just one harmless update has demolished all the stuff on my phone.
Click to expand...
Click to collapse
You should be able to install recovery from the goo app. Open the all, then hit menu, then install openrecoveryscript. Confirm and see if will flash it.
Had this problem many of times on a gs3.
Calm down, I may be able to help you.
In the settings picture you posted. The my phone number was out of sight.
If the spot said Unknown.
You may be in luck.
But anyways do this either way.
Make sure you back up any thing you don't want to lose.
Boot into download mode.
Flash a stock unrooted official version. I believe this will also flash the modems and radio as well.
Check your signal and phone settings now.
I would expect nothing has changed signal wise.
But if you still have problems you open up dialer and call this phone number
*2767*3855#
Now your phone will cook up some magic and everything will be like the day you opened the box
However if this does not work, I would consider a new sim card (free at Verizon), try and do some more research
Or accept the fact you may have a hardware problem.
Feel free to pm me to let me know how it goes.
God bless the American people.
Related
Read all instructions before beginning.
THIS IS NOT A GUIDE TO ROOTING, OR FOR DOWNGRADING TO .33 FROM ICS.
0. link a google account with your tablet if you have recently done a factory reset.
slayer69 said:
1. Extract the update zip on your computer.
2. Find the zip file in the extracted folders.
3. Copy that file to the root of your sd card.
4. Reboot.... Zip file will be detected after reboot.
5. . 33 update will install.
Click to expand...
Click to collapse
jfortier777 said:
Just to be clear...
You are downloading UpdateLauncher_US_epaduser8_8_3_33.zip
at
http://usa.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_Prime_TF201/#download
and extracting US_epad-user-8.8.3.33.zip
Then placing it in REMOVABLE/MICROSD/US_epad-user-8.8.3.33.zip
and then just reboot or wait for the system prompt and it will install .33
Click to expand...
Click to collapse
slayer69 said:
6. After reboot re root
7. Then use root keeper to save root
8. Install ics and enjoy.
9. Once done use root keeper to gain root again
10. Use root checker to verify
Click to expand...
Click to collapse
Thanks to everyone who helped sort this out and make sense of it.
I never new bloatware could be so dangerous.
DO NOT DELETE BLOATWARE IF YOU WANT TO RECEIVE OTA UPDATES IN THE FUTURE
kristovaher said:
Damn OP for making me think that unrooted people are also having update problems. I was panicking when I read through the first pages of this thread.
Nothing to worry about when you don't root and don't delete system apps.
Click to expand...
Click to collapse
My sincere apologies. *I did not want to garner any undue hostility to jcase or viperboy as the Root process was not at fault in any way.
It was only what we all happened to do once we had it. (deleting bloatware)
If you arent sure where the update goes after all this...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Below maintained for archive only:
3 attempts so far and each time after the firmware downloads and the prime reboots, right after the Android with the gears shows up he turns into an android with an exclamation mark.
Then after a 5 minute boot I get a system message that says:
Post here if you failed too, and solutions you have.
Attempts:
first - Device was nachorooted, root backed up via OTA rootkeeper. FAILED
second - with root disabled via OTA rootkeeper FAILED
third - removed root via viperboy's tool FAILED
fourth - factory reset then update FAILED
fifth - just going to repeat the stock attempts until something looks different
No idea if this would work but maybe use that tool viperboy made to unroot yours and then try (pretty sure it has an unroot option)? Not sure why that would help since rooted users have successfully updated but may be worth a shot.
sorry forgot to mention that was my 3rd attempt
i'm on #4 now just doing a factory reset first.
Having this same issue. Not sure what the problem is, but it keeps failing.
I too am rooted.
Trying out this E4GT...
exact same thing happened to me, except I have no idea how to try to update again, when I go to about phone, system update, the check update box is greyed out.
How exactly do you factory reset on .33 with the .33 zip on asus's website?
Sent from my Galaxy Nexus using Tapatalk
method 4 failed as well, any ideas anyone?
How are ya'll able to try the update more than once? Are you just talking about reboot or are you actually downloading the update again? the reason I ask is that I am unable to click the check update button.
chris61292 said:
How exactly do you factory reset on .33 with the .33 zip on asus's website?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
its not exactly "factory" reset, but its a full wipe of settings and data.
like 5 attemps still failed..
factory reset, cold boot, reboot router, still failed.
johnnyutah22 said:
How are ya'll able to try the update more than once? Are you just talking about reboot or are you actually downloading the update again? the reason I ask is that I am unable to click the check update button.
Click to expand...
Click to collapse
I'm following what you mean.
edit:
when I click system firmware update the "check update button is grayed out but it just starts downloading in my tray automagically.
Rest all data, unrooted, still no luck. 4 failed attempts, not sure what would be any different from the rooted users that are able to update.
This is why you guys shouldnt have rooted knowing ICS was around the corner.
I too am getting failed. I used VipreMod to root and I've tried unrooting using said tool and also using the OTA root backup tool.
jdbaker82 said:
This is why you guys shouldnt have rooted knowing ICS was around the corner.
Click to expand...
Click to collapse
even unrooted ppl are having this prob. i think its more a bad firmware download than a root problem.
Sent from my Transformer Prime TF201 using xda premium
jdbaker82 said:
This is why you guys shouldnt have rooted knowing ICS was around the corner.
Click to expand...
Click to collapse
This does not have anything to do with root.
A number of fully rooted users have already updated.
I'm in the same boat, on my 3rd try downloading the update.
jfortier777 said:
This does not have anything to do with root.
A number of fully rooted users have already updated.
Click to expand...
Click to collapse
I was rooted updated with no problems. Got root back with rootkeeper
I cant update anymore.
Now I'm just getting "no update available"
jdbaker82 said:
This is why you guys shouldnt have rooted knowing ICS was around the corner.
Click to expand...
Click to collapse
Thank you, oh wise one, for this great tid-bit of knowledge
After some hours of learning the Asus blob system, I have finally got the latest OTA packaged properly.
Thanks to the Virtuous Team for their updater-script that I started with.
If you download this, please click "thanks" for the chances I took on bricking my device to make this for us.
Disclaimer: I am not responsible for any damage caused to your device due to flashing this.
That said, I am writing this post on my prime which is running this firmware and working well.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This ROM is completely stock 9.4.2.15 except for:
Rooted
Insecure Boot.img (Allows the system to be mounted writable)
ADB debugging enabled (Allows running logcat if needed)
Instructions
Make sure your Prime is unlocked and you have CWM installed (see this thread for help and a handy tool to do that)
Shut down the prime
Hold both the Power-button and the Volume-down button until the splash screen appears and some white text in the left top corner is visible
Release both buttons and press the Volume-up button
The device now boots into your CWM recovery
Make a backup of your current ROM
Inside CWM select "wipe data/factory reset" (Optional but highly recommended)
Then flash the rom zip as usual
Then flash the Accounts & Sync fix zip as usual
Download
9.4.2.15 Full Rom
MD5: e1af5c2386fcf972b238a94fac291cad
Reserved for me...
Wow, this is great! Thanks for your hard work. : )
This is excellent, Great Job!
is this deoxed, zipalined by any chance?
Entree said:
Wow, this is great! Thanks for your hard work. : )
Click to expand...
Click to collapse
You're welcome!
gerald410 said:
This is excellent, Great Job!
Click to expand...
Click to collapse
Thanks!
youngnex said:
is this deoxed, zipalined by any chance?
Click to expand...
Click to collapse
No. The only changes from stock are listed in the OP.
Thanks simply for your effort. Still running the Virtuous ROM, but glad this has been made available.
05GT said:
Thanks simply for your effort. Still running the Virtuous ROM, but glad this has been made available.
Click to expand...
Click to collapse
I share the same situation and feelings. Thanks for working on this. Does your file manage to flash the latest kernel as well?
Deathbyfugu said:
I share the same situation and feelings. Thanks for working on this. Does your file manage to flash the latest kernel as well?
Click to expand...
Click to collapse
Yes it does.
First of all, thank you for packaging this for the rest of us!
I am curious about one thing.
jermaine151 said:
Make sure to do the "wipe data/factory reset" step!
Click to expand...
Click to collapse
I realize that "wipe data" has become the catch-all cure for custom rom issues, but why is this a required step for what's essentially a stock rom when the locked bootloader version doesn't need to wipe data?
I'm not complaining, I'm just wondering why this is a required step (instead of an "if you have problems try wiping data" step)?
iconoclastnet said:
First of all, thank you for packaging this for the rest of us!
I am curious about one thing.
I realize that "wipe data" has become the catch-all cure for custom rom issues, but why is this a required step for what's essentially a stock rom when the locked bootloader version doesn't need to wipe data?
I'm not complaining, I'm just wondering why this is a required step (instead of an "if you have problems try wiping data" step)?
Click to expand...
Click to collapse
I say that to limit issues. You can try it without wiping and then wipe if you have problems. I flashed it over 11.1 and it worked but it seems to run better when installed fresh so I'm re-setting up my apps.
jermaine151 said:
Yes it does.
Click to expand...
Click to collapse
Certainly an easy way to update the kernel, but based on the ways the Prime seems to manage to get bricked even after the user follows instructions to a T I am worried that including the kernel may cause you and the users a big headache if things go awry.
Deathbyfugu said:
Certainly an easy way to update the kernel, but based on the ways the Prime seems to manage to get bricked even after the user follows instructions to a T I am worried that including the kernel may cause you and the users a big headache if things go awry.
Click to expand...
Click to collapse
I've tested it a couple of times on mine. I removed the recovery and bootloader blobs from it so it just basically puts the boot.img in the staging partition and installs it on reboot just like CWM or any other blob. I doubt that anyone could brick with this since it's only touching the boot partition.
Hey,
once we got some successful kernel flash reports, do you mind if I take a look at your updater-script for the kernel thing?
Diamondback said:
Hey,
once we got some successful kernel flash reports, do you mind if I take a look at your updater-script for the kernel thing?
Click to expand...
Click to collapse
No, I don't mind at all.
jermaine151 said:
No, I don't mind at all.
Click to expand...
Click to collapse
Collaboration for the win!
Ah, that is an excellent idea
Calling dd via busybox should work
It just seems the in-built CWM functions for flashing stuff doesn't work at all for the kernel blob.
Thanks, once confirmed, I'll add it to my ROM too
Diamondback said:
Ah, that is an excellent idea
Calling dd via busybox should work
It just seems the in-built CWM functions for flashing stuff doesn't work at all for the kernel blob.
Thanks, once confirmed, I'll add it to my ROM too
Click to expand...
Click to collapse
Thanks! Yeah, I had a hard time trying the old methods to flash the kernel. This method seems to work well. I'm anxious for feedback from people that have installed it.
If you have flashed this, please post and confirm that it installed the ROM and kernel fine for you.
Thanks!
Flashed no problem without wiping, and Kernel installed no problem too. Works great, thanks a lot.
MAC address's wifi and bluetooth, imei are here but I have reflashed stock rom but still no luck, any solutions?
kennguy said:
MAC address's wifi and bluetooth, imei are here but I have reflashed stock rom but still no luck, any solutions?
Click to expand...
Click to collapse
Have you tried flashing the att JB radio? (look for it in the general section there is thread with different radios(modems) you can try.
luisoman2000 said:
Have you tried flashing the att JB radio? (look for it in the general section there is thread with different radios(modems) you can try.
Click to expand...
Click to collapse
Hi mate, no luck, any solutions?
Are you 100% sure airplane mode is not activated? I know it sounds dumb but might be the reason if everything else seems working fine.
kennguy said:
Hi mate, no luck, any solutions?
Click to expand...
Click to collapse
If you have an EFS backup, you might want to restore it.
jimbo77 said:
Are you 100% sure airplane mode is not activated? I know it sounds dumb but might be the reason if everything else seems working fine.
Click to expand...
Click to collapse
Yes,,, airplane mode is off... wifi is strange. When I turn it on to scan wifi but wifi automatically switch off.
kennguy said:
Yes,,, airplane mode is off... wifi is strange. When I turn it on to scan wifi but wifi automatically switch off.
Click to expand...
Click to collapse
When you flashed back to stock, did you do it by CWM/TWRP or LGNPST?
I'd recommend LGNPST (made a backup of your internal sd, it will be wiped out) and see if the problem persist.
jimbo77 said:
When you flashed back to stock, did you do it by CWM/TWRP or LGNPST?
I'd recommend LGNPST (made a backup of your internal sd, it will be wiped out) and see if the problem persist.
Click to expand...
Click to collapse
I revert back to stock by this guide: http://forum.xda-developers.com/showthread.php?t=2668412
... but the problem persist... I think may be is a hardware problem...
kennguy said:
I revert back to stock by this guide: http://forum.xda-developers.com/showthread.php?t=2668412
... but the problem persist... I think may be is a hardware problem...
Click to expand...
Click to collapse
I'd say that only option should be to restore the EFS backup. You should have that when first unlocked bootloader with FreeGee
jimbo77 said:
I'd say that only option should be to restore the EFS backup. You should have that when first unlocked bootloader with FreeGee
Click to expand...
Click to collapse
But I did not backup EFS, any solutions except restoring EFS mate?
kennguy said:
But I did not backup EFS, any solutions except restoring EFS mate?
Click to expand...
Click to collapse
Well my only idea right now if for you to get a radio log from the phone and then share it to see if we can spot anything out of usual that might be affecting your phone's connectivity settings.
You can use this app to get the desired logs
http://forum.xda-developers.com/showthread.php?t=1123129
I'll recommend you to try to reproduce the steps so the app can capture the appropriate log, after that share what you get
jimbo77 said:
Well my only idea right now if for you to get a radio log from the phone and then share it to see if we can spot anything out of usual that might be affecting your phone's connectivity settings.
You can use this app to get the desired logs
http://forum.xda-developers.com/showthread.php?t=1123129
I'll recommend you to try to reproduce the steps so the app can capture the appropriate log, after that share what you get
Click to expand...
Click to collapse
OK, I'll send you the log later...but before that I got issue "HW was reset detected".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And I tried to back to stock rom then I got no wifi, bluetooth, signal but IMEI is not null. After that, I unlocked bootloader, flash recovery, tried to wipe data and got this issue:
kennguy said:
OK, I'll send you the log later...but before that I got issue "HW was reset detected".
View attachment 2689212
And I tried to back to stock rom then I got no wifi, bluetooth, signal but IMEI is not null. After that, I unlocked bootloader, flash recovery, tried to wipe data and got this issue:
View attachment 2689210
Click to expand...
Click to collapse
The first screen is due to a Kernel Crash, are you running a custom kernel on your phone? I've got that with a few custom Kernels and if that's the case then probably the kernel modules are not compatible with the phone software. Can you flash for example a custom KK Rom without a modified kernel to see if you get any connection?
Now for the second screenshot, my take is that you are using a MicroSD that is formatted as exFAT (Usually that's the format of 64GB cards) and the recovery does not have support for that kind of file system.
Q&A for [ROM][PORT][JB 4.1.2] Nabixus 0.1beta for Nabi 2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
I went and installed this Rom, and the Youtube App wont connect to the server, thus the videos wont play. It lets me log into the google account, but every video i try says "cant connect to server tap to retry"
Has anyone else had this issue?
eviltone97 said:
I went and installed this Rom, and the Youtube App wont connect to the server, thus the videos wont play. It lets me log into the google account, but every video i try says "cant connect to server tap to retry"
Has anyone else had this issue?
Click to expand...
Click to collapse
I hadn't noticed it until you mentioned it but, yeah, same problem here. I'm trying to figure out what the problem is.. For now you can uninstall the updates to the app and it will work.
**EDIT: It looks like a lot of people have been having this problem on lots of devices so I'm not sure what the deal is. I did find that if you keep tapping the video that it will eventually play...seems like if you play with it you can find a pattern that works relatively consistently. It's still annoying though.
Just quickly pinging this thread so I can find it later, since XDA refuses to consider a section for Fuhu's Android tablets.
Sent from my Nexus 10 using Tapatalk
Why not a thread for fuhu tablets?
Nabi 2 NAbixus 0.1beta questions!
I followed all the instructions to install this rom but it just stays in the boot screen that says nabi? any suggestions?
CarlosC88 said:
I followed all the instructions to install this rom but it just stays in the boot screen that says nabi? any suggestions?
Click to expand...
Click to collapse
How long did you wait? That first boot can take what seems like forever.
n3wt said:
How long did you wait? That first boot can take what seems like forever.
Click to expand...
Click to collapse
i left it about one hour, i also realized the twrp said no OS installed when i rebooted. not sure if thats a issue
CarlosC88 said:
i left it about one hour, i also realized the twrp said no OS installed when i rebooted. not sure if thats a issue
Click to expand...
Click to collapse
Yeah, something didn't go right...I'd try wiping and re-installing and if it still doesn't work then it might be a bad download.
n3wt said:
Yeah, something didn't go right...I'd try wiping and re-installing and if it still doesn't work then it might be a bad download.
Click to expand...
Click to collapse
i tried wiping and reinstalling. i noticed it said error when trying to install. and ideas?
CarlosC88 said:
i tried wiping and reinstalling. i noticed it said error when trying to install. and ideas?
Click to expand...
Click to collapse
Hmm, did it give any info about the error? Which version of TWRP do you have? Did you have the 2.4 nabi software or something else?
n3wt said:
Hmm, did it give any info about the error? Which version of TWRP do you have? Did you have the 2.4 nabi software or something else?
Click to expand...
Click to collapse
it has version 2.2.2.1.
basically its my friends son nabi tablet and he told me that he was just stuck on the boot logo . i figured i could just put it back to stock with a restore but i cant even do that,
error just basically says errror couldnt be installed
CarlosC88 said:
it has version 2.2.2.1.
basically its my friends son nabi tablet and he told me that he was just stuck on the boot logo . i figured i could just put it back to stock with a restore but i cant even do that,
error just basically says errror couldnt be installed
Click to expand...
Click to collapse
Oh, ok....so you tried to do a restore from a backup in TWRP?
n3wt said:
Oh, ok....so you tried to do a restore from a backup in TWRP?
Click to expand...
Click to collapse
I tried doing a restore to a stock rom, that didn't work.
I also tried just doing a install and that didn't work either.
Maybe I'm not putting the stock rom on the correct folder for restore?
CarlosC88 said:
it has version 2.2.2.1.
basically its my friends son nabi tablet and he told me that he was just stuck on the boot logo . i figured i could just put it back to stock with a restore but i cant even do that,
error just basically says errror couldnt be installed
Click to expand...
Click to collapse
2.2.2.1 is way too old. Will boot but won't work at all if the tablet was on Jellybean or higher.
aicjofs said:
2.2.2.1 is way too old. Will boot but won't work at all if the tablet was on Jellybean or higher.
Click to expand...
Click to collapse
What version do you recommend, and if you could give me a quick step by step tutorial on how to install it please
CarlosC88 said:
What version do you recommend, and if you could give me a quick step by step tutorial on how to install it please
Click to expand...
Click to collapse
I wish I knew what Nabi build you were on to begin with.
I would try this in order. Flash this in TWRP(Install tab)
http://forum.xda-developers.com/showpost.php?p=50431160&postcount=97
This has a more detailed log. If you see stuff in the log about not mounting, etc then it's not going to work. (Actually this is a good thing which means your bootloader is Jellybean)
If that doesn't work try this next. Install this in TWRP. This is what you are going to need to be on eventually anyway if you are trying to run a Jellybean port.
http://nabtabhacks.com/downloads/twrp-recovery-JBNV7AUS-271.zip (There are more recent versions as well I just gave you this one because I know for sure it works for Nabixus)
aicjofs said:
I wish I knew what Nabi build you were on to begin with.
I would try this in order. Flash this in TWRP(Install tab)
http://forum.xda-developers.com/showpost.php?p=50431160&postcount=97
This has a more detailed log. If you see stuff in the log about not mounting, etc then it's not going to work. (Actually this is a good thing which means your bootloader is Jellybean)
If that doesn't work try this next. Install this in TWRP. This is what you are going to need to be on eventually anyway if you are trying to run a Jellybean port.
http://nabtabhacks.com/downloads/twrp-recovery-JBNV7AUS-271.zip (There are more recent versions as well I just gave you this one because I know for sure it works for Nabixus)
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have the Nabi 2 if that helps
I got this while trying to install/flash either one of those zip files you provided
CarlosC88 said:
I have the Nabi 2 if that helps
I got this while trying to install/flash either one of those zip files you provided
Click to expand...
Click to collapse
So either the update-binary in those zips are too new for 2.2.2.1 or you have the jellybean bootloader. How did you get 2.2.2.1 on there to begin with? What did you use?
aicjofs said:
So either the update-binary in those zips are too new for 2.2.2.1 or you have the jellybean bootloader. How did you get 2.2.2.1 on there to begin with? What did you use?
Click to expand...
Click to collapse
I didn't use anything, it was there already.
There is some talk in the P6 race to brick Telegram group, it seems that the december update is causing root to fail.
So until this is fixed/solved, DO NOT UPDATE IF YOU WANT TO RETAIN ROOT.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Oh no topjohnwu you didnt
ne0ns4l4m4nder said:
Oh no topjohnwu you didnt
Click to expand...
Click to collapse
He is working for the enemy now, was only a matter of time for problems to arise since he already stopped supporting MagiskHide at the behest of Google^^
Maybe Magisk just needs an update, maybe we have a bigger problem, we'll see
Nah, he'll find root or another Magisk developer will.
Cant we flash a patched stock boot image after the problem is solved?
As OP stated, do not update to December if you want to keep root. I did before I checked forums and lost root. Rolling back to November to hopefully regain access to root.
bb709394 said:
As OP stated, do not update to December if you want to keep root. I did before I checked forums and lost root. Rolling back to November to hopefully regain access to root.
Click to expand...
Click to collapse
Please report back if its possible to roll back
I don't see any update when I check for update on my Pixel 6.
Do I need to something to get the update? I ma not rooted and hence do not worry about rooting.
bb709394 said:
As OP stated, do not update to December if you want to keep root. I did before I checked forums and lost root. Rolling back to November to hopefully regain access to root.
Click to expand...
Click to collapse
Tread carefully, someone tried dirty flashing which then required a clean flash.
cd993 said:
Tread carefully, someone tried dirty flashing which then required a clean flash.
Click to expand...
Click to collapse
Yup, dirty flashed failed and requiring a clean flash. Good learning experience and lesson for me, don't jump the gun with the newest updates.
Assumptions made when I flashed December update on 4A 5G without any problems... c'est la vie.
bb709394 said:
Yup, dirty flashed failed and requiring a clean flash. Good learning experience and lesson for me, don't jump the gun with the newest updates.
Assumptions made when I flashed December update on 4A 5G without any problems... c'est la vie.
Click to expand...
Click to collapse
Yeah I would have held off rooting, as whilst sideloading the OTA I read that root wasn't working... oh well, a fix will come soon I'm sure
i didnt read this forum before flashing, now im stuck on a screen with the google logo and a loading bar. is my phone ****ed?
does anyone get corrupted data and stuck on google logo? any help?
Lainey52900 said:
i didnt read this forum before flashing, now im stuck on a screen with the google logo and a loading bar. is my phone ****ed?
Click to expand...
Click to collapse
You'll likely have to use the Google reset to factory process to ever use the phone again. I haven't rooted my Pixel 6 yet, though, so I can't confirm. But that's how I fixed a bad Pixel 5 update.
XNine said:
You'll likely have to use the Google reset to factory process to ever use the phone again. I haven't rooted my Pixel 6 yet, though, so I can't confirm. But that's how I fixed a bad Pixel 5 update.
Click to expand...
Click to collapse
what google reset?
Vio281 said:
what google reset?
Click to expand...
Click to collapse
Google Pixel - Update and Software Repair
Need a USB cable and Chrome (I think, never used a different browser for it).
Again, I can't confirm this works but it's just an educated guess
XNine said:
Google Pixel - Update and Software Repair
Need a USB cable and Chrome (I think, never used a different browser for it).
Again, I can't confirm this works but it's just an educated guess
Click to expand...
Click to collapse
just try it, only work up to google 5
Okay, so for anyone else here who tries to root using the December patch and gets stuck on the Google logo screen, here are the steps I took to fix it:
1. Hold down the power button until the phone turns off
2. Enter fastboot via holding down the power button and volume down
3. Attach a usb cable to a computer, download the factory image zip, then extract it
4. Once extracted, double click on "flash-all.bat," this will reflash every single component of the image to your phone and once it's done, will reboot and should boot as if nothing ever happened.
Lainey52900 said:
Okay, so for anyone else here who tries to root using the December patch and gets stuck on the Google logo screen, here are the steps I took to fix it:
1. Hold down the power button until the phone turns off
2. Enter fastboot via holding down the power button and volume down
3. Attach a usb cable to a computer, download the factory image zip, then extract it
4. Once extracted, double click on "flash-all.bat," this will reflash every single component of the image to your phone and once it's done, will reboot and should boot as if nothing ever happened.
Click to expand...
Click to collapse
i got a corrupted image and still stuck on google logo.
Vio281 said:
i got a corrupted image and still stuck on google logo.
Click to expand...
Click to collapse
for anyone running into the same situation i did, I have to use the flash option on the google firmware page to get my phone working again, Thank god...