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.
Related
Well guys, I decided to remake my thread for the new version of this app since it covers both 8gb and 16gb versions of the nook tablet.
--information:
THIS HAS NO TESTING! If something is broken, it's not my fault. Just report it in a non-urgent way and I'll fix it.
Well, I decided to release this app in a separate thread so I can keep track of the new version better. This one has been fixed up (still a visual CluserF*** but it's not supposed to be pretty, only get you an internal recovery up and running.)
Problems:
None with my app, however there are sure to be a few bugs on the recovery. Also: this flashes to internal, that's why I included a reset to stock button!
How to fix a borked install: CLICK ME CLICK ME FOR THE FIX!
(Note, you need superuser otherwise not a damn thing will happen!)
Download link:
here - md5 = 21ab80c09b678c2e9c93e0a2c70bbba2
*Note: Guys, I'm really having cashflow problems for a lot of things that I need to do (which is why I actually sold my nook) so I would like to ask for a bit of donations. Don't want to force you all to pay a couple bucks through market, etc. :/ Thanks.
- Other Note, you don't have to donate, would just appreciate it if you did.
Instructions:
Just click the button that has the recovery you want to flash. It's really simple. Screenshots, credit, and changelog will be posted in the next post.
Wait 10 seconds for the flash to finish then you can reboot if you want.
Please don't mirror
Changelog:
Code:
2.5: Cleaned up code a bit more and added cwm for 8gb + 16gb
2.0: Cleaned up the code, added better md5 checking now it won't flash without a good md5.
1.5.5: Fixed md5 hash checking
1.5: Added Reboot Recovery button
1.1: Fixed filename issue for stock recovery
1.0: Initial release.
Credit:
Code:
megdh00t for the recovery
myself for the image of stock and designing the app
Screenshots:
{
"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 clicked the thanks button, but also wanted to say thank you and mention that this will help many people who have flashed CWM for 16gb to the 8gb device and are not able to recover. Will Donate.
albertwertz said:
I clicked the thanks button, but also wanted to say thank you and mention that this will help many people who have flashed CWM for 16gb to the 8gb device and are not able to recover. Will Donate.
Click to expand...
Click to collapse
Thanks! Guys, expect an update with 1.4.2 recovery for stock later tonight. I just wanted to get the CWM build pushed out first so you atleast have something to use.
Good job, I'm sure this will help reduce some 8 GB bricks.
Indirect said:
Thanks! Guys, expect an update with 1.4.2 recovery for stock later tonight. I just wanted to get the CWM build pushed out first so you atleast have something to use.
Click to expand...
Click to collapse
Has this been incorporated into the download file? Does it provide for selecting whether we want 1.4.0 or 1.4.2?
FYI, link is dead after goo.im went down.. Also, did you have a newer version with a newer recovery? I could only find an older APK (version 2.5) which flashes 5.0.2.8 - looks like the newest version is 5.5.0.4 from what I'm seeing...
The download link is dead ...
I haven't been able to find a rom that runs without random (and very frequent) reboots for me. I'm looking for a good way to go to back to stock, but I can't get anything going. Help please.
zeropants said:
I haven't been able to find a rom that runs without random (and very frequent) reboots for me. I'm looking for a good way to go to back to stock, but I can't get anything going. Help please.
Click to expand...
Click to collapse
post this in Q&A, not here. also in nook tablet general i believe there was a guide how to get it to stock. and what rom were you using? all cm10 roms, and several cm9 roms will reboot occassionally, its a 3.x kernel issue. use chrmhoffmann's CM9 for one with no reboots, or you have to use cm7 (android 2.3)
Link is still down.
Just a thought why not pm the Dev instead of repeatedly posting in a thread he may or may not look at any time soon
Sent through the might of Eris
Finally got around to reuploading.
Sent from my Nook Tablet using xda premium
Quick question... when I reboot into stock recovery I get this error with the picture of the tablet with an exclamation mark saying "Please restart your device again. If you encounter the same issue please contact customer support." Any ideas why?
tackyjan said:
Quick question... when I reboot into stock recovery I get this error with the picture of the tablet with an exclamation mark saying "Please restart your device again. If you encounter the same issue please contact customer support." Any ideas why?
Click to expand...
Click to collapse
did you ever solve this? The same thing happened to me. I had to exchange the tablet at B&N.
Thats just stock recovery...
Sent from my Nexus 7 using xda premium
Indirect said:
Thats just stock recovery...
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
When this came up for me, I couldn't get it to restart - wouldn't boot at all.
parted.img didn't work (unbrick method) - tried CWM SD card - no dice.
I had to take to to the B&N bookstore and they couldn't fix it either. I got an exchange.
Remove any SD, then hold power + N for 15 seconds.
Sent from my Nexus S 4G using xda premium
Indirect said:
Remove any SD, then hold power + N for 15 seconds.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I'll try that - next time it happens.
Too late now, though. I have a different Nook Tablet.
Funny - but the B&N tech person didn't suggest this.
By the way - this happened when I tried restoring with the parted.img brick fix. It didn't unbrick my nook (which was stuck going to CWM Recover - couldn't get past it).
{
"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"
}
Wanna be up to date with ParanoidAndroid project news?, click here, and visit our webpage!
Installation Instructions
Place ROM onto phone storage
Reboot to recovery
Make a Nandroid
Install Rom: Wipe INSIDE ROM
When you select "Reboot Not", you'll get a CWM error, IGNORE IT
Install OPTIONS or Gapps
WIKI/FAQ Located: To be reworked
Click to expand...
Click to collapse
Paranoid Hints
Go to Settings, System, Font size, set it to NORMAL
Launcher Settings: margins: SMALL (If youre using Apex / Nova), show permanent searchbar: YES, Grid: 5x4, resize all widgets: YES, Wallpaper scrolling: OFF
Click to expand...
Click to collapse
Paranoid Trouble
Nothing yet. All possible visual bugs can be fixed changing PAL & PAD parameters
Click to expand...
Click to collapse
What is Borked:
Video Camera-laggy
Transitional Stutters Possible
You tell me
Both GL issues are due to missing drivers. Since Moto won't release, there is no ETA for fix
If you need to report a NEW bug, report it once, and the next TWO people VERIFY it. I don't need everyone reporting same bug 20 times. I you can, provide me the following information:
Version you are using
What wipe you did and what ROM you came from
Have you restored data/apps through Titanium or other app?
What app is misbehaving and steps to reproduce error
LOGCATS <--Prefer this
If you don't know how to logcat, go HERE and learn. This really nice guy took the time to write out a good how to
When you have a LOGCAT and would like to post it, please go to pastebin and post it in there, then LINK that location in this thread...I don't want to see them posted directly in here.
Click to expand...
Click to collapse
Downloads
ROM File Located Here
Options Chooser Located Here
My CWM V1 Located HERE -Aroma Prep Here Too
Click to expand...
Click to collapse
Credits:
Cyanogenmod Project, for CM10
Jokersax11 for help with initial Photon work
scott.hart.bi for help with source work
Amarullz for Aroma Installer
Paranoid Android's Devs for making this ROM
Anyone Testing and Providing USEFUL FEEDBACK (logcats )
Click to expand...
Click to collapse
GITHUB (FOR KERNEL SOURCE)-GPL COMPLIANCE PhotonDevTeam Repo
Click to expand...
Click to collapse
SCREENSHOTS
Is this uploaded? I didnt see it on Jokers site
MikeyLee said:
Is this uploaded? I didnt see it on Jokers site
Click to expand...
Click to collapse
Under Th3Bill
wow great job, I'm happy to review the Paranoid, thanks Th3Bill, I hasten to download and test it
Thanks a lot for the new version of my favourite ICS rom! Can't donate as I don't have paypal, but rest assured I will click on your ads everyday
Ok....don't download for a little while. I have to re-upload the rom. I made a boo-boo, which will result in tablet mode not initiating properly. I just fixed it on my phone, and it is SWEET!!!
Hi Bill, the process com.android.phone stopped unexpectedly on first boot bug is still there. I tried to fix it using the previous webcorefix.zip but it just stuck on the boot animation screen.
/b/-TarD said:
Hi Bill, the process com.android.phone stopped unexpectedly on first boot bug is still there. I tried to fix it using the previous webcorefix.zip but it just stuck on the boot animation screen.
Click to expand...
Click to collapse
GSM or CDMA?
com.phone wouldn't be webcore...
If you can get me a logcat output, that'd be great. I have flashed this 3 times clean over the last few hours. I use CDMA and have had NO issues.
Th3Bill said:
GSM or CDMA?
com.phone wouldn't be webcore...
If you can get me a logcat output, that'd be great. I have flashed this 3 times clean over the last few hours. I use CDMA and have had NO issues.
Click to expand...
Click to collapse
I am using GSM. Is my way of creating a logcat output correct? I reinstall the rom, get the error msg, set usb debugging on and charge only, connect phone to computer, and use adb logcat on my command prompt?
Anyway the reason I thought the webcorefix fix the issue is because it worked for me on Paranoid Android 1.1. After flashing that, no more error messages.
Edit : Not sure where did I do wrong, I use adb logcat > logcat.txt but it kinda stuck there not moving. Am using the android-sdk from my previous Xperia Play flashing days.
Edit 2 : I got the logcat.txt after I got bored waiting and disconnect, hope its complete. Anyway, the phone doesn't detect any network after the phone process fc
/b/-TarD said:
I am using GSM. Is my way of creating a logcat output correct? I reinstall the rom, get the error msg, set usb debugging on and charge only, connect phone to computer, and use adb logcat on my command prompt?
Anyway the reason I thought the webcorefix fix the issue is because it worked for me on Paranoid Android 1.1. After flashing that, no more error messages.
Click to expand...
Click to collapse
If you have root explorer, go to build.prop to the line:
ro.telephony.default_network=7
change the 7 to 0
then reboot
go dialer put in *#*#4636#*#*
go to phone info
make sure it says GSM auto
reboot
I'll up a fix in a few mins once the re-up of this is finished.
Th3Bill said:
Ok....don't download for a little while. I have to re-upload the rom. I made a boo-boo, which will result in tablet mode not initiating properly. I just fixed it on my phone, and it is SWEET!!!
Click to expand...
Click to collapse
Right on man. Cant wait to update. Is the fixed ROM uploaded now?
Updated version is up
Th3Bill said:
If you have root explorer, go to build.prop to the line:
ro.telephony.default_network=7
change the 7 to 0
then reboot
go dialer put in *#*#4636#*#*
go to phone info
make sure it says GSM auto
reboot
I'll up a fix in a few mins once the re-up of this is finished.
Click to expand...
Click to collapse
Not sure whether I followed your instructions correctly. But it isn't working, but its okay, don't bother. I will wait for the your flashable fix and your fixed Paranoid rom together then report back
Thanks for the prompt help anyway
Awesome!
Great! cannot wait to try. No link under thebill, only MUI builds..
edit: found it, but in a weird place.... here is direct link MOD EDIT: Link Removed as per OP Request.....MD
hightech316 said:
Great! cannot wait to try. No link under thebill, only MUI builds..
edit: found it, but in a weird place.... here is direct link
Click to expand...
Click to collapse
Weird place? It's under Th3Bill "Paranoid Android for Photon" PLEASE DO NOT HOT LINK MY WORK. I have it through the site for a reason.
Please remove the link or I will ask the mod to remove it
Booting problem
Hello all,
I am not sure this is the right place for this but I can't get this to boot. I thought I had everything rooted, unlocked and latest version of clockwork recovery installed. This install doesn't make it past the dual core boot screen. I have tried this several times even with a different kernel and no luck. CM7 installs just fine. I may be missing something. Any help is appreciated.
ITSAHERO said:
Hello all,
I am not sure this is the right place for this but I can't get this to boot. I thought I had everything rooted, unlocked and latest version of clockwork recovery installed. This install doesn't make it past the dual core boot screen. I have tried this several times even with a different kernel and no luck. CM7 installs just fine. I may be missing something. Any help is appreciated.
Click to expand...
Click to collapse
When Aroma begins to install...watch it very carefully...if it goes through it really fast, it's because you have an unreported error in CWM. You need to go to Advanced menu, select Report Error, then select Show Log, then Reboot Recovery, then make sure you have at least 75% battery (if not, plug it in to the wall outlet...NOT A PC), then flash the rom
Th3Bill said:
When Aroma begins to install...watch it very carefully...if it goes through it really fast, it's because you have an unreported error in CWM. You need to go to Advanced menu, select Report Error, then select Show Log, then Reboot Recovery, then make sure you have at least 75% battery (if not, plug it in to the wall outlet...NOT A PC), then flash the rom
Click to expand...
Click to collapse
I didn't notice this was AROMA. I have been wiping before install. That could very well be my problem. Thank you.
You might also want to be on jokers recovery or TWRP. The cwm from rom manager app doesn't work for us
Sent from my MOF'd up MoPho
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.
I am stock rooted and didn't modify a single thing. The only thing I did was flash TWRP recovery because I was planning on flashing ROMS but I eventually decided to stick to stock rooted so I reflashed the stock recovery. I received the update a week ago and proceeded to install it. However, it seems to fail. When the phone boots into stock recovery it attempts to install the update but at about a 3rd of it's progress it immediately stops and all that is displayed on the screen is a phone flat down with a red triangle and exclamation mark inside it. I've tried searching about this but everything I find leads me to the One X and I've never owned that phone so I'm not sure how similar they really are. Does anyone know why this is happening? Would it possibly be due to a corrupted recovery file within my download source? Any help would greatly be appreciated.
Thanks in advance.
Anyone?
LuigiBull23 said:
I am stock rooted and didn't modify a single thing. The only thing I did was flash TWRP recovery because I was planning on flashing ROMS but I eventually decided to stick to stock rooted so I reflashed the stock recovery. I received the update a week ago and proceeded to install it. However, it seems to fail. When the phone boots into stock recovery it attempts to install the update but at about a 3rd of it's progress it immediately stops and all that is displayed on the screen is a phone flat down with a red triangle and exclamation mark inside it. I've tried searching about this but everything I find leads me to the One X and I've never owned that phone so I'm not sure how similar they really are. Does anyone know why this is happening? Would it possibly be due to a corrupted recovery file within my download source? Any help would greatly be appreciated.
Thanks in advance.
Click to expand...
Click to collapse
Did you relock bootloader?
Sent from my HTC One using Xparent Skyblue Tapatalk 2
Mine is unlocked and the update worked fine. You just need the stock Tmo recovery to make it work.
mrmytouch said:
Mine is unlocked and the update worked fine. You just need the stock Tmo recovery to make it work.
Click to expand...
Click to collapse
That's the thing.. I do have the TMO stock recovery. Unless you can provide me with another link, the one I downloaded doesn't seem to work at all and I've redownloaded numerous times. I still get that triangle..
Link to stock tmobile recovery is here
I got it from this thread
mrmytouch said:
Link to stock tmobile recovery is here
I got it from this thread
Click to expand...
Click to collapse
Thanks man. much appreciated. I will try this one out and see how it goes.
LuigiBull23 said:
Thanks man. much appreciated. I will try this one out and see how it goes.
Click to expand...
Click to collapse
Did it work out for you mate?
mrmytouch said:
Did it work out for you mate?
Click to expand...
Click to collapse
My apologies. I completely forgot to report back to this.. YES, all is well now. Not sure why the other recovery didn't work as it did work for others but guess that doesn't matter now. Thanks a lot for your help. Much appreciated.
I used this recovery, and it completely wiped my phone and all my stuff was gone. And it still didn't install the update. Is that normal?
Sent from my HTC One using xda app-developers app
bestofrhcp said:
I used this recovery, and it completely wiped my phone and all my stuff was gone. And it still didn't install the update. Is that normal?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Sounds more like a bootloader issue...
bestofrhcp said:
I used this recovery, and it completely wiped my phone and all my stuff was gone. And it still didn't install the update. Is that normal?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yes when you flash recovery I believe it will Wipe your sd card. But your stuff should be on your gmail account though at least your phone numbers. You need to give us more info. Are you on stock t mo rom?
mrmytouch said:
Yes when you flash recovery I believe it will Wipe your sd card. But your stuff should be on your gmail account though at least your phone numbers. You need to give us more info. Are you on stock t mo rom?
Click to expand...
Click to collapse
As far as I'm aware unlocking the bootloader or flashing an RUU are the ONLY things that wipe your storage. Flashing recoveries doesn't touch it except for adding in the necessary files to function properly.
LuigiBull23 said:
As far as I'm aware unlocking the bootloader or flashing an RUU are the ONLY things that wipe your storage. Flashing recoveries doesn't touch it except for adding in the necessary files to function properly.
Click to expand...
Click to collapse
I really cant remember if it did or did not when I flashed the recovery but in post #8 he said it wiped his sd. I could be wrong though. Just trying to help this guy out. I do know unlocking bootloader does wipe your sd though so i'm sure your right I just cant remember.
:| is the update supposed to go "reboot, recovery, blue bar moving along HALT reboot, recovery bigger loading blue bar, STOP dead, Red triangle"
ive tried it 3 times no luck.
{
"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"
}
ive Locked and reset the tamper flag with revone still wont install the OTA
its no so much I WANT the update as much as i WANT my phone to stop buggin me about the damn update XD
ive followed the thread linked above and tried all methods provided. no luck so im sure im doing something horrificaly wrong XD
all i can provide is this,
Verifying curent system...
assert failed: apply_patch_check("/system/build.prop", "5c450bd35b662fa55d667bda7463960e2eb669c
5", "48daa0113456b06b44b52c1b777d7d2e49af1196")
Instalation aborted.
soo all i got was something is up with the build prop that it dosnt like... as for the other randomness hell if i know.
its weird though as ive never rooted the phone. i just unlocked bootloader to get a custom recovery on it so i could make backups of my entire phone.
and flash that one mod that gets rid of the 3 dot bar.
Heres the build prop paste bin
http://pastebin.com/cT1sZ73K
Sieze said:
:| is the update supposed to go "reboot, recovery, blue bar moving along HALT reboot, recovery bigger loading blue bar, STOP dead, Red triangle"
ive tried it 3 times no luck.
ive Locked and reset the tamper flag with revone still wont install the OTA
its no so much I WANT the update as much as i WANT my phone to stop buggin me about the damn update XD
ive followed the thread linked above and tried all methods provided. no luck so im sure im doing something horrificaly wrong XD
all i can provide is this,
Verifying curent system...
assert failed: apply_patch_check("/system/build.prop", "5c450bd35b662fa55d667bda7463960e2eb669c
5", "48daa0113456b06b44b52c1b777d7d2e49af1196")
Instalation aborted.
soo all i got was something is up with the build prop that it dosnt like... as for the other randomness hell if i know.
its weird though as ive never rooted the phone. i just unlocked bootloader to get a custom recovery on it so i could make backups of my entire phone.
and flash that one mod that gets rid of the 3 dot bar.
Heres the build prop paste bin
http://pastebin.com/cT1sZ73K
Click to expand...
Click to collapse
Are you even on stock recovery?
LuigiBull23 said:
Are you even on stock recovery?
Click to expand...
Click to collapse
technicly yea XD i flashed the latest stock recovery and being as my phone wasnt OTA'd to the 4.2.2 its recovery was from the 4.2.2 but the rest of the phone wasnt. unless i can get my hands on the stock recovery from my phone im **** out of luck and will be forever stuck with the red triangle of ass... its at times like this i regret my haste and stupidity XD
just tryed again and now its spitting out that assert failed for system/app/settings.apk
Restarted the tablet just now and noticed a Dell update. Installed it and, something definitely has improved as the tablet seems much quicker. Ran Antutu and the Ram speed has gone way up. Is it possible Dell has addressed an issue with these tablets? Anyone else get this update?
Yes i did receive this update, it fixed some of the browser issues in chrome.
I can't install the update is just fails mid Install with an Android Caution sign and constantly gives me the OTA Notification.
Maybe it depends on how new your Venue 8 is?
petewr said:
Maybe it depends on how new your Venue 8 is?
Click to expand...
Click to collapse
Mine is the newest 8340 - I think I messed something up but I am not sure how to return to stock as the only fastboot images I could find are rooted ones with disabled OTAs.
Haxxa said:
Mine is the newest 8340 - I think I messed something up but I am not sure how to return to stock as the only fastboot images I could find are rooted ones with disabled OTAs.
Click to expand...
Click to collapse
Were you rooted or stock?
My wifes 8340 was rooted and the updater rebooted and promptly failed. Tablet didn't loose root but something is definitely messed up now. I've not had time to figure out what happened yet.
LinuxTom said:
Were you rooted or stock?
My wifes 8340 was rooted and the updater rebooted and promptly failed. Tablet didn't loose root but something is definitely messed up now. I've not had time to figure out what happened yet.
Click to expand...
Click to collapse
Yes I am rooted but no root apps were used and I unrooted to no avail. So it must be to do with the root process or something it has changed in the system partition. If we had fastboot images it would be easy enough to revert to stock and upgrade...
Haxxa said:
Yes I am rooted but no root apps were used and I unrooted to no avail. So it must be to do with the root process or something it has changed in the system partition. If we had fastboot images it would be easy enough to revert to stock and upgrade...
Click to expand...
Click to collapse
Aren't stock images available on the mykit_batch thread?
LinuxTom said:
Aren't stock images available on the mykit_batch thread?
Click to expand...
Click to collapse
Not for the Dell Venue 8340 (New Version) as far as I can see.
Haxxa said:
Not for the Dell Venue 8340 (New Version) as far as I can see.
Click to expand...
Click to collapse
You all can make your own, that's how those are made.
vampirefo said:
You all can make your own, that's how those are made.
Click to expand...
Click to collapse
Yes would appreciate someone taking the lead on that; I can't with my tablet in its current state... :crying::crying::crying:
Haxxa said:
Yes would appreciate someone taking the lead on that; I can't with my tablet in its current state... :crying::crying::crying:
Click to expand...
Click to collapse
I think someone has http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
quote from post below, I don't have this tablet to confirm, I have 3830, have made my own back ups since day one.
Code:
Stock Build YTP802A128630 Images
Note, unless you are doing development, you won’t need to download the following file. For Developers, here are the stock Android 4.4.4 (not rooted) boot.img, recovery.img, system.img.gz:
Dell_venue8_3840_4.4.4_Stock_Images.zip 822.1MB md5sum: 995db36a2daa6bd9955e75fa5a14a519
Haxxa said:
Yes would appreciate someone taking the lead on that; I can't with my tablet in its current state... :crying::crying::crying:
Click to expand...
Click to collapse
Looks like OEM 4.4.4 images are at http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427/post57209175#post57209175
LinuxTom said:
Looks like OEM 4.4.4 images are at http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427/post57209175#post57209175
Click to expand...
Click to collapse
vampirefo said:
I think someone has http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
quote from post below, I don't have this tablet to confirm, I have 3830, have made my own back ups since day one.
Code:
Stock Build YTP802A128630 Images
Note, unless you are doing development, you won’t need to download the following file. For Developers, here are the stock Android 4.4.4 (not rooted) boot.img, recovery.img, system.img.gz:
Dell_venue8_3840_4.4.4_Stock_Images.zip 822.1MB md5sum: 995db36a2daa6bd9955e75fa5a14a519
Click to expand...
Click to collapse
No Dice!
So I have tried everything to return to stock, the stock images provided in the thread refuse to flash with fastboot outputing error 121, It is a big image and gets half way through downloading system.img when this error occurs, I have tired unbricking but it will not detect my device when pressing download button and have tried about every driver available & 3 computers. I tried using CWM temp boot to flash the system.img put inside a update.zip but it did not work and now I am prepared to return the tablet as it will not restore
Any ideas left to help here?
Here's the error when using fastboot-
{
"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"
}
& The xFSTK Flasher gives no error as I can't no matter what I do get it to detect.
I have now spent 20 Hours trying to fix this - I have run through the guide 3 times and used 3 different computers I have no idea what to do?
Haxxa said:
No Dice!
So I have tried everything to return to stock, the stock images provided in the thread refuse to flash with fastboot outputing error 121, It is a big image and gets half way through downloading system.img when this error occurs, I have tired unbricking but it will not detect my device when pressing download button and have tried about every driver available & 3 computers. I tried using CWM temp boot to flash the system.img put inside a update.zip but it did not work and now I am prepared to return the tablet as it will not restore
Any ideas left to help here?
Here's the error when using fastboot-
& The xFSTK Flasher gives no error as I can't no matter what I do get it to detect.
I have now spent 20 Hours trying to fix this - I have run through the guide 3 times and used 3 different computers I have no idea what to do?
Click to expand...
Click to collapse
Well you should be flashing system.img.gz not system.img.
fastboot flash system system.img.gz
as far as recovery you would need to unpack system.img and build a rom to install via CWM.
vampirefo said:
Well you should be flashing system.img.gz not system.img.
fastboot flash system system.img.gz
as far as recovery you would need to unpack system.img and build a rom to install via CWM.
Click to expand...
Click to collapse
My deep apologies I have never flashed a .gz in fastboot before file I just assumed it need to be unachieved and it was compressed for the purpose of size...
I did try to build a Rom however it would not build on my Linux Server for some reason so I gave up on that after a few hours.
vampirefo said:
Well you should be flashing system.img.gz not system.img.
fastboot flash system system.img.gz
as far as recovery you would need to unpack system.img and build a rom to install via CWM.
Click to expand...
Click to collapse
Well I just managed to restore the system image found on the thread on to the tablet however when updating I encounter the same issue with the update failing. Even after flashing system, recovery, boot and wiping data back to original. There should be no trace of root at all....
Haxxa said:
Well I just managed to restore the system image found on the thread on to the tablet however when updating I encounter the same issue with the update failing. Even after flashing system, recovery, boot and wiping data back to original. There should be no trace of root at all....
Click to expand...
Click to collapse
How did you root? What are the errors you get from OTA update?
sent from my kingSing T1 via taptalk
vampirefo said:
How did you root? What are the errors you get from OTA update?
sent from my kingSing T1 via taptalk
Click to expand...
Click to collapse
Using Tethered Recovery by Social, and the error is half way through installing OTA in Recovery it goes from a loading (Progress bar) to a red caution symbol and then it reboots. Upon boot the version number and details remian the same....
Also should add this is stock without any mods or installed apps (just flashed and went straight to updating) ... root should have disappeared entirely when I flashed system.
Haxxa said:
Using Tethered Recovery by Social, and the error is half way through installing OTA in Recovery it goes from a loading (Progress bar) to a red caution symbol and then it reboots. Upon boot the version number and details remian the same....
Also should add this is stock without any mods or installed apps (just flashed and went straight to updating) ... root should have disappeared entirely when I flashed system.
Click to expand...
Click to collapse
That doesn't help, if I had that tablet, I would run the ota update through my cwn recovery, all failures are recorded so would know what was wrong.
Stock recovery I don't think records failures, without a log can't help you.
sent from my kingSing T1 via taptalk