I need help to fix my tab,
I've been running pershoots OC kernel with task's roms for several months with no problems and i've been keeping up to date with each version with out any problems.
I just rebooted my tab today and now suddenly out of the blue, the screen shows static and corrupted rbg lines after a few seconds of the samsung logo. And now it is stuck like this after repeatedly trying to turn my device on. I can get into CWM recovery but i dont a restore file on it because i moved them off my tab to my PC to save space.
Is there anyway to move the files back on to the tab to restore it or maybe move the stock kernel so i can flash it and see if that fixes it?
If you don't care about the data in your tab (all your apps and the /sdcard partition), you could try returning to stock via Odin. Here is a good guide (is the last part "Re-“Stocking” Yer System…"): The Guide
Other option (I recommend this one) is adb, in cwm just push the files you want to flash to the /sdcard .
Thanks! I'll try by android debug bridge and see if i can figure this out..
I have adb installed and it works but when i push the zip to /sdcard/ it doesnt show up on CWM install zip from sdcard menu option, i also tried to push it to /mnt/sdcard/ and the files doesnt show up.
I'm at a loss here the cmd prompt doesnt give any errors after the zip transfer
Mercatorn said:
I have adb installed and it works but when i push the zip to /sdcard/ it doesnt show up on CWM install zip from sdcard menu option, i also tried to push it to /mnt/sdcard/ and the files doesnt show up.
I'm at a loss here the cmd prompt doesnt give any errors after the zip transfer
Click to expand...
Click to collapse
Are you mounting the partition? My guess is you forgot to do it.
Enter the follow commands (one by one) in the terminal (cmd prompt):
Code:
adb shell
Code:
mount /data
Code:
exit
Code:
adb push fileyouwanttoflash.zip /data/media
Now the file should be in /sdcard, just install it from cwm.
If at the moment you're trying to choose the zip from sdcard you get an error telling you "Couldn't open directory" and "No files found", reboot cwm.
Other way to do it is in cwm (so you don't have to do the "adb shell" and "adb mount")
In cwm, choose "install zip from sdcard", then "choose zip from sdcard", then "+++++Go Back+++++"
And from your cmd promt:
Code:
adb push fileyouwanttoflash.zip /sdcard/
Now, flash the file from cwm. (Again, if there's some error, reboot cwm).
Even though clockwork ROM Manager is installed,
https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager
When I try to run it - it says: "you must have ClockwordMod Recovery installed before continuing! Install the recovery thropugh ROM Manager first"
Normally you would just download it but how is this done on a phone without internet connection, can I download the .apk file somewhere then move it to phone? Android phones are Motorola Cliq and CliqXT.
c627627 said:
Even though clockwork ROM Manager is installed,
https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager
When I try to run it - it says: "you must have ClockwordMod Recovery installed before continuing! Install the recovery thropugh ROM Manager first"
Normally you would just download it but how is this done on a phone without internet connection, can I download the .apk file somewhere then move it to phone? Android phones are Motorola Cliq and CliqXT.
Click to expand...
Click to collapse
ClockworkMod recovery is not an application (.apk file). It's an image file. You can get the images here: http://clockworkmod.com/rommanager.
Thank you. How do you install the capability to run the image recovery process by simply running it from the ClockwordMod App, not by manually rebooting?
In other words, on a phone with internet access, you simply "Install the recovery thropugh ROM Manager first".
But how do you install it manually without internet access. How do you install the image file you linked to?
c627627 said:
Thank you. How do you install the capability to run the image recovery process by simply running it from the ClockwordMod App, not by manually rebooting?
In other words, on a phone with internet access, you simply "Install the recovery thropugh ROM Manager first".
But how do you install it manually without internet access. How do you install the image file you linked to?
Click to expand...
Click to collapse
See here: http://wiki.cyanogenmod.com/wiki/Motorola_Cliq:_Full_Update_Guide and follow the "Installing a Custom Recovery Image" section. Change the names as needed.
I'm not sure we understand each other so let me try to clarify and by the way thanks for your help:
Goal:
1. From within running CynogenMod launch ROM Manager >
2. Manage and Restore Backups >
3. Select exiting backup > Restore > OK
It automatically reboots and does its thing.
So now, if you have a phone on which ROM Manager is not installed, you install it and launch it from already running CyanogenMod *however* you get this message:
"you must have ClockwordMod Recovery installed"
It then simply downloads something and from then on you are able to use the ROM Manager to restore existing backups not by custom rebooting but by simply running it from within a running CyanogenMod.
Isn't the image file you linked to for custom booting into the restore environment from which you run the restore? I am trying to "run" the restore by simply lunching the ROM Manager which then itself reboots and runs the restore automatically.
What is it exactly that is installed when you get this message so that I can install it on a phone without an internet connection.
I know how to custom boot by holding the button etc. I just want to not custom boot and have it launch automatically by simply using a shortcut and launching the restore process which itself reboots and does its thing.
c627627 said:
I'm not sure we understand each other so let me try to clarify and by the way thanks for your help:
Goal:
1. From within running CynogenMod launch ROM Manager >
2. Manage and Restore Backups >
3. Select exiting backup > Restore > OK
It automatically reboots and does its thing.
So now, if you have a phone on which ROM Manager is not installed, you install it and launch it from already running CyanogenMod *however* you get this message:
"you must have ClockwordMod Recovery installed"
It then simply downloads something and from then on you are able to use the ROM Manager to restore existing backups not by custom rebooting but by simply running it from within a running CyanogenMod.
Isn't the image file you linked to for custom booting into the restore environment from which you run the restore? I am trying to "run" the restore by simply lunching the ROM Manager which then itself reboots and runs the restore automatically.
What is it exactly that is installed when you get this message so that I can install it on a phone without an internet connection.
I know how to custom boot by holding the button etc. I just want to not custom boot and have it launch automatically by simply using a shortcut and launching the restore process which itself reboots and does its thing.
Click to expand...
Click to collapse
The image I linked to is the "thing" Rom Manager downloads when it gives that message (if you have an internet connection). Flashing that file and linking it to Rom Manager will remove that error.
Got it.
Selecting Flash ClockworkMod Recovery from ROM manager to try to use the img file you linked to results in an "error while downloading from server. Please make sure that you have a stable internet connection..."
So that does not work for the thread topic, which is doing this w/o internet connection.
Will try the Android SDK Tools method.
0. The Cliq XT is known as Zeppelin.
1. Install Motorola USB drivers:
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
2. Install Java SE Runtime Environment (JRE): http://www.oracle.com/technetwork/java/javase/downloads/
3. Get Android SDK zip: http://developer.android.com/sdk/
4. Unzip it and start SDK Manager.exe and download Android SDK Tools.
5. Get ClockworkMod Recovery, for example:
http://download.clockworkmod.com/recoveries/recovery-clockwork-4.0.0.5-zeppelin.img
Copy recovery-clockwork-4.0.0.5-zeppelin.img to
Android SDK folder android-sdk-windows\platform-tools
7. Phone Settings > Applications > Unknown sources (select green check mark to activate it)
Settings > Applications > Development > Enable USB Debugging
Make sure the phone is rooted. Check if Superuser icon is in the drawer menu.
*** Connect the phone to computer but DO NOT enable USB Drive ***
8. Use DOS to navigate to the android-sdk-windows\platform-tools directory
for example, if the folder location is C:\android-sdk-windows\platform-tools
then in type this in DOS:
c:
cd android-sdk-windows\platform-tools
adb shell
su
***You must press on Allow on the phone when prompted***
cd /sdcard/
flash_image recovery recovery-clockwork-4.0.0.5-zeppelin.img
Hi there,
I bought ZTE U819 and I was trying to replace the Chinese recovery, but I chose wrong recovery version by mistake, so:
- I Can´t access to my device recovery (Up Volume + power).When I try to enter, the device always restart
- I Can´t access to download mode (It would be because the bootloader was deleted? mobileuncle tools says (when I try to reboot into bootloader mode) "MTK android have not bootloader mode")
- The device doesn´t recognize the external SD and internal storage either but if I search in the system folder "data", I can see all the apps I´ve installed with iAPK.exe)
- I only can access to system folder through root explorer
- It´s rooted
The only way to install apk is with iAPK.exe
* I tried to edit vold.fstab but didn´t work.
* I tried to install the chinese original recovery from adb but I couldn´t, because when I write down fastboot don´t find any device and always says "waiting for devices" (I have installed all zte drivers at least I think so...)
* I tried to copy the correct recovery to "data" system folder through android commander, and I got, then I copied the recovery in "data" system folder and I tried to flash with terminal emulator, but it didn´t work
* I tried to flash other ROMs (I tried to install 6) which I copied to "data" system folder with Flash Gordon APK but it always says "Is not a valid flashable ZIP"
What can I do to sort it out?
Could I replace any folder from the original .ZIP ROM, I´ve installed in my device, to the system folder through android commander?
If it´s necessary, I can upload all the system folders from the device and anyone could check them and find the problem.
Thank you ever so much!!
Any advice?
Nobody can help me?
bebito0077 said:
Nobody can help me?
Click to expand...
Click to collapse
I've the same problem, what is the solution?
I am bit late.. But why don't you flash stock ROM via SP Flash Tools, and flash correct recovery once again?
(Format everything except bootloader)
Hi Guys,
I'm hoping someone can help me here with unbricking my daughters Nabi 2 tablet.
The long story short is that I've tried to update to the latest OTA with TWRP 2.3.3.0 (Nabi 1.9.37) and gapps installed in the past (in order to have google play services).
After downloading the OTA and successfull file verification it booted into TWRP mode and this is when things went wrong...
As I wasn't sure about how to even leave the TWRP mode I have hit few things by accident (I think one of them asked me if I want to wipe my ROM and I said YES + when I was after that trying to reboot the tablet it gave me a warning saying something like "you have no OS installed - are you sure to reboot?).
Now, of course due to my stupid actions it doesn't work - stuck on Nabi boot logo and when I try to pres Volume+ and Power together it gives me the screen with 4 options to choose from (Boot Normally, Fastboot Protocol, Recovery Kernel, Forced Recovery) but I still can't select/move the highlighted item. All what I'm able to do now is to power it off by holding the power button pressed for couple seconds.
Based on your experience here - is there anything that can be done or is it a "real brick" and we need to buy something new for her?
Thank you for any suggestions.
Hi,
I managed to boot into TWRP somehow...
Could someone please direct me how I can re-flash it with a Nabi 2 UK OS (and where I can source the file from if possible at all)?
Cheers,
T1000
termostat1000 said:
Hi,
I managed to boot into TWRP somehow...
Could someone please direct me how I can re-flash it with a Nabi 2 UK OS (and where I can source the file from if possible at all)?
Cheers,
T1000
Click to expand...
Click to collapse
Try sections 9 and 10. http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Hi,
Using NabiLab I managed to load stock 1.9.37 through TWRP.
At the moment tablet will start, let me through the initial setup wizard and go into normal mode from when it was new (no Google services available).
When I try to install gapps (TWRP mode) using NabiLab it goes into endless boot loop showing just a splash screen of the screen lock and reloads again.
I tried also bringing it more to factory condition but it is not recognised in NabiLab when android is fully booted (even though PC can see it). I tried different drivers but without too much luck. When in TWRP mode it comes up as Alcatel ADB Device and when adroid is booted it comes up as a storage device rather than ADB.
I feel I'm pretty close but I need just a hint how to solve it finally without bricking it for real...
Cheers
T
termostat1000 said:
Hi,
Using NabiLab I managed to load stock 1.9.37 through TWRP.
At the moment tablet will start, let me through the initial setup wizard and go into normal mode from when it was new (no Google services available).
When I try to install gapps (TWRP mode) using NabiLab it goes into endless boot loop showing just a splash screen of the screen lock and reloads again.
I tried also bringing it more to factory condition but it is not recognised in NabiLab when android is fully booted (even though PC can see it). I tried different drivers but without too much luck. When in TWRP mode it comes up as Alcatel ADB Device and when adroid is booted it comes up as a storage device rather than ADB.
I feel I'm pretty close but I need just a hint how to solve it finally without bricking it for real...
Cheers
T
Click to expand...
Click to collapse
Pretty hard to brick a Nabi2.
Why did you choose 1.9.37? Isn't the latest 2.3.2 and already has Gapps?
When in Android do you have ADB turned on in Developer options?
Is this the procedure you used?
a) Download the ROM for your device in section 10
b) Boot to TWRP (see above for instructions)
c) Do a backup of just the boot partition in TWRP.
- Click Restore tab
- Just check "boot" and nothing else.
- Swipe to Backup
d) Eject the external SD from the tablet and place in the computer
- Note: You should unmount the card from the mount tab in TWRP before ejecting it. (Uncheck the box next to external SD)
e) Connect the SD card to you computer
f) On the SD card navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
g) Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
h) Unzip the ROM file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. Inside the the "yourfolder" directory.
i) Download the bootloader zip for your device from section 10
j) Copy it to the external SD in a location you will remember. This will be for the bootloader update.
k) Eject the SD card from your computer (safely eject it)
l) Install SD card in Nabi
- After inserted in tablet go to TWRP mount tab and check the box to mount the SD card
m) Go to restore tab, and find the backup under the "yourfolder" you made and unzipped the files to.
n) You should be able to select boot, system, and addon and skip the others.
o) If everything restores then go to TWRP install tab, find the bootloader.zip you downloaded and install it.
p) Reboot
Code:
[U][B]Nabi2 Original United Kingdom (NABI-NV7A-UK)[/B][/U]
Version 2.3.2[URL="https://www.androidfilehost.com/?fid=24269982087011751"] Download[/URL]
ROM Mirror[URL="http://www.nabtabhacks.com/downloads/232UKstock.zip"] Download[/URL]
Bootloader [URL="https://www.androidfilehost.com/?fid=24269982087013995"] Download[/URL]
aicjofs said:
Pretty hard to brick a Nabi2.
Why did you choose 1.9.37? Isn't the latest 2.3.2 and already has Gapps?
When in Android do you have ADB turned on in Developer options?
Is this the procedure you used?
a) Download the ROM for your device in section 10
b) Boot to TWRP (see above for instructions)
c) Do a backup of just the boot partition in TWRP.
- Click Restore tab
- Just check "boot" and nothing else.
- Swipe to Backup
d) Eject the external SD from the tablet and place in the computer
- Note: You should unmount the card from the mount tab in TWRP before ejecting it. (Uncheck the box next to external SD)
e) Connect the SD card to you computer
f) On the SD card navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
g) Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
h) Unzip the ROM file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. Inside the the "yourfolder" directory.
i) Download the bootloader zip for your device from section 10
j) Copy it to the external SD in a location you will remember. This will be for the bootloader update.
k) Eject the SD card from your computer (safely eject it)
l) Install SD card in Nabi
- After inserted in tablet go to TWRP mount tab and check the box to mount the SD card
m) Go to restore tab, and find the backup under the "yourfolder" you made and unzipped the files to.
n) You should be able to select boot, system, and addon and skip the others.
o) If everything restores then go to TWRP install tab, find the bootloader.zip you downloaded and install it.
p) Reboot
Code:
[U][B]Nabi2 Original United Kingdom (NABI-NV7A-UK)[/B][/U]
Version 2.3.2[URL="https://www.androidfilehost.com/?fid=24269982087011751"] Download[/URL]
ROM Mirror[URL="http://www.nabtabhacks.com/downloads/232UKstock.zip"] Download[/URL]
Bootloader [URL="https://www.androidfilehost.com/?fid=24269982087013995"] Download[/URL]
Click to expand...
Click to collapse
Hi aicjofs,
I followed the steps above except step c which I haven't done.
So it looked good with the NabiLab built in 1.9.37 and it seemed to load fine with my TWRP 2.3.3.0 but it was hgoing into this endless boot loop after trying to install gapps. BTW I went for 1.9.37 as it came with NabiLab and turned right.
After your reply I've donwloaded the 232UK stock rom and bootloader. Copied both onto SD card - at that stage it would let me do a restore directly from the SD card so I've copied the 232UK rom into internal memory. Restore process went OK and at the end I've installed its dedicated bootloader...
Right now the situation is that I can only boot into TWRP but restore doesn't show any available roms (both internal or external memory) even though there is backup folder on the SD card.
What worries me the most is when I go to advanced / file manager / sdcard (internal memory) in TWRP mode it doesn't show any files or folders there. When I try to dipslpay tablet information in NabiLab it shows the external SD card properties properly (capacity/free space) but on the internal memory it says "Size df:KB Free can'tKB used find".
Does it mean it has wiped all the internal memory down to zero? Would this be the reason for recovery no being able to identify the roms on external SD card too?
Looking at the log in TWRP mode it is filled with entries like
E:Unable to mount '/data'
E:Unable to mount '/cache'
E:Can't open /cache/recovery/last_install
E:Can't open (No such file or directory)
What a pain is this thing, honestly...
termostat1000 said:
Hi aicjofs,
I followed the steps above except step c which I haven't done.
So it looked good with the NabiLab built in 1.9.37 and it seemed to load fine with my TWRP 2.3.3.0 but it was hgoing into this endless boot loop after trying to install gapps. BTW I went for 1.9.37 as it came with NabiLab and turned right.
After your reply I've donwloaded the 232UK stock rom and bootloader. Copied both onto SD card - at that stage it would let me do a restore directly from the SD card so I've copied the 232UK rom into internal memory. Restore process went OK and at the end I've installed its dedicated bootloader...
Right now the situation is that I can only boot into TWRP but restore doesn't show any available roms (both internal or external memory) even though there is backup folder on the SD card.
What worries me the most is when I go to advanced / file manager / sdcard (internal memory) in TWRP mode it doesn't show any files or folders there. When I try to dipslpay tablet information in NabiLab it shows the external SD card properties properly (capacity/free space) but on the internal memory it says "Size df:KB Free can'tKB used find".
Does it mean it has wiped all the internal memory down to zero? Would this be the reason for recovery no being able to identify the roms on external SD card too?
Looking at the log in TWRP mode it is filled with entries like
E:Unable to mount '/data'
E:Unable to mount '/cache'
E:Can't open /cache/recovery/last_install
E:Can't open (No such file or directory)
What a pain is this thing, honestly...
Click to expand...
Click to collapse
My fault. I forgot to tell you once you update the bootloader you need to use TWRP for Jellybean, you are still using TWRP for Ice Cream Sandwich .
Code:
[B][U]Nabi2 Original (NABI-NV7A)[/U][/B]
Ice Cream Sandwich TWRP 2.6.3[URL="http://forum.xda-developers.com/attachment.php?attachmentid=2586828&d=1392743412"] Download[/URL]
Jellybean TWRP 2.8.5[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3211498&d=1426404068"] Download[/URL]
KitKat TWRP 2.8.7[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3473994&d=1442276115"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2074501"]Link[/URL]
At that point you can try to restore the 2.3.2 ROM again. Or try the 2.2 ROM http://forum.xda-developers.com/showpost.php?p=50341726&postcount=85
aicjofs said:
My fault. I forgot to tell you once you update the bootloader you need to use TWRP for Jellybean, you are still using TWRP for Ice Cream Sandwich .
Code:
[B][U]Nabi2 Original (NABI-NV7A)[/U][/B]
Ice Cream Sandwich TWRP 2.6.3[URL="http://forum.xda-developers.com/attachment.php?attachmentid=2586828&d=1392743412"] Download[/URL]
Jellybean TWRP 2.8.5[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3211498&d=1426404068"] Download[/URL]
KitKat TWRP 2.8.7[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3473994&d=1442276115"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2074501"]Link[/URL]
At that point you can try to restore the 2.3.2 ROM again. Or try the 2.2 ROM http://forum.xda-developers.com/showpost.php?p=50341726&postcount=85
Click to expand...
Click to collapse
Forgive me please but I'm not entirely sure how to load this TWRP 2.8.5 for JellyBean on it with TWRP 2.3.3.0 in place..
Cheers
termostat1000 said:
Forgive me please but I'm not entirely sure how to load this TWRP 2.8.5 for JellyBean on it with TWRP 2.3.3.0 in place..
Cheers
Click to expand...
Click to collapse
You will need to use fastboot to load it. If you have a nabilab folder it already has fastboot available. So using the procedure below you couldn't download the ZIP file I linked in post above. Extract the from the zip the recovery.img or twrp-recovery.img and put it in the nabilab folder. (Im puling the procedure from http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119 )
1) To load TWRP we will be in the fastboot operational mode(see section 3)
Device powered off:
-Depending on device press and hold the power and vol - keys OR power and vol + key. Some will boot straight to recovery, and others will come to the "bootloader" screen. We want the bootloader.
-To enter fastboot use vol+ and vol- to highlight and select fastboot protocol. (Device will need to be plugged in to computer and fastboot driver installed before the screen will change)
Device powered on:
-Use ADB and execute from the command line:
Code:
adb reboot-bootloader
2) USB plugged in and Fastboot/Bootoader Driver loaded(see section 4) verify with windows device manager if needed.
3) Download the TWRP zip file for your device from TWRP list below(see section 8)
4) Extract the file to the location your are running your command prompt(see section 6)
-The file will be called twrp-recovery.img or recovery.img
5) Depending on the name of the file in step 4, load TWRP by typing at the command prompt:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery twrp-recovery.img
aicjofs said:
You will need to use fastboot to load it. If you have a nabilab folder it already has fastboot available. So using the procedure below you couldn't download the ZIP file I linked in post above. Extract the from the zip the recovery.img or twrp-recovery.img and put it in the nabilab folder. (Im puling the procedure from http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119 )
1) To load TWRP we will be in the fastboot operational mode(see section 3)
Device powered off:
-Depending on device press and hold the power and vol - keys OR power and vol + key. Some will boot straight to recovery, and others will come to the "bootloader" screen. We want the bootloader.
-To enter fastboot use vol+ and vol- to highlight and select fastboot protocol. (Device will need to be plugged in to computer and fastboot driver installed before the screen will change)
Device powered on:
-Use ADB and execute from the command line:
Code:
adb reboot-bootloader
2) USB plugged in and Fastboot/Bootoader Driver loaded(see section 4) verify with windows device manager if needed.
3) Download the TWRP zip file for your device from TWRP list below(see section 8)
4) Extract the file to the location your are running your command prompt(see section 6)
-The file will be called twrp-recovery.img or recovery.img
5) Depending on the name of the file in step 4, load TWRP by typing at the command prompt:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery twrp-recovery.img
Click to expand...
Click to collapse
Hi,
Thank you very much for your help but it clearly looks that this is way beyond my knowledge on how to use all of these fastboot, command, adb and so on...
I regret I ever touched the thing at all.
So there is absolutely no easy way - command line is a must from where I am right now?
termostat1000 said:
Hi,
Thank you very much for your help but it clearly looks that this is way beyond my knowledge on how to use all of these fastboot, command, adb and so on...
I regret I ever touched the thing at all.
So there is absolutely no easy way - command line is a must from where I am right now?
Click to expand...
Click to collapse
Its not a must but easiest to try and walk you through. Which version of Nabilab are you using? You could move some files around and still use Nabilab. Up to you which way to go forward. I'll try and help.
aicjofs said:
Its not a must but easiest to try and walk you through. Which version of Nabilab are you using? You could move some files around and still use Nabilab. Up to you which way to go forward. I'll try and help.
Click to expand...
Click to collapse
Hi,
I'm not so much afraid of copy/paste for cmd... the biggest fear is that I don't know anything about ADB, fasboot etc. So when your instruction in previous post says use ADB and I purely don't know what it means.
I think if the option is there I'd like to ask if you could help with restoring it with Nabilab.
Thanks a million for your help!
T
termostat1000 said:
Hi,
I'm not so much afraid of copy/paste for cmd... the biggest fear is that I don't know anything about ADB, fasboot etc. So when your instruction in previous post says use ADB and I purely don't know what it means.
I think if the option is there I'd like to ask if you could help with restoring it with Nabilab.
Thanks a million for your help!
T
Click to expand...
Click to collapse
Which version of Nabilab are you using? Is it the commandline version. Black window, where you have to use keyboard to make selections?
aicjofs said:
Which version of Nabilab are you using? Is it the commandline version. Black window, where you have to use keyboard to make selections?
Click to expand...
Click to collapse
Hi,
I'm using Nabilab ver 2 - black windows with keyboard made selections.
termostat1000 said:
Hi,
I'm using Nabilab ver 2 - black windows with keyboard made selections.
Click to expand...
Click to collapse
Find the Nabilab folder on your computer. Open the "recovery" folder. Then open the "stock" folder. Inside it there is recovery.img file. Rename it to recoverystock.img.
You downloaded the twrp-recovery-JBNV7AUS.zip from a few posts back. Extract the twrp-recovery.img file and put it in the stock folder. Now rename the twrp-recovery.img file to recovery.img.
Now boot the tablet to TWRP recovery(the one that isn't working) and run Nabilab. Select 4 Install recoveries. Then 4 instal stock recovery. Then reboot in to recovery and see if you have the 2.8.5 recovery
aicjofs said:
Find the Nabilab folder on your computer. Open the "recovery" folder. Then open the "stock" folder. Inside it there is recovery.img file. Rename it to recoverystock.img.
You downloaded the twrp-recovery-JBNV7AUS.zip from a few posts back. Extract the twrp-recovery.img file and put it in the stock folder. Now rename the twrp-recovery.img file to recovery.img.
Now boot the tablet to TWRP recovery(the one that isn't working) and run Nabilab. Select 4 Install recoveries. Then 4 instal stock recovery. Then reboot in to recovery and see if you have the 2.8.5 recovery
Click to expand...
Click to collapse
Great!
Your trick worked fine and now I can see TWRP 2.8.5.0 and I have problems with drivers - keeps failing to recognize the tablet.
I'll work on the driver issue or is there something I should know about it with TWRP 2.8.5.0 lodaed?
What is my next step from here as Android is still stuck on Nabi logo (no motion) and I'm afraid to do anything in case I create even bigger mess than I already have
I also noticed when I try to shut it down from inside TWRP it asks me a question if I want to root the tablet (Install super SU) - is it something I should do and at what stage?
Thanks!
T
termostat1000 said:
Great!
Your trick worked fine and now I can see TWRP 2.8.5.0 and I have problems with drivers - keeps failing to recognize the tablet.
I'll work on the driver issue or is there something I should know about it with TWRP 2.8.5.0 lodaed?
What is my next step from here as Android is still stuck on Nabi logo (no motion) and I'm afraid to do anything in case I create even bigger mess than I already have
I also noticed when I try to shut it down from inside TWRP it asks me a question if I want to root the tablet (Install super SU) - is it something I should do and at what stage?
Thanks!
T
Click to expand...
Click to collapse
If you can see the files again now with the correct TWRP. You can try to restore the 2.3.2 ROM again. Or maybe try the procedure from post #5 with the 2.2 ROM I linked to in post #7. You don't have to do the bootloader install anymore so skip that step. Installing root doesn't matter, you can choose to install or not.
aicjofs said:
If you can see the files again now with the correct TWRP. You can try to restore the 2.3.2 ROM again. Or maybe try the procedure from post #5 with the 2.2 ROM I linked to in post #7. You don't have to do the bootloader install anymore so skip that step. Installing root doesn't matter, you can choose to install or not.
Click to expand...
Click to collapse
You're a STAR!
All happy working as new with 232UK ROM and bootloader loaded with your instructions.
I'd never get this sorted without your specialized help.
If I only could I'd send you something just to say Thank You...
T - Happy Dad of Amelia
termostat1000 said:
You're a STAR!
All happy working as new with 232UK ROM and bootloader loaded with your instructions.
I'd never get this sorted without your specialized help.
If I only could I'd send you something just to say Thank You...
T - Happy Dad of Amelia
Click to expand...
Click to collapse
Your thanks is enough Glad we got it sorted and a happy kid!
Every time I try to install a custom rom, my device gets bricked. I'm stuck in a bootloop and TWRP tells me, that /data is unusable and /system can't be unmounted.
Right now I get I back to life, if I change the filesystem in TWRP for /data from f2fs to ext4 and back. After that /data is empty, but usable again. To get /system back to work, I erase it with "fastboot erase system". Then I reboot TWRP and reinstall STF-L09 8.0.0.360(C432) with zxz0O0s HuRUpdater. The logfile for the installation is attached with the title "Log during installation.zip".
After the installation I do a reboot and go through all the setup stuff of Android (WLAN, do you want to use..., etc.). Then everything seems to work fine. I can use the phone and reboot without a problem. But if I start TWRP, there are error messages about it can't unmount /system. I attached that logfile with the title "Log after Installation.zip". If I try to install an OTA update it gets bricked again.
No matter, how I try to install the custom rom, or how I reset my phone after it gets bricked, seems to make a difference. To me it seems like, either a problem with the file system, or a driver problem. But I'm not sure, because I'm more experienced with PCs. If I would have such a problem with a PC, I would erase everything and do a fresh start. But I don't know how to handle this here.
Please help me, to get out of this bricking cycle, before I can build a wall.
Status Update 1:
I went back to STF-L09C432B120 (Android 7) with this method: https://forum.xda-developers.com/showpost.php?p=75084955&postcount=17
All credits to gaguga:
Rollback from 8 android to 7
1. Place the firmware files of ?any? android 7 update.zip, update_data_public.zip and update_all_hw.zip in the HWOTA8 / repack folder. (I used STF-L09C432B120)
2. Run the bat file "repack" to repackage the zip files. This will prepare our firmware
I had a problem with this and had to update the file META-INF\com\google\android\update-binary by hand.
3. Create the folder "HWOTA8" on the SD card. (Without quotes)
4. Place the archive hwota8_update.zip, STF_RECOVERY8_NoCheck.IMG (from the HWOTA8 folder) and the three update archives (update.zip, update_data_public.zip and update_all_hw.zip (from the repack folder after repackaging)) to the "HWOTA8" folder on the sd card.
5. Boot into the TWRP
6. Install the hwota8_update.zip file which lies in the HWOTA8 folder on the sd card. The phone will reboot into the recovery mode and install the update automatically.
7. After the rollback, boot into recovery and make a reset
This was the first time, that I was able use the original recovery without problems.
I think I will try to do a rebrand at the weekend.