(First post - must go in General forum). Hello. I think I have discovered why some of us are having problems rooting the Hisense Sero 7 Pro tablet. I have downloaded the files (abbreviated) Root.part1.rar and Root.part2.rar from the sero7 website. When I use 7zip to verifiy file integrity, I get a data error on one of the files in one of the archives. Specifically, in Root.part2.rar, the file cwm_touch_recovery.img has an error. Root.part1.rar integrity is fine, however, Root.part1.rar contains a copy of cwm_touch_recovery.img which is correct. I went to the xda thread on this subject (posted by XBOXEXPERT - [DEV/CWM/ROOT/ROM] Hisense Sero 7 Pro CWM Touch Recovery, Factory ROM & My XE-SeroROM) and downloaded the part 1 and part 2 files. In part 1 tests ok, but part 2 gets a data error on file busybox. However, in this set of files, part 2 files are duplicated (except for the usb driver folder, which is empty) in part 1, so what is the need for part 2? Anyway, I was able to recover from the busybox and cwm_touch_recovery files (since they were duplicated). So, should I put all the files in one place to do the rooting?
I want to do this properly and correctly. As an aside, here is a question: in lieu of restoring the stock image, is there a way to remove the Developer Menu from the settings once it has been invoked? Thanks, Dennis.
Problems rooting Sero 7 Pro more info...
Hello. After doing some more experimentation, I've come to the conclusion that there is something wrong with the RAR files (other than having duplicate files and empty folders). I have downloaded (again) the part1 and part2 files from both the sero7 site and the xda site. I can do a file integrity test and it comes out clean. If I run it again, I get an error, always a problem with busybox (crc or data error) or cwm_touch_recovery.img (data error). I have downloaded the files and run the file integrity test on Windows (with 7zip) and Linux (the utility that compresses - it reads zip/rar etc. and can do an integrity test). Maybe you should be using ZIP or other compression program other than rar? How about 7zip? I have cobbled together all the files, including good versions of the busybox file and the cwm_touch_recovery.img file. Hope that's ok. I still don't understand how running a file integrity test can cause a file to go bad. But it seems to be doing just that, but only with busybox and cwm_touch_recovery.img. All for now. Thank you, D.
Sero 7 Pro Root
I have 2 Sero 7 Pro tablets and both are rooted without any issues. I download both rar files and extracted them into the same folder. I did get a message saying "file already exists do you want to overwrite?". I overwrote the file and both rar files extracted into one folder without any errors.
I'm running Windows 7 x64 and had a heck of a time getting Windows to recognize the tablet. I solved this by:
1. Creating a file named adb_usb.ini in C:\Users\Use Name\.android
2. Added this code to the adb_usb.ini: 0x109b
3. Then saved the file and and ran adb devices to verify adb saw the tablet. The table should show up now.
I then ran XESeroRoot.exe and followed the onscreen instructions in the pop up window.
After the program finished. I rebooted my tablet twice and it was good to go....rooted with stock rom.
From there I copied the custom I wanted to install onto my external sd card. I booted into cwm recovery, I wiped everything and then flashed the custom Rom from my external sd card.
Works great.
---------- Post added at 05:26 PM ---------- Previous post was at 05:18 PM ----------
Also.....I was having an issue with apps crashing to the home screen, such as Adobe Photoshop Touch, and Sims Freeplay on my wife's tablet.
I discovered there was a missing font causing the crash. Check your /system/font folder and make sure DroidSans.ttf and DroidSans-Bold.ttf exist. Once I added the fonts, the apps ran just fine without error.
If install a custom ROM and install the Table UI mod and you experience app crashes. Try re-flashing the Table UI.
My wife's tablet was doing weird things and apps were crashing...turned out to be a corrupt Table UI...I re-flashed and that fixed the issue.
I followed the directions here http://forum.xda-developers.com/showthread.php?p=41875797
Also have windows7 64bit and no issues rooting mine
Sent from my SPH-L720 using Tapatalk 2
I rooted with the same files, I used Xubuntu to extract and combine the 2 rar's back to one file then copied them to Windows to root with no problems.
Sent from my M470BSA using Tapatalk 2
Hisense Sero Pro 7 will not turn on
usegnu said:
I rooted with the same files, I used Xubuntu to extract and combine the 2 rar's back to one file then copied them to Windows to root with no problems.
Sent from my M470BSA using Tapatalk 2
Click to expand...
Click to collapse
My tablet will not power on. When I connect it to the charger the screen flashes a blue lightning bolt (see picture) with what appears to be a charging cable. I left it on the charger for 24 hours, still nothing. Does anyone know what this means and how to solve it. Customer service for Hisense was no help. Told me to ship it to me. I have to pay for shipping.
Black night have you tried a different charger or cable?
rooted my hisense
i rooted my hisense sero 7 pro last week an everything went fine. i intalled a diferent font from rom toolbox an when it rebooted it stayed on the startup screen ,
richard41 said:
i rooted my hisense sero 7 pro last week an everything went fine. i intalled a diferent font from rom toolbox an when it rebooted it stayed on the startup screen ,
Click to expand...
Click to collapse
If its still getting stuck at boot (bootloop), you might try going into CWM recovery and run "fix permissions". I haven't tried messing with the fonts, but permissions world be my first guess. Fonts need to be in the /system/fonts folder with the permissions of rw-r--r--.
I posted a link below with several methods to change fonts. There is also instructions on how to change the font via adb. So if you can get to recovery you can fix it from there without having to restore a backup.
http://www.android.gs/how-to-change-fonts-on-any-android-device/
Sent from my Nexus 7 using xda app-developers app
Just use vroot app. For zero 7 Lt or pro. It'll install super user and its in Chinese. Just re download super user from Google market and delete the Chinese one after rooting.
sent from my Sero 7 using XDA Premium Tablet app
exs.advocate said:
Just use vroot app. For zero 7 Lt or pro. It'll install super user and its in Chinese. Just re download super user from Google market and delete the Chinese one after rooting.
sent from my Sero 7 using XDA Premium Tablet app
Click to expand...
Click to collapse
there are some newer root scripts in the dev thread from delorespark
Hisense sero 7 pro stuck in bootloop
richard41 said:
i rooted my hisense sero 7 pro last week an everything went fine. i intalled a diferent font from rom toolbox an when it rebooted it stayed on the startup screen ,
Click to expand...
Click to collapse
Richard41, I am having the same problem. I root my Hisense Sero 7 Pro a week ago and it worked perfectly. Then a few days ago I downloaded an app from Google play to change the font on my device. It worked just fine but a day or two later, I went in the app to change the font again, but it immediately took me to Google play where I downloaded it and on the top of the screen it said, "This app is not compatible with your device."
I don't understand why it would say that when I already had it installed. So I left that screen and went back to the font app itself. I selected the font I wanted, it asked if I'm sure I want to change the font to the selected one, I confirmed it and then another pop up screen came up in Chinese or Japanese letters. It looked like it was asking the same question but in another language. I choice what I thought would be yes in English since it was in the was in the same place and then another pop up screen came but I don't know what it said because it was in the same Chinese or Japanese letters with a mixture of a few English letters, but still couldn't comprehend the message. So I figured I just needed to reboot it. I rebooted it, and it has been stuck on the "Hisense Smart" boot introductory screen ever since.
Danaroxy said:
Richard41, I am having the same problem. I root my Hisense Sero 7 Pro a week ago and it worked perfectly. Then a few days ago I downloaded an app from Google play to change the font on my device. It worked just fine but a day or two later, I went in the app to change the font again, but it immediately took me to Google play where I downloaded it and on the top of the screen it said, "This app is not compatible with your device."
I don't understand why it would say that when I already had it installed. So I left that screen and went back to the font app itself. I selected the font I wanted, it asked if I'm sure I want to change the font to the selected one, I confirmed it and then another pop up screen came up in Chinese or Japanese letters. It looked like it was asking the same question but in another language. I choice what I thought would be yes in English since it was in the was in the same place and then another pop up screen came but I don't know what it said because it was in the same Chinese or Japanese letters with a mixture of a few English letters, but still couldn't comprehend the message. So I figured I just needed to reboot it. I rebooted it, and it has been stuck on the "Hisense Smart" boot introductory screen ever since.
Click to expand...
Click to collapse
I also rebooted my Sero 7 and ever since I am stuck. I tried to install other ROMs also including the latest 4.4 by randomblame, however it is stuck... forever.
dogood1 said:
I also rebooted my Sero 7 and ever since I am stuck. I tried to install other ROMs also including the latest 4.4 by randomblame, however it is stuck... forever.
Click to expand...
Click to collapse
I found out that you're suppose to flash the original stock ROM (unroot it) and start over from there. I never tried it. I just went out and bought a new one.
Danaroxy said:
I found out that you're suppose to flash the original stock ROM (unroot it) and start over from there. I never tried it. I just went out and bought a new one.
Click to expand...
Click to collapse
I have tried installing stock ROM (from xboxexpert's thread), and it didn't work. Anyways, I am not going to buy a new one. Will try to fix it.
Trojan in XESeroRoot.exe
There's a Trojan (Trojanware.win32.renfro dot something) in XESeroRoot.exe. Execution halted by Comodo, removed the file and a registry entry. What's up with that??? The usb driver installed just fine, but there's no ADB debugging selection on my Hisense Sero 7 Pro (and yes, I have developer status).
Found the latest install, rooting and new ROM worked like a charm, thx, dolorespark!!
Related
Hi all.
I recently acquired a Trio M4302 4.3 inch Internet Tablet to try Android out, being a long time iOS user. My question is this. I'm looking for a way to a.) Get Google Play running on here, and b.) either flash a phone ROM or to turn on phone mode in ICS because the tablet interface is just too big for this little screen.. does anyone know of anything? Thanks in advance for the help!
Trio 4.3 root and Google Play Store
macfan406 said:
Hi all.
I recently acquired a Trio M4302 4.3 inch Internet Tablet to try Android out, being a long time iOS user. My question is this. I'm looking for a way to a.) Get Google Play running on here, and b.) either flash a phone ROM or to turn on phone mode in ICS because the tablet interface is just too big for this little screen.. does anyone know of anything? Thanks in advance for the help!
Click to expand...
Click to collapse
Hi,
I just picked this tablet up. I have successfully rooted it and have installed a working Play Store. I now have access to all my apps that I use on my Galaxy Note 10.1.
To root I used the instructions from this thread: http://forum.xda-developers.com/showthread.php?t=1886460
Once I had root I wanted to get Google Play Store on the tab. I found a couple of places that had information concerning adding Play Store to other devices and kind of pieced the info together to come up with this solution.
1. Download gapps for ICS. http://goo.im/gapps/gapps-ics-20120429-signed.zip
2. Unzip file
3. Navigate to the " System/app " folder and find "phonesky.apk and setupwizard.apk"
(You will need to copy these two files to your tablet)
4. Once files are on tablet use something like "Root Explorer" to copy both to the "system/app" folder of the tablet.
(The folders will need to be mounted as "R/W" so they can be written to )
5. After the files are copied to the proper folder, you need to edit the permissions for both.
6. In "Root Explorer" long press on each file and choose "permissions"
7. Edit permissions to read "Owner: Read, Write" "Group: Read" "Others: Read"
8. Reboot and launch Play Store
Hope it works for you!
Tabfreak
My Trio won't boot
It doesn't boot after enabling quickboot.
EDIT: Wait... I just flashed the Allwinner A10 ROM. I hope it works. Boot takes very very long and will not end in looping!
EDIT 2: It works... the touchscreen just didn't work and freezes when loading with SD Card.
NOW I DON'T HAVE A STOCK ROM FOR TRIO! I SPENT $60 FOR A BRICKED DEVICE!
Kotetsukun said:
It doesn't boot after enabling quickboot.
EDIT: Wait... I just flashed the Allwinner A10 ROM. I hope it works. Boot takes very very long and will not end in looping!
8:44 - Oh crap... Boot animation froze. WHAT DID I DO!?!?
8:45 - Bootloop confirmed.
NOW I DON'T HAVE A STOCK ROM FOR TRIO! I SPENT $60 FOR A BRICKED DEVICE! So I burned it.
Click to expand...
Click to collapse
Contact the manufacturer and maybe they can help. I just rooted and kept the stock rom. Sorry for your misfortune.
Sent from my GT-N8013 using Tapatalk HD
I'll try. I just flashed CM9 for AllWinnerTablets. I said I burned it just for expressing my emotion. I'll try to get a replacement or return it.
EDIT: I'll TRY to return it. But I'll see if I can replace it first, since it's on a one-year warranty. I have a reciept and kept it safe.
Don't know about Walmart, but you could try to return it
Sent from my GT-N8013 using Tapatalk 2
Here is a safer way
http://www.slatedroid.com/topic/658...49986__hl__stealth__fromsearch__1#entry749986
hi guys, i'm new in this forum, and i'm new to android too, i just bought a htc desire x and want it to be root, but i have problem when trying to get token id in hasoon2000 HTC Desire X All-In-One Toolkit V2.0 [1-1-2013], it says C:\ Document is not recognized as an internal or external command openable program or batch file.
usb debugging is already connected, please any one kindly fixing my problem, thx
sorry for my bad english. btw i'm from indonesia
Did you follow these steps?
How To Use. THIS IS FOR THE PC ONLY. No plans ever for Mac or Linux. Sorry.
1. Download the toolkit DO NOT RENAME THE FOLDER
2. Download Winrar from here. Install it after you download it
3. Extract the folder anywhere.
4. Run the program.
thx for replying so quick, after i downloaded then i extract to desktop and just run the program by clicking the symbol written as desire, am i doing it right?
Try to unpack it somewhere else on a root of some partition of your PC, try to unpack it to non system partition.
ok thx, i'll try it tomorrow, i'm sorry i've to go home coz it's 11.41pm already in my town, and i'm still on friend's house.
thx anyway for your reply, i'll let you know the progress
hi nlooooo, i did what u told me to do and it worked, i unpacked to (Cdrive, but another problem came on my device when i clicked get token id.
here is the picture shows the problem
@nlooooo.....i just tried your way on rooting this device, and same problem came up on step 8 when getting token id, still it says C:\ Document is not recognized as an internal or external command openable program or batch file, i've found out my device still locked, is it because of the device still lock? here's the image shown
problem solved
hi nlooooo......i've rooted my device, just try to put all the downloaded file to C:drive, and followed your tutorial on your thread, and i succeeded, at least i saw superuser on my device, thx alot for your tutorial.
No problem, that's why we're here. If you see it then it should be it. Try to install some app that requires root privileges (Titanium Backup for ex) and see if it can get SU rights.
hi.....any recommendation of apps or what to do after this rooting? cos i really a noob in android and root things. thx
uso_diario said:
hi.....any recommendation of apps or what to do after this rooting? cos i really a noob in android and root things. thx
Click to expand...
Click to collapse
Yeah install AdFree, and get rid of the ads
ayyu3m said:
Yeah install AdFree, and get rid of the ads
Click to expand...
Click to collapse
Well, it works for me with wifi but not with mobile data, it's configured over APN IP.
nlooooo.....sorry to bother you again, but i think my dx still not rooted, cos when i installed titanium backup root it comes like this, what do i hv to do?
ayyu3m said:
Yeah install AdFree, and get rid of the ads
Click to expand...
Click to collapse
heyyy........thank you
uso_diario said:
nlooooo.....sorry to bother you again, but i think my dx still not rooted, cos when i installed titanium backup root it comes like this, what do i hv to do?
Click to expand...
Click to collapse
Go and open Superuser app, swipe to first screen and see if the binary is installed. Then go and clear data for Titanium and open it again.
If you still have the problem use some root explorer to check folder system/bin if there is a file named su.
nlooooo said:
Go and open Superuser app, swipe to first screen and see if the binary is installed. Then go and clear data for Titanium and open it again.
If you still have the problem use some root explorer to check folder system/bin if there is a file named su.[/QUOTyes..there is binary installed, but it says outdated binary notification ticked
Click to expand...
Click to collapse
That's ok it should be like that. For me Titanium is working fine I have no problems.
nlooooo said:
That's ok it should be like that. For me Titanium is working fine I have no problems.
Click to expand...
Click to collapse
hi nlooooo........finally i got it fixed by start it all over again today........i'm new in this forum, don't know whether i can click your thanks button or not, but i will try it anyway, thx a lot
ps: i think it clicked
uso_diario said:
hi nlooooo, i did what u told me to do and it worked, i unpacked to (Cdrive, but another problem came on my device when i clicked get token id.
here is the picture shows the problem
Click to expand...
Click to collapse
I've got the same screen too, nothing is happening. What did you do to make it work?
i am getting stuck at last step i am always getting this message sending 'unlocktoken' (0kb) .
i have not installed htc sync app but just directly installed the drivers for unlocking purpose.
the boot loader is recognizing the usb connection as Fastboot usb.
using windows 7 32 bit operating system.
tried putting the unlock_code in c drive and desktop but it doesnt work.
the file is just a 1kb file.
the default view is shown as a vlc player file.
any help will much appreciated. this is my 1st htc mobile and am not used to this kind of rooting. previously owned a samsung so was using odin a lot.
I own a rooted Asus Transformer Prime TF201 table with JB 4.1.1 (original), and have probably done something stupid... please help this Noob, as I've read so much when looking for answers the last 2 days -- now I'm thoroughly confused! (To tell the truth, wasn't that great of a root user before...)
My tablet won't get beyond "Launcher has stopped" error when booting.
I rooted several months ago, installed a custom bootloader graphic (still works), SuperSU, ROM Manager and some other rooted apps. I had flashed cyanogen rom "9" (I think) -- the stable one for Asus -- and was running fine. I thought I had done a nandroid backup (file on SD card).
Then I created my problem: I had messed around with the LED settings via ROM Manager, and then I think I changed the build.prop file value for VM heap stack from 256 to 512 ("governor" settings?). (I know, I know -- used to mess around a little with PCs and I should have known better what I was doing!)
Now I can't get homescreens or launch apps, or anything. "Launcher has stopped"
I can power off and power on (using power + volume buttons). My custom bootloader image comes into view after the ASUS logo -- but next I get the "Asus Keyboard is not installed" message with the "Unfortunately, Launcher has stopped" message on top of that. Pressing the OK buttom just blinks and back to the errors.
I *can* get get to the settings, though.
Is a new tablet in my future?
Can anyone help me undo this mess I've made?? Help for the Noobs! Oh, and THANK YOU in advance for the trouble!
Hey!
Can you access the recovery mode? If yes:
1. Download the zip file attached to this post;
2. Put the holo.zip file in your sdcard;
3. Enter in recovery mode and flash the zip;
4. Reboot system;
5. Now you get Holo Launcher in your tablet!
Can't See Asus tablet from PC
Thanks for confirming that I am going about trying to fix this in the 'right' way!
I had never installed the SDK / android bridge to my Windows Vista 32-bit PC -- and I did that a couple days ago.
But I am not able to get root connected to the Asus. It shows as MTP device and I can see the sd card (also via Explorer in Windows)
I feel so dumb but I think the tablet can be rescued, if only I knew what to do!
Can you help me -- start from the beginning and help me get my Asus tablet working again??
Ellie92 said:
Thanks for confirming that I am going about trying to fix this in the 'right' way!
I had never installed the SDK / android bridge to my Windows Vista 32-bit PC -- and I did that a couple days ago.
But I am not able to get root connected to the Asus. It shows as MTP device and I can see the sd card (also via Explorer in Windows)
I feel so dumb but I think the tablet can be rescued, if only I knew what to do!
Can you help me -- start from the beginning and help me get my Asus tablet working again??
Click to expand...
Click to collapse
Sorry, I didn't see your post before.
Why don't you flash the ROM again?
I mean the custom one.
Sent from my mind using super powers.
Wifi and OTA updates were working fine before I rooted my kids' Nabi 2. I never tried an OTA update until after I rooted them, which doesn't work (I tried 2.1 since it said it was available). I followed the directions at http://forum.xda-developers.com/showthread.php?t=2041224 and it worked great to restore to stock 1.9.12, but wifi doesn't work now (mine could have been 1.9.37 originally). I tried the "wifi fix" mentioned, but there are still no wifi networks displayed like there were earlier today. I do not have a micro SD card to install the updates from, as mentioned in the replies. If I were to buy one, can I just put the OTA updates from http://forum.xda-developers.com/wiki/Fuhu_nabi_2 on it, and install from it somehow?
I tried to copy fuhu_nabi2_138139_1937_ota.zip to the device and install through the recovery kernel, but got an "assert failed" error. Any ideas as to what can be done to at least update this to 1.9.37, or maybe do a "stock install" of 1.9.37 instead of 1.9.12 so I have a better chance of wifi working? Please be specific as to what I need to try and in what order...some of the tools I tried seem to be inconsistent in results (Nabi Lab was latest I used). I am comfortable using what t499user has to go back to 1.9.12, I just wish I could use the same method to go to something newer...
I had the wifi problem this past spring. I backed up all my apps and data then flashed back to stock with NabiLab. Re-rooted and all was fine again.
You should also be able to use TWRP to flash back to stock. See TWRP thread http://forum.xda-developers.com/showthread.php?t=2074501
Some more info that may help http://forum.xda-developers.com/showthread.php?t=2248495
This experience is only my second time with TWRP and updating the Nabi. I've previously tried reverting to the backup in the "stockunrooted" folder, which is where I think the original was. I now recall that this had been updated to 2.0 using OTA before it was rooted.
Using TWRP, I tried reverting back to stockunrooted just now. Wifi works again, but OTA still does not (2.1 downloaded and seemed to install quicker, but upon reboot all I saw was "an error installing" message and it went directly to TWRP (where I just rebooted and it went to the Nabi screen). I am not sure what else to try. There is also an "oem" folder available for restore in TWRP, but that is the one created using t499user's process to go to 1.9.12. I initially used t499user's tutorial because I thought maybe something was wrong with the stockunrooted backup.
I have a few questions. Is updating TWRP to the latest version important? If yes, how do I do that (I've seen http://forum.xda-developers.com/showthread.php?t=2074501 before, but still not sure how to download/install 2.6.1.0)? If this has been reverted to "stock" and OTA updates still don't work, how do I apply them manually (from http://forum.xda-developers.com/wiki/Fuhu_nabi_2)?
I just noticed that the "stockunrooted" backup has things that aren't stock. Internal Storage has an Android folder with com.google.apps subfolders, etc. I am back to the original problem, and that is going to "stock" (something other than 1.9.12).
Cool, I figured out how to install 205to210.zip (TWRP 2.3.3.0)...For anyone interested, I copied the zip to Nabi/Internal Storage/TWRP, booted while holding +, pressed - to 'recovery kernel,' pressed + to choose it, then chose install. There is one more update I tried (2127stock.zip), but I get a flash error and it did not install. Considering (so far) I cannot get back to "stock unrooted" and use OTA updates, does anyone know how I can install this?
Wait...maybe there isn't another update. http://forum.xda-developers.com/wiki/Fuhu_nabi_2 has "Update 2.0.5 to 2.1.27" as the latest. I think it is working OK. Back to my original question(s), what is the process to install an updated version of TWRP and a "stock version" of something other than 1.9.12? Just trying to get the whole process understood...If I can simply use t499user's tutorial with different images, that would be rad to the max.
brentford said:
Wait...maybe there isn't another update. http://forum.xda-developers.com/wiki/Fuhu_nabi_2 has "Update 2.0.5 to 2.1.27" as the latest. I think it is working OK. Back to my original question(s), what is the process to install an updated version of TWRP and a "stock version" of something other than 1.9.12? Just trying to get the whole process understood...If I can simply use t499user's tutorial with different images, that would be rad to the max.
Click to expand...
Click to collapse
Yes its probably wise to update to TWRP 2.6.1.0. Get the file
Download
Follow "Method 3" here
http://forum.xda-developers.com/showthread.php?t=2074501&highlight=nabi
As for getting a stock image. You were using the zips here http://forum.xda-developers.com/wiki/Fuhu_nabi_2
You dont "Install" those zips. You need to extract the contents. boot.win, system.win, etc. and put them in the TWRP folder.(TWRP/BACKUPS/XXXXXX/folder)
Make a folder called 2127 put the filed in there. Then "Restore in TWRP. Then you should have a stock system. Same goes for 1937stock.zip 205stock.zip
If you have questions ask away.
Thank you all! I think I am getting it. Since I am reading (and had first hand experience) that Google Play isn't working very well with 2.1.27, I will go back to 2.05. That should keep the kids happy. I will let you know if I have more questions.
Oops...I broke something. I have two Nabis. I accidentally restored one using the device ID path of the other. I used "adb push c:\nabi\fuhu_nabi2_v1912_system.ext4.win /sdcard/TWRP/BACKUPS/015d2bc264340217/oem/system.ext4.win" for both. The incorrect one booted, but I noticed that the apps aren't the same. I tried to use TWRP again, but it is not recognized by cmd "adb devices" and I get "error: device not found" when trying "adb reboot-bootloader." I also tried whatever restore option there was in the settings, but it is the same result...Any options?
brentford said:
Oops...I broke something. I have two Nabis. I accidentally restored one using the device ID path of the other. I used "adb push c:\nabi\fuhu_nabi2_v1912_system.ext4.win /sdcard/TWRP/BACKUPS/015d2bc264340217/oem/system.ext4.win" for both. The incorrect one booted, but I noticed that the apps aren't the same. I tried to use TWRP again, but it is not recognized by cmd "adb devices" and I get "error: device not found" when trying "adb reboot-bootloader." I also tried whatever restore option there was in the settings, but it is the same result...Any options?
Click to expand...
Click to collapse
Google play won't work with 2.1.27 unless you delete some apps from /system/vendor/apps before installing gapps
As long as you have the bootloader(with the 4 options boot normal, fastboot, recovery kernel, forced recovery) and working USB port there are always options.
So is ADB not working in TWRP or in Android or both? It's probably best to copy boot.emmc.win, data.ext4.win and restore those too since you have done so much stuff. Boot contains you kernel, and data the apps. You will be back to a stock tablet with no game saves or anything so make sure you got off the tablet what you needed
I don't see a /system/vendor folder using TWRP file manager now...is that only when 2.1 is installed? How much do I need to remove, and are there any known problems with gapps in this case?
I fixed whatever problems I had. (Yes, I still have the bootloader.)
I am not that familiar with this, but let me explain what I have done. As before, I was using ADB/fastboot instructions from http://forum.xda-developers.com/showthread.php?t=2041224 (Windows 7). Both tablets' Internal Storage were recognized by Windows, but only the other one (with correct device ID 015d2bc264340217) was recognized when using ADB. That is how I was updating between Nabi 2 versions before.
Tablet 1:
C:\adb>adb devices
List of devices attached
015d2bc264340217 device
Tablet 2 (normally 015d24a7f41c1c15):
C:\adb>adb devices
List of devices attached
At one point, both devices started an endless loop when booting (shows the "Please wait while Nabi initializes" message for a split second and boots again). It may have been something with the way I installed the OTA updates, but I figured that it had to be something wrong with System so I wiped absolutely everything from within TWRP and I followed t499user's instructions for Windows cmd line (for going back to 1.9.12). Everything is good now, but I don't want to upgrade to 2.1 if gapps has any problems...
brentford said:
I don't see a /system/vendor folder using TWRP file manager now...is that only when 2.1 is installed? How much do I need to remove, and are there any known problems with gapps in this case?
I fixed whatever problems I had. (Yes, I still have the bootloader.)
I am not that familiar with this, but let me explain what I have done. As before, I was using ADB/fastboot instructions from http://forum.xda-developers.com/showthread.php?t=2041224 (Windows 7). Both tablets' Internal Storage were recognized by Windows, but only the other one (with correct device ID 015d2bc264340217) was recognized when using ADB. That is how I was updating between Nabi 2 versions before.
Tablet 1:
C:\adb>adb devices
List of devices attached
015d2bc264340217 device
Tablet 2 (normally 015d24a7f41c1c15):
C:\adb>adb devices
List of devices attached
At one point, both devices started an endless loop when booting (shows the "Please wait while Nabi initializes" message for a split second and boots again). It may have been something with the way I installed the OTA updates, but I figured that it had to be something wrong with System so I wiped absolutely everything from within TWRP and I followed t499user's instructions for Windows cmd line (for going back to 1.9.12). Everything is good now, but I don't want to upgrade to 2.1 if gapps has any problems...
Click to expand...
Click to collapse
Before browsing with TWRP file manager you need to go to the "Mount" tab, put an X in system. Then go to file manager.
Probably have to remove around ~50MB, maybe a bit less. Lots of people choose Wings, but obviously Wings is something some kids love. Really depends on the user.
When you flash stock, it often reset USB debugging to off in Android settings, if you flashed data too.
USB debugging is still on. Do you know anything about whether or not gapps has any problems with rooted Nabi 2.1? You have been a great help!
I didn't realize what would happen until it broke, but what I tried to do was remove apk files prior to upgrading to 2.1. I have copies of them on Internal Storage and locally, but I don't see a way to copy them back to /system/vendor/app using TWRP (tried mounting everything except external storage, which isn't selectable; internal storage isn't selectable, located to the right). Is there a way to do it, or do I have to go back to 1.9.12 and start over?
brentford said:
I didn't realize what would happen until it broke, but what I tried to do was remove apk files prior to upgrading to 2.1. I have copies of them on Internal Storage and locally, but I don't see a way to copy them back to /system/vendor/app using TWRP (tried mounting everything except external storage, which isn't selectable; internal storage isn't selectable, located to the right). Is there a way to do it, or do I have to go back to 1.9.12 and start over?
Click to expand...
Click to collapse
The only problem gapps has is there isn't enough room for it with a stock 2.1. You have to remove something.
Mount everything in TWRP. Go to file manager. /data/media is internal storage. You will find your files. Copy them back to /system/vendor/apps. Might have to set permissions.
Thanks! I copied from Windows using adb, but I got the same asset error (two of the files no longer had their original icon, it was default Android icon). That might have been the permissions issue you mentioned. In the future, how do I change the permissions, and what should they be set to? After this, I am done messing with it. Thank you for everything!
brentford said:
Thanks! I copied from Windows using adb, but I got the same asset error (two of the files no longer had their original icon, it was default Android icon). That might have been the permissions issue you mentioned. In the future, how do I change the permissions, and what should they be set to? After this, I am done messing with it. Thank you for everything!
Click to expand...
Click to collapse
You might be out of space again depending on what you copied back and why the icons are blank. Check with
adb shell df (in Android)
Look at system and see how much space you have free.
Or it could be permissions. You can use a file manager in Android such as ES File Explorer or Astro. You need to go to the setting in the app and enable whatever option they have to browse and remount "system" as read/write that will require root and should prompt you to accept. Then you can browse to the directory. You could also use TWRP File manager the same as when you copied files. There is a permissions tab.
I think the permission you want is 0644(for TWRP), or wr-r--r--(for ES). Same thing just different nomenclature.
Similar issue as OP
Hi guys, I have done pretty much the same thing as the OP. The wireless will not turn on or find any networks. I have tried reverse tethering, but have lost root and pretty much any other way to get internet to the nabi 2, so I can update from version 1.9.12. The big problem is I cannot use TWRP because when I boot into recovery and try to get there I get the dead green android guy with the exclamation point error and it hangs there until a hard restart. Any ideas on how to fix this. Is there a way to push an update through the SD card? Any ideas and suggestions would be greatly appreciated. I have already spent more time than I would have liked trying to fix this.
Dead android is stock recovery. You need to reflash TWRP.
Also to get out of the stock recovery just press vol + and - together. Should be am option to reboot. No need to hard power off.
aicjofs said:
Dead android is stock recovery. You need to reflash TWRP.
Also to get out of the stock recovery just press vol + and - together. Should be am option to reboot. No need to hard power off.
Click to expand...
Click to collapse
Well I swear I have tired this, but decided to give it another go and it worked! Got TWRP up and running then ran NabiLab to return to stock 1.9.37. Wireless is working and updating to 2.1 and then will give root a shot and GApps. Thanks for getting back on track!
I have had this problem on your ‘assist’ thread for two days now and had 101 views but no reply. I am trying here.
I am trying to put a more advanced rom from your site on to my Samsung 7.7 p6810.
Each time I try to install one I get a Status 7 error.
So far I have tried
lollipop_cm-12.1_20151006-unofficial-p6810.zip
omni-6.0.1_20160115-p6810-homemade.zip
Both have that error.
I started with cwm-20120710-p6810.tar
I thought that twrp might not produce the error so loaded:-
twrp-2.6.3.0-p6810.tar
I am using twrp and that still has the error.
I used Odin3_v3.10.6 to load the cwm and later the twrp.
I copied root.zip to the 7.7 and flashed that with the initially installed CWM
Can some kind soul suggest what I might be doing wrong? I see something about editing scrips in the zip files. I guess I could to that but (a) I am warned it is dangerous if the software is for the wrong machine and that is what I understand a Status 7 signal is saying.
And (b) it is going to be very tedious if I have to edit every new zip file as I experiment with your (nightly) upgrades.
Killing the Status 7 must be the way forward.
However, In desperation I have tried editing those first few lines of the updater script with Notepad ++ but I still get a Status 7 error.
Firstly I am getting no blue line on the TWRP progress bar - whereas I do on the Restore that I have to use rather more often than I would like.
My error message on a file that has those top lines removed from the script says:-
Applyparsedperms ; lstetfilecon of system/lost+found to ubject_r:system_file:s0 failed. Operation not supported on transport set metadata_recursive: some changed failed.
Then the Status 7 msg.
What should I try now, please?
Tony. London UK
I could not resist another try.
I flashed a newer version of TWRP. (Daniels 2.8.7.1) It worked fine as regards making a backup.
I then decided to install one of the errant roms and in the process wiped my whole machine. The right hand wipe button caused the damage. I was then left with a machine that would only produce TWRP.
However, having fiddle around so much over the last three days I guessed that if I used the recovery mode of TWRP it would be seen by my PC. I used Explorer to copy a root.zip, a lollipop zip and a marshmallow zip.
I used TWRP to install the root zip and it worked. I then took a flyer and put on the lollipop that had failed almost two dozen times before. Wowee, it installed.
I could see it was working so I have now put on the marshmallow. OK, I realise the marshmallow is not yet fully developed but I am only using this particular 7.7 to experiment with so that does not matter, yet.
Conclusion. I am not sure whether the newer TWRP is the solution or whether wiping the whole system cleared some rubbish.
Anyway. I am now there.
If anyone looks at this message I would value any comments - and also love to know how I configure a third party rom so it is recognised by google and the playstore. I want to re-install some of my apps and currently playstore does not know who I am.
Tony