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
Related
Hello,
Could you pls help a noob with a rooting problem? I attempted to root my ICS AT&T Galaxy Note i-717 using Odin3 v 1.85 and a pda.tar file. Prior to that, I had checked and confirmed the USB drivers are installed (I have Kies software installed on the PC. However, folliwing the succesful flash of pda.tar I got the phone stuck at the Samsung screen. I could still get to the download screen. However, the phone would not go pass that screen. Can you pls tell me what I did wrong/guide me w simple steps on how to fix the phone and finish the root? I have the read many different root treads but I find them confusing. Treads are ponting at different files to be frashed/installed on the phone. Thanks very much.
This happens from time to time...don't worry.
Reboot phone in download mode, connect phone, reflash kernel.
A few things: use stock samsung cable. Use back of computer usb port. Reboot computer before you try again. Re download the kernel to be sure your file is not corrupted. Make sure phone battery is more than 80%.
re:
rangercaptain said:
This happens from time to time...don't worry.
Reboot phone in download mode, connect phone, reflash kernel.
A few things: use stock samsung cable. Use back of computer usb port. Reboot computer before you try again. Re download the kernel to be sure your file is not corrupted. Make sure phone battery is more than 80%.
Click to expand...
Click to collapse
Rangercaptain,
Thanks very much. Where can I get the kernel from and which one/which file do I need to flash? Also, how do I flash it? Do I use Odin or another method? Again Thanks a lot!
ptanev said:
Rangercaptain,
Thanks very much. Where can I get the kernel from and which one/which file do I need to flash? Also, how do I flash it? Do I use Odin or another method? Again Thanks a lot!
Click to expand...
Click to collapse
Follow the part one instructions in the first post. Read twice click once. Take your time.
http://forum.xda-developers.com/showthread.php?p=24539068
Make sire lies is closed
Sent from my SAMSUNG-SGH-I717 using xda premium
Nolenm04 said:
Make sire lies is closed
Click to expand...
Click to collapse
Make sure Kies is closed
Yes, good suggestion. I would reboot the computer, put the phone in download, open Odin3, then plug in phone.
All that is well explained in the thread.
Problem solved
rangercaptain said:
Make sure Kies is closed
Yes, good suggestion. I would reboot the computer, put the phone in download, open Odin3, then plug in phone.
All that is well explained in the thread.
Click to expand...
Click to collapse
All,
Thanks very much for your help! I fugured it out and am now up and running!
I ended up flashing rooted Stock ICS ROM from FJ!
Thanks very much to all of you and FJ!
rangercaptain said:
Make sure Kies is closed
Yes, good suggestion. I would reboot the computer, put the phone in download, open Odin3, then plug in phone.
All that is well explained in the thread.
Click to expand...
Click to collapse
Oh snap lol just noticed I misspelled half of that oops
Sent from my SGH-I717 using xda premium
Nolenm04 said:
Oh snap lol just noticed I misspelled half of that oops
Sent from my SGH-I717 using xda premium
Click to expand...
Click to collapse
I liked it....:laugh:.....:good:
I thought it was drunk-xda-ing.
{
"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"
}
rangercaptain said:
I thought it was drunk-xda-ing.
Click to expand...
Click to collapse
:laugh:
rangercaptain said:
I thought it was drunk-xda-ing.
Click to expand...
Click to collapse
Lol
View attachment 1291558
Sent from A Closet @ Arkham Asylum on my GNote using Forum Runner, Black ★.
Stuck at Samsung
I have the same issue tho have tried troubleshooting and could really use some extra help.
Updated to ATT stock ICS update a few months ago. Everything workin fine.
Wanted to root it so I could back everything up not to lose anything when moving to JB.
Rooted by flashing Da_G's pda.tar, reboot, and then flashed 2.3.3.0 TWRP
Noticed it was stuck at Samsung.
Here's where I'm kickin myself because I should have backed it up before all this, but I waited because I figured root doesn't wipe data!
Entered TWRP, backed up.
Now what I've tried to fix it... and failed
1. Reflashed pda.tar about 5 times
2. Found a stock pda "pda-odin-att-stock.tar", flashed (fixed) but it's stock setup and contacts and other google services don't work, lost homescreen icon placement and all other settings.
3. TWRP: Restore all = stuck at Samsung again
4. Repeat 2 and Restore only System
5. Repeat 2 and Restore only Data
6. Repeat 2 and flash pda.tar = boots, but same thing with it all stock, so I restore and it's stuck again.
It's my wife's phone and she has contacts that aren't saved in Google, to-do lists saved in app data files, and to be honest, she said everything better be exactly the same after updating (which I promised it would be since the plan was to root, backup, update, and restore), so I'm kinda trying to save my hide. PLEASE HELP me save my ass ha!
Other things to note: I just rooted a new phone about 30mins prior with the exact same root and TWRP files and it went very smooth, no issues.
Using a Samsung original cable on a laptop. Phone Battery was ~30% when I did all the steps, but since then read that battery should be higher so swapped out to fully charged battery and retried the steps.
Using the root kernel you did, basically flashed a Gingerbread kernel over an ICS rom. (Doesn't work)
Your best bet at this point, is too flash a rooted ICS build from bigfau ...(located in the super thread stock section)
Just flash using TWRP ....BUT !!!
make sure you wipe the dalvik cache, system cache, and system before flashing the rooted ICS build.
Once the rom is flashed, you will be stock and rooted.
Regarding data you have lost with no backup....start begging forgiveness now ....it's gone ....g
gregsarg said:
Using the root kernel you did, basically flashed a Gingerbread kernel over an ICS rom. (Doesn't work)
Your best bet at this point, is too flash a rooted ICS build from bigfau ...(located in the super thread stock section)
Just flash using TWRP ....BUT !!!
make sure you wipe the dalvik cache, system cache, and system before flashing the rooted ICS build.
Once the rom is flashed, you will be stock and rooted.
Regarding data you have lost with no backup....start begging forgiveness now ....it's gone ....g
Click to expand...
Click to collapse
Wouldn't I be able to just flash an ICS Kernel to undo the GB kernel and set things straight? Or is the whole thing ruined already?
I have the data/app and data/data files. If all's really lost, I'll just put JB on it. If I copy the data/app and data/data files onto the new image will all the apps with their settings/data be restored at least?
Yes, flash the correct kernel.
I think what happened to me is the OS got deleted cuz once I flashed a rom I was good to go!
I had successfully flashed my phone and installed Cyanogenmod 11. After several weeks I decided to take my phone back to Stock Sense and in the process I messed up terribly. Somehow I erased everything off of my internal memory and the phone sits in the cyanogenmod bootloader. Apparently I had saved my backup to internal storage like an idiot and it is gone now. I do have an SD card accessible. The status is as follows:
1. Phone is unlocked
2. S-ON Status showing (not sure how to get it to S-Off but not sure if this is my biggest issue)
3. When the phone powers on it goes to the Cyanogenmod Boot Screen and the little blue guy staring at me stares at me with the spinning blue circle until the phone actually goes dead.
4. Once phone goes dead I can attain access to my bootloader by holding volume down and the power button and I can get into TWRP recovery.
5. I connect the phone to my PC and when I access by command prompt and type adb devices it shows the phone either in fastboot or recovery or sideload mode depending on where I am at in the accessible system.
6. I have loaded cyanogenmod 11 nightly on my external sd card and flashed it and it says successful but when I reboot the phone still remains locked on the bootscreen until it dies again.
7. I have tried sideloading the ROM and when I do that it tells me that it can not access internal storage or any type of storage and says it is using RAM for storage....not sure how that works but once the ROM has been sideloaded I can not find it.
Here is what I want....I simply want to be able to reinstall Sense 6 or Cyanogenmod 11 back onto my phone so it will work once again but I am lost. I have followed numerous how tos on the web and I am getting nowhere.
If anyone can help it would be greatly appreciated. Ask as many questions as needed and I will supply you with as detailed of an answer as I can.
Thanks in advance.
okay try this first and see if it gets at least cm11 working again...
1. Go and put cm11 on your external sdcard
2. boot into recovery mode
3. factory reset the device
4. manually wipe /system (this is needed under certain circumstances)
5. now flash cm11 and the gapps package
6. reboot
this should get cm11 back up and running for you at least. Now once cm11 is back up and running do the same thing with the sense rom that you were trying to go to. it should work.
EDIT: also, keep a copy of your nandroid backup on a computer somewhere that way if something like this happens again you dont loose your backup.
ziggy46 said:
okay try this first and see if it gets at least cm11 working again...
1. Go and put cm11 on your external sdcard
2. boot into recovery mode
3. factory reset the device
4. manually wipe /system (this is needed under certain circumstances)
5. now flash cm11 and the gapps package
6. reboot
this should get cm11 back up and running for you at least. Now once cm11 is back up and running do the same thing with the sense rom that you were trying to go to. it should work.
EDIT: also, keep a copy of your nandroid backup on a computer somewhere that way if something like this happens again you dont loose your backup.
Click to expand...
Click to collapse
When I attempt to factory reset the device it tells me it has failed.....and unable to mount '/data'
unable to mount internal storage
and does it matter that it is in S-On?
Thanks again
scruff72 said:
When I attempt to factory reset the device it tells me it has failed.....and unable to mount '/data'
unable to mount internal storage
and does it matter that it is in S-On?
Thanks again
Click to expand...
Click to collapse
okay ive had a phone of mine do that before, it should be okay as long as you wipe /system. after doing that try and flash the rom again and let me know if it works right.
and no it being s-on shouldnt matter with this.
scruff72 said:
When I attempt to factory reset the device it tells me it has failed.....and unable to mount '/data'
unable to mount internal storage
and does it matter that it is in S-On?
Thanks again
Click to expand...
Click to collapse
Did not work...still hung in boot loop......just fyi....there is NOTHING on my internal storage....it says 0 MB...here is a screenshot of what shows after I flash or do anything else about it not being able to mount....
{
"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"
}
ziggy46 said:
okay ive had a phone of mine do that before, it should be okay as long as you wipe /system. after doing that try and flash the rom again and let me know if it works right.
and no it being s-on shouldnt matter with this.
Click to expand...
Click to collapse
I will send you a screenshot of what I get when I try to wipe the system - it states that it fails. Should be able to attach screenshot in a few minutes.
Waiting on phone to die again because it will not power down.
I'm not 100% sure what's going on man.
Sent from my HTC One_M8 using Tapatalk
ziggy46 said:
I'm not 100% sure what's going on man.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
No problem. I appreciate your help. I know it can be saved because I can still get into the bootloader and recovery.....just not sure what to do.
ziggy46 said:
I'm not 100% sure what's going on man.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I fixed it....your advice got me to digging and I actually formatted the partition and then was able to load CM11. Thanks again...greatly appreciated.
scruff72 said:
I fixed it....your advice got me to digging and I actually formatted the partition and then was able to load CM11. Thanks again...greatly appreciated.
Click to expand...
Click to collapse
no problem man glad you got it working again [emoji1]
Sent from my HTC One_M8 using Tapatalk
Did you ever try to factory reset in bootloader?
This is the second post today I've seen where a person was having trouble wiping /data, which is usually a breeze. I wonder what is causing this. I'm just reaching a bit here, as the only time I've seen such issues, is on my old One X (EVITA) where doing a factory reset in bootloader would corrupt the internal storage. And the fact you said that formatting the storage fixed the issue, also reminds me of that same issue on the EVITA.
I'm in the same boat.
scruff72 said:
I fixed it....your advice got me to digging and I actually formatted the partition and then was able to load CM11. Thanks again...greatly appreciated.
Click to expand...
Click to collapse
Hi, I'm in a similar situation with my newly acquired HTC One M8.
I have access to bootloader and recovery (TWRP v.2.7.0.2), but I'm getting all the same "failed to mount ***" errors as you were having.
Can you please elaborate on how to "format the partition" or point me to a detailed thread/article on how to do that?
And any notes on how you got it back to work are very appreciated - I've spent hours and hours researching a trying things without any success.
I'm sorry I'm somewhat new to this...
Let me know if you need any more info and thank you for your help in advance.
scruff72 said:
I fixed it....your advice got me to digging and I actually formatted the partition and then was able to load CM11. Thanks again...greatly appreciated.
Click to expand...
Click to collapse
But how do you formatted the partition?! i´m in all most the same situation, and i think the things are clear, mi internal storage is corrupted, but the cuestion is How do i manually format it?
Thanks in advanceeeed!
AkaDeast said:
But how do you formatted the partition?! i´m in all most the same situation, and i think the things are clear, mi internal storage is corrupted, but the cuestion is How do i manually format it?
Thanks in advanceeeed!
Click to expand...
Click to collapse
You posted to a thread that is over a year old, its a stretch (to say the least) that you are in the "same situation".
If you can boot or flash TWRP, go to the Wipe options, then try the "Format Data" option.
Otherwise, try to relock the bootloader and RUU back to stock.
HTC One (M8) recovery fix
I have be stuck almost Vb. this worked with (M7) /(M8) AT&T. The quick fix would be to reflash BusyBox in recovery. Because more than likely your partition is out of wake due to flashing to many roms. If you get into recovery and are getting errors when trying to mount .Zip ie: all files completely missing or not enough space/storage est. When you the error its looking for an 4 dig number. try 0000 not work 1111. That works 90% for me. This assuming you are using TWRP 7.2++ or later. If still Stuck just flash same TWRP using over the top. Should be fine, I only know this because I have done the same and had worked great.
redpoint73 said:
You posted to a thread that is over a year old, its a stretch (to say the least) that you are in the "same situation".
If you can boot or flash TWRP, go to the Wipe options, then try the "Format Data" option.
Otherwise, try to relock the bootloader and RUU back to stock.
Click to expand...
Click to collapse
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.
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
Hi all.. Quick question.
I've just started the process of trying to root my One Max (international) and everything has gone smoothly with unlocking the bootloader etc, and i've flashed a CWM image to it as my recovery, but once i've rebooted, volume down and select recovery, hit power, it says entering recovery but then screen goes off, waits about 20-30 seconds and boots up as normal.. Is the CWM image file wrong? And if so, can i just redo the process of flashing the rom again the same way, or do i need to uninstall this image before i can? Does any new image not just overwrite?
I'm just a little frustrated at this point because it's now unlocked and tampered yet i have no root access.
RyanH77 said:
Hi all.. Quick question.
I've just started the process of trying to root my One Max (international) and everything has gone smoothly with unlocking the bootloader etc, and i've flashed a CWM image to it as my recovery, but once i've rebooted, volume down and select recovery, hit power, it says entering recovery but then screen goes off, waits about 20-30 seconds and boots up as normal.. Is the CWM image file wrong? And if so, can i just redo the process of flashing the rom again the same way, or do i need to uninstall this image before i can? Does any new image not just overwrite?
I'm just a little frustrated at this point because it's now unlocked and tampered yet i have no root access.
Click to expand...
Click to collapse
Go with twrp it roots the device after first time going through the recovery. I've heard of issued with cwm.
Sent from my HTC0P3P7 using XDA Free mobile app
cstrife999 said:
Go with twrp it roots the device after first time going through the recovery. I've heard of issued with cwm.
Sent from my HTC0P3P7 using XDA Free mobile app
Click to expand...
Click to collapse
The reason i picked CWM over TWRP was because i'm familiar with it and like the UI.. TWRP just seems too basic looking. But my initial question still remains. Can i simply re-run the process over the top with TWRP or do i need to remove CWM before i can write TWRP to the device?
RyanH77 said:
The reason i picked CWM over TWRP was because i'm familiar with it and like the UI.. TWRP just seems too basic looking. But my initial question still remains. Can i simply re-run the process over the top with TWRP or do i need to remove CWM before i can write TWRP to the device?
Click to expand...
Click to collapse
I would highly suggest twrp either way though yea always just flash over in fastboot.
Sent from my HTC0P3P7 using XDA Free mobile app
cstrife999 said:
I would highly suggest twrp either way though yea always just flash over in fastboot.
Sent from my HTC0P3P7 using XDA Free mobile app
Click to expand...
Click to collapse
Ok well i'll give TWRP a go. But do i need a specific .img file? Because when i go onto the TWRP site to get the version i need, it only lists Sprint and Verizon for the One Max. I'm on International so surely need a GSM or Non-US variant surely? Or can i just use the M7 GSM version?
Thanks.
RyanH77 said:
Ok well i'll give TWRP a go. But do i need a specific .img file? Because when i go onto the TWRP site to get the version i need, it only lists Sprint and Verizon for the One Max. I'm on International so surely need a GSM or Non-US variant surely? Or can i just use the M7 GSM version?
Thanks.
Click to expand...
Click to collapse
Ok, now i've just redone this procedure exactly the same but with TWRP instead of CWM and it's doing exactly the same thing.. Why does it just go blank after saying "entering recovery" then boot as normal after about 20 secs? I really want root access but can't see how i'm going to get it if my phone won't boot into recovery.
RyanH77 said:
Ok, now i've just redone this procedure exactly the same but with TWRP instead of CWM and it's doing exactly the same thing.. Why does it just go blank after saying "entering recovery" then boot as normal after about 20 secs? I really want root access but can't see how i'm going to get it if my phone won't boot into recovery.
Click to expand...
Click to collapse
Ok.. I finally figured what was wrong.. The .img was too new a version and clearly my phone didn't like it.. So i used an older version and it's done the whole process perfectly. So to anyone else having the same problem, try an older version.
Ok, hang on.. It seems i might not be rooted.. I've installed TWRP, done my Nandroid backup installed Superuser and a few root checkers and one of them said i was rooted, while the others couldn't gain access, same with Superuser and SuperSU, they both say they can't access binaries etc.. Now i assumed once the phone said tampered, unlocked and had TWRP installed that it was rooted.. Is this the case? I have attached some thumbnails of various screengrabs so someone can tell me if i am or if something has gone wrong.. When i did it on my DHD it was never this hard to 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"
}