Can't manual update nook tablet to 1.4.1 and 1.4.2 - Barnes & Noble Nook Tablet

My nook tablet installed CWM boot. I want update to 1.4.1 and 1.4.2 after then. but I followed step by step : http://www.barnesandnoble.com/u/Software-Updates-NOOK-Tablet/379003187/ to manual update but . It had a error message :
"nook tablet update fail to verify whole-file signature"
Please help me.

Not sure why you want to go 1.4.1 first before 1.4.2, I went from 1.4.0 to 1.4.2 without any issue using the instructions in B&N page.
Maybe it's something with CWM, although I had my tablet rooted on 1.4.0, I didn't have CWM internal, I always use the bootable microSD CWM.
After update you have to root again.
Sent from my LG-P990 using Tapatalk

use recovery flasher to flash stock recovery and try to update again, it should work. CWM prevents OTA and manual patch. They require stock recovery.

albertwertz said:
use recovery flasher to flash stock recovery and try to update again, it should work. CWM prevents OTA and manual patch. They require stock recovery.
Click to expand...
Click to collapse
Thank you, but I installed CWM , I copied the file at : http://forum.xda-developers.com/showthread.php?t=1402190 to My SD Card and Power my NT. It booted to CWM.
Please help me.
Thank you.

kieuphongeg said:
Thank you, but I installed CWM , I copied the file at : http://forum.xda-developers.com/showthread.php?t=1402190 to My SD Card and Power my NT. It booted to CWM.
Please help me.
Thank you.
Click to expand...
Click to collapse
You didn't say how the suggestion Albert gave you worked or failed. That might be a good place to start if you haven't already. His suggestion would replace CWM which currently resides in your recovery partition with stock recovery and allow the updates you desire as they require stock recovery to function.
Good Luck!

Related

[Q] able to get in to CWM but can't boot into TNT 4.4

I installed CWM and TNT 4.4.0; and was able to boot once(first time). But once I powered down the gTab, It goes in to boot loop. I am able to boot into CWM and able to connect to my pC via USB Mass storage using CWM; please help me correctly install the TNT app.
thanks in advance,
I hope this helps!
Check out this thread and make sure you read the comments because you installed CWM.
http://forum.xda-developers.com/showthread.php?t=842000
Also, if you decide to upgrade to a custom ROM, you don't have to install CWM. You can do it in standard recovery, but there is another thread it in both:
http://forum.xda-developers.com/showthread.php?t=842004
Good luck!
i would try re-flashing the rom. maybe even re-download it to ensure that the file isn't incomplete or corrupt.
can I just install tntlite 4.3 or something that is older and upgrade to 4.4? Since I have the CWM installed already?
At this point I do get the Bootloader and mount error E: can't mount /dev/block/mmcblk3p2
Perhaps a good course of action would be:
1> Boot into CWM then partition the sdcard to 2048/0.
2> Follow direction in the second post to return to stock rom, then re-flash the rom using standard recovery (not with CWM).
If that does not work, then use nvflash method to return to stock and start over again http://forum.xda-developers.com/showthread.php?t=861950. I had to do this several times to get my gtablet functions the way it should.
Hope this helps.
tboneuncw said:
. . .
Also, if you decide to upgrade to a custom ROM, you don't have to install CWM. You can do it in standard recovery, but there is another thread it in both:
http://forum.xda-developers.com/showthread.php?t=842004
Good luck!
Click to expand...
Click to collapse
yes, I preferred the standard recovery method to install rom too. However, I have not been able to search for a method to install latest kernel without the use of CWM. Do you have a method?
mydave1 said:
Perhaps a good course of action would be:
1> Boot into CWM then partition the sdcard to 2048/0.
2> Follow direction in the second post to return to stock rom, then re-flash the rom using standard recovery (not with CWM).
If that does not work, then use nvflash method to return to stock and start over again http://forum.xda-developers.com/showthread.php?t=861950. I had to do this several times to get my gtablet functions the way it should.
Hope this helps.
Click to expand...
Click to collapse
What does partitioning of 2048/0 do?
use4all,
To answer your question, it may fix it.
When I hear boot loop, I think partition problem because partitioning often
does fix it.
1. Flash the tablet back to stock. Use the files in the instructions:
http://forum.xda-developers.com/showthread.php?t=861950
2. Install ClockWorkMod (CWM)
3. Reboot into CWM and go to the Advanced Menu -- Repartition to 2048 and 0, Fix Permissions
and Wipe Dalvik Cache. Return to Main Menu and Wipe Cache
and Wipe Factory Data.
4. Shut down and repeat Step 1.
5. At this point if all has gone well, you should have a "stock" working
tablet with "Bekit 1105" (AKA Stock Version 2638 on it.
6. Set up the wifi and almost immediately you should get an OTA (over the air)
Update notice. Do it and when you finish you should have a Stock 3588
tablet.
From there, you can move carefully to where you want to go and hopefully
won't have any more boot loops. I know this is a long process -- and once
in a while it doesn't work -- but I've done it with folks a pile of times and I
think it is the best procedure for your situation.
Good Luck,
Rev
2048/0 is an SD repartition. Think of it as a troubleshooting task just before having to resort to nvflash. It will wipe both /sdcard and /data, so keep that in mind.
Also, btw, if you have TNT Lite 4.3.0+, you can toggle back and forth between standard and cwm - it's called the "3588 Recovery Pack". Read my first post for details.
Ok, thanks for the help. I got to Stock ROM now.
Before I jump into reinstalling 4.4, let me ask this:
do I just copy the 4.4 into the GTab? and boot? or is there something I need to do before that?
4.4 install is just like the 4.3 install - just read my first post for details.
Thank you all for your help. I am up and running on TNTLite4.4. Love it so far..

[Q] Did NvFlash - What did I do Wrong?

I read and read - did not see an answer to my question - if so I did not understand.
I have ran the NvFlash and it appeared to go okay - but now my Gpad does is rotate back and forth between the Viewsonic and Gtablet screen.
I am stuck on what to do next.
Thanks very much for your help!
Same exact thing happened to me Friday night. I fixed it by partitioning to 2048 0 using CWM via NVFlash.
How do you do that?
Sorry to be so thick!!!!
I found the downloads for cwm - how do you access that with NvFlash?
You can flash the stock recovery images and swap in teh part9.img with the CWM recovery file taken from the cwm zip.
Basically, you need to extract the CWM recovery zip and get the recovery.img file. You rename this to part9.img and replace the part9.img file in the nvflash_stock 1105 directory wherever you have it.
Alternativly, you can put CWM recovery on the microsd card, the instructions are in the CWM recovery thread.
Finally, I had issues failing to boot when I was using a different nvflash.exe. You should use the 140KB nvflash file for the process outlined int eh stock recovery thread.
CWM and nvflash are 2 different things. Install cwm and repartition as suggested.
tgatlinjr said:
How do you do that?
Sorry to be so thick!!!!
I found the downloads for cwm - how do you access that with NvFlash?
Click to expand...
Click to collapse
Here's a step-by-step tutorial:
http://forum.xda-developers.com/showthread.php?t=1030042
Once you're into CWM just go to advanced and then partition to change to 2048 & 0.
Btw, since you're going to be changing two files in your NVFlash folder (part9.img & nvflash_gtablet.bat) you may want to copy them somewhere else on your pc so you can put them back after you're done.
I did manage to get it to boot and download the 3588 update but when it reboots and tries to apply the update it fails.
Any ideas?
tgatlinjr said:
I did manage to get it to boot and download the 3588 update but when it reboots and tries to apply the update it fails.
Any ideas?
Click to expand...
Click to collapse
One way is to get the 3588 zip from the forum here & download it to the root of the G Tablet. Rename it to update.zip & install with CWM. I'd also wide data/factory reset & wipe cache partition too.
I have installed CWM now with no problem.
The Gpad boots to Viewsonic Tap UI version1.0-2638
It then informs me that there is an update to 3588
It proceeds to download the update - asks me to accept and apply the update
States it will shutdown to apply this update - it does, reboots - and after a few seconds a triangle with an exclimation mark along side the little Android man pops up and will do nothing else.
I, also, downloaded the 3588.zip file as suggested in the previous reply and got the same result.
I wiped the cache and did the data factory reset as well.
Any ideas to where I can go from here as all of this is new to me?
Hi everyone - got it fixed.
I appreciate everyones help.

[Q] Nabi 2 UK update

I have a Nabi 2 UK for my son and had GAPPS installed but stayed on the 1.9.37 version as the OAT would not work.
I now see that I can get the tablet up to 4.1 and get GAPPS as well but I seem to be defeated at the last step every turn but the 'dead' android on it's back.
I don't have the original back up to start from.
I've gone to the 1937 stock image and via TWRP, the OAT'ed to 2.1, but the second 2.3 update fails with the dead android
I've tried 2311 which also fails in the same way.
I've seen some conversations on these boards but the file outlined are often out of bandwith and I can't comment on the threads to ask for help.
So now I'm back to 1.9.37 but I also can't seem to reinstate GAPP using Nabi Labs tools I as it braks the nabi mode and the tablet won't work.
All in all this is turing out to be a massive waste of time. Any suggestions how I can salavge this?
Cheers
Fulhair
Fulhair said:
I have a Nabi 2 UK for my son and had GAPPS installed but stayed on the 1.9.37 version as the OAT would not work.
I now see that I can get the tablet up to 4.1 and get GAPPS as well but I seem to be defeated at the last step every turn but the 'dead' android on it's back.
I don't have the original back up to start from.
I've gone to the 1937 stock image and via TWRP, the OAT'ed to 2.1, but the second 2.3 update fails with the dead android
I've tried 2311 which also fails in the same way.
I've seen some conversations on these boards but the file outlined are often out of bandwith and I can't comment on the threads to ask for help.
So now I'm back to 1.9.37 but I also can't seem to reinstate GAPP using Nabi Labs tools I as it braks the nabi mode and the tablet won't work.
All in all this is turing out to be a massive waste of time. Any suggestions how I can salavge this?
Cheers
Fulhair
Click to expand...
Click to collapse
Hi.
I had a similar issue (US ROM though). I had dead Android guys, messages in TWRP that I didn't have an operating system installed and all kinds of other issues. I really thought that I had bricked the Nabi as I was up against a wall and nothing I was finding online was working.
I have posted this before elsewhere -- this is what I did to get out of it:
I think when I was installing the JB version of TWRP I also tried to change the screenlock image not realizing that the process had changed for JB. I had a complete mess with very similar if not identical issues as you.
What I did:
1. Make sure TWRP 2.6.3.0 for Jellybean is on the Nabi.
2. Download the stock 2.3.11 ROM from the Nabi wiki site and unzip it into a folder on your PC.
3. Next you need to copy the 4 recovery files from your PC to your SD card. I put the SD card into my PC and copied the files over putting them into a TWRP back up folder on the SD card. Now, in order for Jellybean TWRP to recognize the backup, I had to fool it into thinking I had a "good" existing Jellybean TWRP backup and rename the TWRP backup folders to something like this:
TWRP\BACKUPS\0f41000001000000\2014-01-24--09-54-07 JRO03C\
4. Put the SD card back into the Nabi and then boot into TWRP mode.
5. Do a restore from there.
It *should* install a clean fresh copy of Jellybean on the Nabi. It does take what seems like an eternity for it to get past the spinning circle with the NABI logo when it's loading for the first time so be patient.
You may need to alter some of this since you are in the UK though.. but the main suggestion is to put whatever copy of the ROM onto an SD card (remember to follow the correct directory format for either ICS or JB) and then restore via TWRP to get you running.
2girlzdad said:
Hi.
I had a similar issue (US ROM though). I had dead Android guys, messages in TWRP that I didn't have an operating system installed and all kinds of other issues. I really thought that I had bricked the Nabi as I was up against a well and nothing I was finding online was working.
I have posted this before elsewhere -- this is what I did to get out of it:
I think when I was installing the JB version of TWRP I also tried to change the screenlock image not realizing that the process had changed for JB. I had a complete mess with very similar if not identical issues as you.
What I did:
1. Make sure TWRP 2.6.3.0 for Jellybean is on the Nabi.
2. Download the stock 2.3.11 ROM from the Nabi wiki site and unzip it into a folder on your PC.
3. Next you need to copy the 4 recovery files from your PC to your SD card. I put the SD card into my PC and copied the files over putting them into a TWRP back up folder on the SD card. Now, in order for Jellybean TWRP to recognize the backup, I had to fool it into thinking I had a "good" existing Jellybean TWRP backup and rename the TWRP backup folders to something like this:
TWRP\BACKUPS\0f41000001000000\2014-01-24--09-54-07 JRO03C\
4. Put the SD card back into the Nabi and then boot into TWRP mode.
5. Do a restore from there.
It *should* install a clean fresh copy of Jellybean on the Nabi. It does take what seems like an eternity for it to get past the spinning circle with the NABI logo when it's loading for the first time so be patient.
You may need to alter some of this since you are in the UK though.. but the main suggestion is to put whatever copy of the ROM onto an SD card (remember to follow the correct directory format for either ICS or JB) and then restore via TWRP to get you running.
Click to expand...
Click to collapse
Thanks for the outline. Sorry if I'm being a bit dim but how do I get the 2.6.3.0 TWRP onto it?
I've got the NaviLabs GUI and TWRP'd up to v 2.6.1.0 but need to get the Jelly Bean version.
I've tried the zip install with twrp-recovery-JBNV7AUS-263 but it just breaks TWRP and won't boot.
Thanks again.
Fulhair said:
Thanks for the outline. Sorry if I'm being a bit dim but how do I get the 2.6.3.0 TWRP onto it?
I've got the NaviLabs GUI and TWRP'd up to v 2.6.1.0 but need to get the Jelly Bean version.
I've tried the zip install with twrp-recovery-JBNV7AUS-263 but it just breaks TWRP and won't boot.
Thanks again.
Click to expand...
Click to collapse
Get whatever TWRP you want
http://forum.xda-developers.com/showpost.php?p=48891386&postcount=76
Follow this http://forum.xda-developers.com/showpost.php?p=49956448&postcount=49 to put that recovery in Nabilabgui except use
For XP
C:\Documents and Settings\username\Local Settings\Apps\2.0\xxx\xxx\nabixxxx\2\recovery\new
or Vista/7/8
C:\Users\username\appdata\local\apps\2.0\xxx\xxx\n abixxx\2\recovery\new
The post is for the JR I think the above will be right for the Nabi2, I'm mobile so I can't check.
aicjofs said:
Get whatever TWRP you want
http://forum.xda-developers.com/showpost.php?p=48891386&postcount=76
Follow this http://forum.xda-developers.com/showpost.php?p=49956448&postcount=49 to put that recovery in Nabilabgui except use
For XP
C:\Documents and Settings\username\Local Settings\Apps\2.0\xxx\xxx\nabixxxx\2\recovery\new
or Vista/7/8
C:\Users\username\appdata\local\apps\2.0\xxx\xxx\n abixxx\2\recovery\new
The post is for the JR I think the above will be right for the Nabi2, I'm mobile so I can't check.
Click to expand...
Click to collapse
Good advice. Thanks for the TWRP instructions,
I can now get the TWRP v2.6.3.0 on, but only the ICS version will boot, The Jelly bean install won't bring up the TWRP screens. I've even tried updating to 2311 from the ICS version and then trying to update to the TWRP JB version with no joy.
Now I can't even get the nabi to connect to the usb in Nabi Lab GUI This is doing my head in!!!
Fulhair said:
Good advice. Thanks for the TWRP instructions,
I can now get the TWRP v2.6.3.0 on, but only the ICS version will boot, The Jelly bean install won't bring up the TWRP screens. I've even tried updating to 2311 from the ICS version and then trying to update to the TWRP JB version with no joy.
Now I can't even get the nabi to connect to the usb in Nabi Lab GUI This is doing my head in!!!
Click to expand...
Click to collapse
If going to 2311 you need to update bootloader. That is in the addonfix zip. Then JB twrp should work.
aicjofs said:
If going to 2311 you need to update bootloader. That is in the addonfix zip. Then JB twrp should work.
Click to expand...
Click to collapse
Okay, so I managed to get back to TWRP 2.6.3.0 under ICS. I then install the 2311 rom, which succeeds. As per instructions, before I reboot I go back and try to install the addon zip in TWRP.
But I get an error
'E:Error executing updater binary in zip '/external_sdcard/addonzip'
Error flashing zip '/external_sdcard/addonzip'.
I'm not sure if the error is something with TWRP or the addon.zip.
One of the microsd I have won't show the addonzip and none of the other TWRP recovery roms..and yes I have checked the directory structure.
Any ideas?
Thanks
Fulhair said:
Okay, so I managed to get back to TWRP 2.6.3.0 under ICS. I then install the 2311 rom, which succeeds. As per instructions, before I reboot I go back and try to install the addon zip in TWRP.
But I get an error
'E:Error executing updater binary in zip '/external_sdcard/addonzip'
Error flashing zip '/external_sdcard/addonzip'.
I'm not sure if the error is something with TWRP or the addon.zip.
One of the microsd I have won't show the addonzip and none of the other TWRP recovery roms..and yes I have checked the directory structure.
Any ideas?
Thanks
Click to expand...
Click to collapse
Okay, I abandoned the addon.zip and went back to 2.1.27 rom and OAT over to get to the last update which failed.
Then installed the OAT2.zip via TWRP and bingo! Now working on Jelly Bean with Google Play - okay it's now the US version but it works
I would caution that the zip install had to be installed on the internal SD not the external one.
But otherwise a BIG thank you to all for building the tools to let me do the update and for your support.
Cheers:highfive:

[Q] Nook Tablet CMW Recovery

Hi, I am new to the whole jailbreaking. I followed this video (hZyfWpBJpiE) to root the tablet (6 gb).
In this process, I used NT16or8gbV47SDimagefile and I set the tablet to factory setting, deleted partitions, and deleted dalvik cache. I may have repeated this process because i thought it wasnt rooted because my screen looked different from the video guys tablet
Then followed this video (GZAQpeCtFi0) to install CWM Recovery 4.0.4.8. It booted to the recovery setting screen but I started seeing green lines to the right of my screen then it shut off to restart.
It wouldnt respond when I tried it again so I repeated the first process and tried again but still, same thing happens.
Does anyone have ideas on how to fix this?
Ultimately, I want to install the CM11...
Thanks in Advance
I used the Root Recovery Tools to run the 4.0.4.8
PfanneKuchenAngriff said:
Hi, I am new to the whole jailbreaking. I followed this video (hZyfWpBJpiE) to root the tablet (6 gb).
In this process, I used NT16or8gbV47SDimagefile and I set the tablet to factory setting, deleted partitions, and deleted dalvik cache. I may have repeated this process because i thought it wasnt rooted because my screen looked different from the video guys tablet
Then followed this video (GZAQpeCtFi0) to install CWM Recovery 4.0.4.8. It booted to the recovery setting screen but I started seeing green lines to the right of my screen then it shut off to restart.
It wouldnt respond when I tried it again so I repeated the first process and tried again but still, same thing happens.
Does anyone have ideas on how to fix this?
...
Click to expand...
Click to collapse
You should not have deleted any partition. Also I am not aware of a CWM v4.0.4.8 for the Nook Tablet, are you sure you downloaded tools intended for the Nook Tablet?
I'd suggest that you try the recovery-to-stock method posted at http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/. See http://forum.xda-developers.com/showthread.php?t=2575489 for more info/pointers.
digixmax said:
You should not have deleted any partition. Also I am not aware of a CWM v4.0.4.8 for the Nook Tablet, are you sure you downloaded tools intended for the Nook Tablet?
I'd suggest that you try the recovery-to-stock method posted at http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/. See http://forum.xda-developers.com/showthread.php?t=2575489 for more info/pointers.
Click to expand...
Click to collapse
Thanks for your reply. I was able to get it back to factory setting but when following direction i get a message that says E: unable to mound /bootdata
I have no idea what is going on anymore
PfanneKuchenAngriff said:
Thanks for your reply. I was able to get it back to factory setting ...
Click to expand...
Click to collapse
Meaning you were able to get your NT back to running stock ROM?
but when following direction i get a message that says E: unable to mound /bootdata
...
Click to expand...
Click to collapse
Which direction are you referring to?
digixmax said:
Meaning you were able to get your NT back to running stock ROM?
Which direction are you referring to?
Click to expand...
Click to collapse
I was able to get back to running stock ROM. Then I followed the other linke ttp://forum.xda-developers.com/show....php?t=2575489
After I went through the directions, I got the unable to mount error
Which version of recovery did you use?
digixmax said:
Which version of recovery did you use?
Click to expand...
Click to collapse
I rooted the NT with: NT16or8gbV47SDimagefile.img
I used this version: flashable_CWM_6.0.4.8_chrmhoffmann
And I have these to install:
cm-11-20141102-NIGHTLY-acclaim
gapps-kk-20140606-signed
I think I tried 3 different ways to install it...do I need both TWRP and CMW recovery?
I read that TWRP was buggy and when it didn't work, I tried CMW recovery.
Right now, I have the NT back to rooted stated and nothing else. I followed this direction last, I think:
http://forum.xda-developers.com/showthread.php?t=2692403
The other video said I can use the root flasher app to run the CMW recovery so I tried that as well
Thanks
PfanneKuchenAngriff said:
I rooted the NT with: NT16or8gbV47SDimagefile.img
I used this version: flashable_CWM_6.0.4.8_chrmhoffmann
And I have these to install:
cm-11-20141102-NIGHTLY-acclaim
gapps-kk-20140606-signed
I think I tried 3 different ways to install it...do I need both TWRP and CMW recovery?
I read that TWRP was buggy and when it didn't work, I tried CMW recovery.
Right now, I have the NT back to rooted stated and nothing else. I followed this direction last, I think:
http://forum.xda-developers.com/showthread.php?t=2692403
The other video said I can use the root flasher app to run the CMW recovery so I tried that as well
Thanks
Click to expand...
Click to collapse
Since your NT is running (rooted) stock, you'd need SD-based recovery to flash CM/Gapps onto EMMC. Flashing CM11 requires CWM version later than 6.0.4.5 or TWRP version later than 2.6.3.0, unfortunately there does not seem to be any compilation of SD-based CWM versions 6.0.4.5 or later for the Nook Tablet, hence we are stuck with TWRP 2.6.3.0+ as the only SD-based recovery for flashing CM11 onto the NT. (The flashable_CWM_6.0.4.8_chrmhoffmann is for flashing CWM 6.0.4.8 onto your NT EMMC to replace the stock recovery; the root flasher app recovery is likely a too old recover version to be compatible with CM11).
A potential alternative course of action is to first flash CM10.x for which there are SD-based CWM recovery available (see http://forum.xda-developers.com/showpost.php?p=51377882&postcount=163), then upgrade from CM10.x to CM11 (see http://forum.xda-developers.com/showthread.php?t=2670589).
digixmax said:
Since your NT is running (rooted) stock, you'd need SD-based recovery to flash CM/Gapps onto EMMC. Flashing CM11 requires CWM version later than 6.0.4.5 or TWRP version later than 2.6.3.0, unfortunately there does not seem to be any compilation of SD-based CWM versions 6.0.4.5 or later for the Nook Tablet, hence we are stuck with TWRP 2.6.3.0+ as the only SD-based recovery for flashing CM11 onto the NT. (The flashable_CWM_6.0.4.8_chrmhoffmann is for flashing CWM 6.0.4.8 onto your NT EMMC to replace the stock recovery; the root flasher app recovery is likely a too old recover version to be compatible with CM11).
A potential alternative course of action is to first flash CM10.x for which there are SD-based CWM recovery available (see http://forum.xda-developers.com/showpost.php?p=51377882&postcount=163), then upgrade from CM10.x to CM11 (see http://forum.xda-developers.com/nook-hd/general/how-to-updating-hd-hd-internal-emmc-to-t2863171).
Click to expand...
Click to collapse
I think I was able to get through the first step in loading cm 10...
Is it normal for cyanoboot to show up before the cyanogenmod flash??
If normal, I will try to upgrade to cm11. This is a huge improvement though Thanks!
PS. the update from CM10x to CM11 seems to be only for HD or HD+...would this work with NT?
PfanneKuchenAngriff said:
I think I was able to get through the first step in loading cm 10...
Is it normal for cyanoboot to show up before the cyanogenmod flash??
Click to expand...
Click to collapse
Yes
PS. the update from CM10x to CM11 seems to be only for HD or HD+...would this work with NT?
Click to expand...
Click to collapse
Sorry, the correct URL for the NT CM10.x to CM11 update is http://forum.xda-developers.com/showthread.php?t=2670589.
digixmax said:
Yes
Sorry, the correct URL for the NT CM10.x to CM11 update is http://forum.xda-developers.com/showthread.php?t=2670589.
Click to expand...
Click to collapse
Thanks so much for all your help! For this step do I upload the files straight into the device (not the SD card)? Also, do i use the flashable_CWM_6.0.4.5_chrmhoffmann.zip or could I use the 6.0.4.8?
PfanneKuchenAngriff said:
Thanks so much for all your help! For this step do I upload the files straight into the device (not the SD card)?
Click to expand...
Click to collapse
Either way would work.
Also, do i use the flashable_CWM_6.0.4.5_chrmhoffmann.zip or could I use the 6.0.4.8?
Click to expand...
Click to collapse
Your choice.
FWIW I am using 6.0.4.8 on my NT (running CM11 snapshot M12).

Returning to 5.1 after rolling back to 5.0.2

Hello, im facing an issue.
Ive made a rollback to 5.0.2 by this guide:
http://forum.xda-developers.com/dell-venue/general/7840-succeed-to-unbrick-t3205024
But now when i want to go back to 5.1 i cant.
I cant install ota, even through CWM. Also there is no recovery, at least i cant get into it, when I press "Recovery mode" in bootloader it just rebooting back to bootloader. No changes, nothing.
But 5.0.2 working fine(just cant do factory reset)
Will be gratefull for any assisstance
You'll need the droidboot version that uses twrp instead of cwm. With that, installing the 5.1 update works just fine.
Sent from my Venue 8 7840 using XDA Free mobile app
Can you please share the link?
PS: How to fix stock recovery? any solution for this?
When im trying to install using TWRP(like cwm tethered) im receiving errors
Updating IFWI....
Error executing updater binary
Error flashing zip
Unable to mount /Data
...done
Unable to mount storage
olvrick said:
When im trying to install using TWRP(like cwm tethered) im receiving errors
Updating IFWI....
Error executing updater binary
Error flashing zip
Unable to mount /Data
...done
Unable to mount storage
Click to expand...
Click to collapse
do you mind giving a bit more information?
What version of TWRP are you using?
Is the update on a sdcard or internal memory?
Can you export the error logs from twrp and post it to pastebin or sth like that?
toxic_garden said:
do you mind giving a bit more information?
What version of TWRP are you using?
Is the update on a sdcard or internal memory?
Can you export the error logs from twrp and post it to pastebin or sth like that?
Click to expand...
Click to collapse
Im using TWRP from tethering CWM package for rooting^ IntelAndroid-FBRL-07-24-2015
Update downloaded here from this post: http://forum.xda-developers.com/showpost.php?p=60632439&postcount=21
Memory: external sd card
olvrick said:
Im using TWRP from tethering CWM package for rooting^ IntelAndroid-FBRL-07-24-2015
Update downloaded here from this post: http://forum.xda-developers.com/showpost.php?p=60632439&postcount=21
Memory: external sd card
Click to expand...
Click to collapse
don't use the update from this link. I don't want to say it's not working but at least for me it was the best (and simplest) option to boot up 5.0.1 after fresh installation and let the tablet download the 5.1 update by itself. After download is complete, it can be installed via TWRP-Recovery without problems.
toxic_garden said:
don't use the update from this link. I don't want to say it's not working but at least for me it was the best (and simplest) option to boot up 5.0.1 after fresh installation and let the tablet download the 5.1 update by itself. After download is complete, it can be installed via TWRP-Recovery without problems.
Click to expand...
Click to collapse
Im facing an issue that neither CWM nor TWRP couldnt mount /data/ partition
Thanks
toxic_garden said:
don't use the update from this link. I don't want to say it's not working but at least for me it was the best (and simplest) option to boot up 5.0.1 after fresh installation and let the tablet download the 5.1 update by itself. After download is complete, it can be installed via TWRP-Recovery without problems.
Click to expand...
Click to collapse
Thanks, managed to flash 5.1 but still cant go inside stock recovery. Cant do factory reset...
Any ideas, how to fix this?

Categories

Resources