Hello,
I'm completely new to the "Android Head Units" and would like to root my device. I've read different tutorials in this forum and I'm still not sure, if I will get through without trouble.
I would like to install root or a custom rom to my head unit, to install navigon which is not supported by the default rom, which is installed and I want to remap the hardware buttons. Could u guys give me tipps and links to download?
becaue of the fact, that I'm a new user and can not post any links, I am going to describe the device:
Android 4.4.4
Screen: 800x480
chip: rk 3066
unit: kld
muiem said:
Hello,
I'm completely new to the "Android Head Units" and would like to root my device. I've read different tutorials in this forum and I'm still not sure, if I will get through without trouble.
I would like to install root or a custom rom to my head unit, to install navigon which is not supported by the default rom, which is installed and I want to remap the hardware buttons. Could u guys give me tipps and links to download?
becaue of the fact, that I'm a new user and can not post any links, I am going to describe the device:
Android 4.4.4
Screen: 800x480
chip: rk 3066
unit: kld
Click to expand...
Click to collapse
I've got this unit, installed and tried a couple of ROMs (image updates) on it until I found the one I liked. Just go back to the original post, down load an image update file you like, get the v2.64 MCU-img file as well (follow the links) put them both in the root of the GPS card boot into recovert (hold down reset and power, release reset then power) flash the image/MCU files (second option down).
Reboot and enjoy your rooted unit.
Cheers
rom files
Hello
I have exactly the same unit and would like to root, but I am unable to find a link to the files.
Can someone please help?
Regards
Meirion
I have pumpkin 4.4 radio. I went to factory settings and entered password *#hct#root# that did something with adb. Can anybody tell me what rooting app they used to root?
Thanks
vipersinu2 said:
I have pumpkin 4.4 radio. I went to factory settings and entered password *#hct#root# that did something with adb. Can anybody tell me what rooting app they used to root?
Thanks
Click to expand...
Click to collapse
You don't need an app. By entering that specific password you're rooted. You should also complete the whole thing by writing adbon
in the same field. If you go to settings you will find #superuser which was not there before rooting.
---------- Post added at 04:02 PM ---------- Previous post was at 03:59 PM ----------
saintadam said:
I've got this unit, installed and tried a couple of ROMs (image updates) on it until I found the one I liked. Just go back to the original post, down load an image update file you like, get the v2.64 MCU-img file as well (follow the links) put them both in the root of the GPS card boot into recovert (hold down reset and power, release reset then power) flash the image/MCU files (second option down).
Reboot and enjoy your rooted unit.
Cheers
Click to expand...
Click to collapse
Honestly, you don't need to put any rom in there, just write the specific command for rooting in the same field as the password for entering factory settings *#hct#root#. This is all described wiki. http://forum.xda-developers.com/wiki/Hui_Fei_Type
abdon not working
Just to make sure I am doing this correctly.
I went to play store and downloaded superuser.
I went to factory settings and put in *#hct#root# then I pressed OK I got a message ADB ROOT. I went back to factory settings and put in abdon and got wrong password. Does *#hct#root# and abdon have to be entered at the same time like *#hct#root#abdon ? I know there is no root terminal emulator will not take su command and root checker say no root. Any advice?
vipersinu2 said:
Just to make sure I am doing this correctly.
I went to play store and downloaded superuser.
I went to factory settings and put in *#hct#root# then I pressed OK I got a message ADB ROOT. I went back to factory settings and put in abdon and got wrong password. Does *#hct#root# and abdon have to be entered at the same time like *#hct#root#abdon ? I know there is no root terminal emulator will not take su command and root checker say no root. Any advice?
Click to expand...
Click to collapse
You don't have to download anything. Just make the command *#hct#root#. When you get adbroot, your rooted. That's it. You're making it too complicated.
If adbon doesn't work for you no harm done. Try it another time. Why download superuser? It's there in settings without any downloading.
halloj said:
You don't have to download anything. Just make the command *#hct#root#. When you get adbroot, your rooted. That's it. You're making it too complicated.
If adbon doesn't work for you no harm done. Try it another time. Why download superuser? It's there in settings without any downloading.
Click to expand...
Click to collapse
I forgot to add that in my last post, superuser is not showing up in settings
vipersinu2 said:
I forgot to add that in my last post, superuser is not showing up in settings
Click to expand...
Click to collapse
Maybe because you've been fiddling around by downloading and installing. Uninstall what you have been installing
and try again and look out for adbroot. #superuser will appear one row under factory settings. Of course you have to reboot the unit.
[URL="http://i1202.photobucket.com/albums/bb373/vipersinu2/Mobile%20Uploads/20160326_140113.jpg"]http://i1202.photobucket.com/albums/bb373/vipersinu2/Mobile%20Uploads/20160326_140045.jpg[/URL]
no superuser, is your radio 6.95"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/URL][/IMG]
[/URL][/IMG]
No superuser this is 4.4 kitkat
---------- Post added at 06:15 PM ---------- Previous post was at 06:08 PM ----------
vipersinu2 said:
[/URL][/IMG]
[/URL][/IMG]
No superuser this is 4.4 kitkat
Click to expand...
Click to collapse
Do you have developer options. I pressed build 7 times nothing happens
Update. I factory reset head unit . *#hct#root# Still no superuser. I also updated MCU to 2.78. Still no superuser. And I lost radio reception b/c of upgrade. I downgraded MCU to 2.54 that restored radio.
So I went and download a rooted custom rom and installed by sdcard. Head unit took *#hct#root# password and is now showing superuser. And is rooted.
just in case anyone is wondering, just download "kingo root" on your pumpkin head unit, click the one click root button and that's it! it takes about 2-3 full minutes so be patient! it will stick at 90% for awhile, then full root access.
Related
My wife got me a brand new A500 off ebay a couple of months ago for a Christmas gift(for me it's only three days old). So far I love it but it will not take the OTA update that it keeps bugging me about. The download starts fine but then stalls out mid download. I looked here http://forum.xda-developers.com/showthread.php?t=1113878 but did not see my current version there. Can anyone point me in the direction of the OTA I need to download and flash with recovery? My build is Acer_a500_1.145.09_com_gen1 I'm running 3.0.1. It looks like it's trying to download 4.010.11.
Further info:
According to the log the file name is Acer_A500_1.145.09_4.010.11_com_gen1_1311243587838_bd1ab95c.zip
I can't find that file anywhere on the net.
The reason I would suspect is because someone replaced the stock recovery? Off eBay you say, was it brand new and never used? It sounds like it was used or someone tampered with it?
If that's not the case, then you can just install the update manually. Download the update you want and put it on your external SDCard and then enter recovery (using power and volume). The recovery will install the update for you.
timmyDean said:
The reason I would suspect is because someone replaced the stock recovery? Off eBay you say, was it brand new and never used? It sounds like it was used or someone tampered with it?
Click to expand...
Click to collapse
It said it was brand new. My wife would not buy something like this used. The weird thing is it knows it has an update and it starts to download and get's up to half way downloaded and then it just stops. It shows that it still is pulling data but the downloaded file size doesn't increase anymore after it stalls.
Ive been looking into rooting it and since I'm on 3.0.1 it appears Gingerbreak is all I need. The next question is what rom should I get and how do I go about installing it? I've never rooted droid before and most instructions on XDA are written for the experienced level and not the new guy. I'd like to stay fairly stock but rooted.
Sent from my A500 using Tapatalk
There are reports of others having the same issue. They say that a soft reset often fixes it.
You can use my tool to flash in 3.2.1 which is rooted. http://forum.xda-developers.com/showthread.php?t=1307539&page=14
timmyDean said:
There are reports of others having the same issue. They say that a soft reset often fixes it.
You can use my tool to flash in 3.2.1 which is rooted. http://forum.xda-developers.com/showthread.php?t=1307539&page=14
Click to expand...
Click to collapse
Just to make sure I'm getting it right: I go here http://forum.xda-developers.com/showthread.php?p=20680452 download that to my PC and follow the instructions contained within and I end up with a stock rooted 3.2.1? I don't need to download anything else right? A soft reset for this tab is pusing the little red button on the end by the USB port?
Sent from my A500 using Tapatalk
Yes, if you want to flash 3.2.1 stock with root read the instructions in the download. The download has everything in it.
The soft reset everyone talks about is using the paperclip in that little hole next to the USB port.
timmyDean said:
Yes, if you want to flash 3.2.1 stock with root read the instructions in the download. The download has everything in it.
The soft reset everyone talks about is using the paperclip in that little hole next to the USB port.
Click to expand...
Click to collapse
Sweet. You're a life saver. Thanks for translating it all to noob for me. Will I need to reinstall all of my apps and such afterwards?
Sent from my A500 using Tapatalk
Yes, the flashing tool makes it just like new, out of the box, but with root.
timmyDean said:
Yes, the flashing tool makes it just like new, out of the box, but with root.
Click to expand...
Click to collapse
OK that's not a big deal. The SD card will remain intact though right?
Sent from my A500 using Tapatalk
Jds method does work. But you can also trybthis.
http://forum.xda-developers.com/showthread.php?t=1410802
Simple easy no computer needed
timmyDean said:
Yes, the flashing tool makes it just like new, out of the box, but with root.
Click to expand...
Click to collapse
I tried your method and I get stuck at the serial number part. It says ADB server out of date. What do I do?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit: Never mind. I got my steps out of order. I was clicking next before running test.cmd
Last edit: It appears to have worked. I'm back to the initial setup screens just like when I first got it.
Hello,
A customer gave a Grand 2 (SM-G7106) for service, to have a custom rom & recovery installed.
I've been trying to use the method that's available in all the forums (put the phone to download mode, connect it to odin & etc...).
But the phone does not go into download mode in the first place for some reason.
Rather, when I keep holding Vol Down + Home + Power (or Vol Down + Power only) , a screen flashes to say 'Factory mode' for like 2 secs & then, I get these options
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, I tried, Vol Up + Power & I get these options
Please give me a solution to this.
Thanking you all in advance,
bro...
which andriod version he izz using??
haneef95 said:
Hello,
A customer gave a Grand 2 (SM-G7106) for service, to have a custom rom & recovery installed.
I've been trying to use the method that's available in all the forums (put the phone to download mode, connect it to odin & etc...).
But the phone does not go into download mode in the first place for some reason.
Rather, when I keep holding Vol Down + Home + Power (or Vol Down + Power only) , a screen flashes to say 'Factory mode' for like 2 secs & then, I get these options
So, I tried, Vol Up + Power & I get these options
Please give me a solution to this.
Thanking you all in advance,
Click to expand...
Click to collapse
I think its not the original set it must high copy so its not going to the download mode .
Andriod version
PKothavale said:
which andriod version he izz using??
Click to expand...
Click to collapse
4.4.X, can't remember what that X was!
kemesh said:
I think its not the original set it must high copy so its not going to the download mode .
Click to expand...
Click to collapse
Not sure, it only came for service.
How do I distinguish between original & duplicate?
Even then, is there any solution to this problem though?
haneef95 said:
Not sure, it only came for service.
How do I distinguish between original & duplicate?
Even then, is there any solution to this problem though?
Click to expand...
Click to collapse
If its an 4.4.X version then u can use balliboxer's new kikat superior rom u can directly insatll it from recovery mode/install a zip...but bro if it doesnt has base of version 4.4.x be aware device can be bricked...
---------- Post added at 11:56 AM ---------- Previous post was at 11:39 AM ----------
PKothavale said:
If its an 4.4.X version then u can use balliboxer's new kikat superior rom u can directly insatll it from recovery mode/install a zip...but bro if it doesnt has base of version 4.4.x be aware device can be bricked...
Click to expand...
Click to collapse
And Be aware if it gets any error dont downgrade it again to 4.3 aware !!! it will make ur device hard brick...
Hey buddies,
I got a 4.3 Samsung SM-G7106, with G7106ZNUANK1 from China Unicom (CHU). unfortunately, I can't root it properly. Tried CF-Root, TowelRoot and Framaroot but no luck.
I hope you can help me out guys, thanks!
May be it is super copy for grand 2,,try to chek with cpu identifier or cpu z,,
Sent from my SM-G7102
Nah, its not a supercopy, just found out that one of my friend was also using the same phone, same specs, same everything and he bought it on Samsung Store in China (He presented me with the copy of the receipt and box stuffs), so yeah, I think its a legit one since its running well on Kies also (unlike other copy phones which can't be detected thru Kies). Anyway, I found a root program from G7106ZNUANC1 and I forgot the other one, its thru SRS root, but didnt work for my phone unfortunately. :crying:
Hope someone could help me root my G7106ZNUANK1 soon!
chopsuey8 said:
Nah, its not a supercopy, just found out that one of my friend was also using the same phone, same specs, same everything and he bought it on Samsung Store in China (He presented me with the copy of the receipt and box stuffs), so yeah, I think its a legit one since its running well on Kies also (unlike other copy phones which can't be detected thru Kies). Anyway, I found a root program from G7106ZNUANC1 and I forgot the other one, its thru SRS root, but didnt work for my phone unfortunately. :crying:
Hope someone could help me root my G7106ZNUANK1 soon!
Click to expand...
Click to collapse
Flash CWM or TWRP through odin..den flash su binaru 2.45 from recovery. su binary 2.45 available in chainfire site.Gud Luck
prakash87 said:
Flash CWM or TWRP through odin..den flash su binaru 2.45 from recovery. su binary 2.45 available in chainfire site.Gud Luck
Click to expand...
Click to collapse
Thanks for the tutorial buddy! Is it possible you can walk me thru it? Even though I'm kinda lurking here for quite some time, still some things are alien to me. I hate to say this, but, can you spoon-feed me the instructions in doing so? Would really appreciate your help!
Thanks! :good:
Hi.
I just got also a Grand 2 G7106, and does the same thing - chinese menus instead of recovery mode. Found a video on youtube that explained which single item does, and most are only a bunch of tests, and one for factory reset, but still with this same issue.
I also would like to know how to use odin without entering in download mode.
sacp said:
Hi.
I just got also a Grand 2 G7106, and does the same thing - chinese menus instead of recovery mode. Found a video on youtube that explained which single item does, and most are only a bunch of tests, and one for factory reset, but still with this same issue.
I also would like to know how to use odin without entering in download mode.
Click to expand...
Click to collapse
Hey buddy, try using SRS root software if you wanted to root your phone. If you're lucky enough that its not the G7106znuank1 model, then it can be rooted thru it. Otherwise, you'll be stuck like me. lol.. good luck! :good:
looks like i am stuck with you guys too. Have the same Samsung SM-G7106 . I tried using ODIN to install CWM. Despite Odin saying that it is PASS and device rebooted itself, when i try to go into recovery mode (CWM) it goes into default Android recovery mode instead with (write protected) ... i tried TWRP too using ODIN and it is not working. Tried both Odin 3.09 and 3.10
If you're still looking for a way to root your SM-G7106, I managed to do it with the KingoRoot app.
super simple process. It's based on Chainfire.
I should mention this was with: G7106znuank1
I have a grand 2 g7106 hard bricked and it is totally dead how to solve this problem please help.
Thanks in advance
So, I had a rooted, ROMd, OC/UVd, crazy 4.4 setup on my N4 for the longest time, then I put 5.0 on.
This was all cool and fine and all that but I lost root in the process as is common.
I procrastinated re-rooting as I knew I would be upgrading soon and I didn't feel like wiping.
Then I dropped it.
For the 100th time.
It broke, finally.
The top half of the screen no longer responds to touch making it impossible to unlock now.
What I need are some options. I tried ADB stuff and can get nowhere without su. I tried "AndroidScreenCast" but for it to work I also need su to change some file permissions. SOL again.
Basically I'm left with the phone and ADB debugging...that's it. What can I do?
End goal: re-purpose the phone as something that doesn't require a screen anymore...
http://www.howtogeek.com/139373/how-to-turn-an-old-android-phone-into-a-networked-security-camera/
All I have to do is get the apps on there and get it up and running.
Any help appreciated. Thanks!!
62 views and not a single reply...
I'm starting to think I'm hosed.
I don't care about saving anything on the phone. I just don't want to lose the hardware...there's got to be SOMETHING I can do...
rmp5s said:
62 views and not a single reply...
I'm starting to think I'm hosed.
I don't care about saving anything on the phone. I just don't want to lose the hardware...there's got to be SOMETHING I can do...
Click to expand...
Click to collapse
First, Download UPDATE-SuperSU-v2.46.zip
and place it in sdk\platform-tools (or the same directory as your adb and fastboot)
Boot into fastboot by turning off phone, then hold volume up button while pressing power button.
or
From within your platform-tools folder, open a command prompt.
If the phone running in android, run the following command
adb reboot fastboot
Then run
fastboot flash UPDATE-SuperSU-v2.46.zip
In android, you can then install your apps by placing the .apk in your "sdk\platform-tools" too
and run the following command replacing "my.apk" with the actual name of your .apk
adb install my.apk
The biggest problem you face now is how to allow superSU permission for the individual app.
If you get lucky, the permission dialog will appear in the half of your touchscreen that works:good:
Best of luck
---------- Post added at 04:18 AM ---------- Previous post was at 04:00 AM ----------
Or if androidscreencast is working for you, just enable the SU app permissions with androidscreencast!
joegestes said:
First, Download UPDATE-SuperSU-v2.46.zip
and place it in sdk\platform-tools (or the same directory as your adb and fastboot)
Boot into fastboot by turning off phone, then hold volume up button while pressing power button.
or
From within your platform-tools folder, open a command prompt.
If the phone running in android, run the following command
adb reboot fastboot
Then run
fastboot flash UPDATE-SuperSU-v2.46.zip
In android, you can then install your apps by placing the .apk in your "sdk\platform-tools" too
and run the following command replacing "my.apk" with the actual name of your .apk
adb install my.apk
The biggest problem you face now is how to allow superSU permission for the individual app.
If you get lucky, the permission dialog will appear in the half of your touchscreen that works:good:
Best of luck
---------- Post added at 04:18 AM ---------- Previous post was at 04:00 AM ----------
Or if androidscreencast is working for you, just enable the SU app permissions with androidscreencast!
Click to expand...
Click to collapse
Thanks for the reply! I'll try it when I get home tonight.
The "update" zip will root it?
rmp5s said:
Thanks for the reply! I'll try it when I get home tonight.
The "update" zip will root it?
Click to expand...
Click to collapse
Actually NO. I got this totally wrong
You can not root using fastboot commands with UPDATE-SuperSU-v2.46.zip
Reason being, you need something that can mount the /system partition as writable.
So I apologize and please disregard my previous post.
You need to "abd sideload UPDATE-SuperSU-v2.46.zip" .
But in order to do that you need to be in adb sideload mode in your custom recovery.
Honestly, since you have issues with the busted touchscreen, it might be imposible to get to the proper place in your recovery.
I think the best option to get rooted again is
Wug's Nexus Root Toolkit
Its free, simple and works well. It will allow you to root without using the touchscreen provided you already have adb debug enabled.
Just download the toolkit from the link above and install on your PC, select your phone model and let it download the needed dependency's.
Then simple click on "root" in the main screen of the program and follow the prompts.
Simple as that.
Looks like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Apologies again for my misleading first post brain fart, but Wugs should work well in your situation.
joegestes said:
Actually NO. I got this totally wrong
You can not root using fastboot commands with UPDATE-SuperSU-v2.46.zip
Reason being, you need something that can mount the /system partition as writable.
So I apologize and please disregard my previous post.
You need to "abd sideload UPDATE-SuperSU-v2.46.zip" .
But in order to do that you need to be in adb sideload mode in your custom recovery.
Honestly, since you have issues with the busted touchscreen, it might be imposible to get to the proper place in your recovery.
I think the best option to get rooted again is
Wug's Nexus Root Toolkit
Its free, simple and works well. It will allow you to root without using the touchscreen provided you already have adb debug enabled.
Just download the toolkit from the link above and install on your PC, select your phone model and let it download the needed dependency's.
Then simple click on "root" in the main screen of the program and follow the prompts.
Simple as that.
Looks like this
Apologies again for my misleading first post brain fart, but Wugs should work well in your situation.
Click to expand...
Click to collapse
I actually have that already AND DO have USB debugging turned on so that should work. I completely forgot about that thing. It'll wipe the phone but I really don't care...after it's rooted again, I'll be good to go.
Thanks!!
Yup...having a big problem hitting "Install" in TWRP. Big problem == can't. lol
I've tried various ADB screen press commands and keep getting weird "/sbin/sh: input: not found" errors. Not sure what that's all about. Still working on it.
AndroidScreenCast still won't work, probably because it's still not rooted.
All I need to do is install the "UPDATE-SU..." zip and the BusyBox zip. That's it. Then I'll be golden. So close yet so far away. lol
Appreciate all the help.
Back to trying stuff!
rmp5s said:
I actually have that already AND DO have USB debugging turned on so that should work. I completely forgot about that thing. It'll wipe the phone but I really don't care...after it's rooted again, I'll be good to go.
Thanks!!
Click to expand...
Click to collapse
If your bootloader is already unlocked and you use the "ROOT" option in Wugs it will simply root the device.
It will not wipe your phone.:good:
---------- Post added at 09:19 AM ---------- Previous post was at 09:08 AM ----------
I could be mistaken, but It should root without any user input in twrp.
Just be sure to uncheck
"And also flash
Custom recovery
It will boot to a non permanent temporary TWRP recovery Without flashing TWRP
---------- Post added at 09:37 AM ---------- Previous post was at 09:19 AM ----------
Ok, just to confirm this, I rooted my girlfriends unlocked nexus 4 that has a stock recovery in wugs using the root button .
Absolutely no user input at all was required.
Her user Data is still intact.
Phone is rooted.
https://forums.geforce.com/default/...android-5-1-lollipop-ndash-available-7-23-15/
Finally the OTA has been released
Anyone use the 5.1 xposed on this yet? Waiting to see if it works before I update.
Sent from my bacon
Is the update even out yet? It's not showing up when I click check for updates..
zach jeremay said:
Is the update even out yet? It's not showing up when I click check for updates..
Click to expand...
Click to collapse
Yeah, I downloaded it and tried to install it. I forgot I had installed a custom recovery, so it failed. I reinstalled the factory recovery and now I'm waiting for the update again.
Does anyone have the img file for lollipop? I don't know why my updates not showing up.
Ok, seems the old CWM from KitKat is working. Also SU 2.46 does.
Sadly no Miracast anymore.
A few games apart from the mentioned ones in the link above won't work too: ARC Redux (more to come)
Did anyone catch the OTA. I have the factory Image for 103 but wont flash due to the "insufficient memory" for the system.img and the userdata.img I had similar problems with the tablet and only updated via the OTA. My system isn't showing as an update available.
diigibio said:
Did anyone catch the OTA. I have the factory Image for 103 but wont flash due to the "insufficient memory" for the system.img and the userdata.img I had similar problems with the tablet and only updated via the OTA. My system isn't showing as an update available.
Click to expand...
Click to collapse
You can try flashing the factory Image from update 103.
It's available now too...
https://developer.nvidia.com/gameworksdownload
Just make an account (it's free) and set the filter to "SHIELD".
Here you go.
astuermer said:
You can try flashing the factory Image from update 103.
It's available now too...
https://developer.nvidia.com/gameworksdownload
Just make an account (it's free) and set the filter to "SHIELD".
Here you go.
Click to expand...
Click to collapse
Thanks but already tried.
Sent from my A0001 using Tapatalk
Hi !
It seems my CWM is nit "compatible" with OTA 103, i get all sort of errors in CWM when trying to execute OTA update.
Do you have any hint where to download a compatiple CWM or stock recovery ?
(Or any smarter solution for that problem of course).
Greetings,
Ender
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can anybody confirm this issues?
1. Volume way too loud
2. Volume often varies, step 1 isn't always the same level.
3. Shield Hub can't be activated with button
Couldn't install with TWRP. Got some weird error after flashing and it wouldn't boot up at all. Had to go back and restore a backup.
Sent from my bacon
Hmm, i "solved" my Problem by flashing 5.1 with Linux instead of OTA...
Greetings,
Ender
Problems I can confirm are, cant install or update anything from the play store because of "insufficient space" when I clearly have 2GBs and a 64GB micro SD card, its alot slower and Apex Launcher is now utterly terrible with the new update.
After trying to install it won't boot up. Then I tried to fastboot but I'm getting an error saying target reported max download size of 643825664 bytes error: cannot load 'recovery.img' : No error .
Any ideas
I disabled "Google" so the Shield button does not activate it but still the Game Mapper is not showing up. Thats horrible, dis anyone manage to get back the Game Mapper ?
Ender
enderffx said:
I disabled "Google" so the Shield button does not activate it but still the Game Mapper is not showing up. Thats horrible, does anyone manage to get back the Game Mapper ?
Ender
Click to expand...
Click to collapse
To enable it open the app / game then hold down the start button until it pops up, If it didn't work then read down...
for me it's working perfectly i think because i flashed it using a computer (or maybe a factory reset should do the trick) if you're going to do it make sure you do a backup in the external sdcard because everything in the internal sdcard will be deleted I'm not responsible for any lost file or any damage, I'm not trying to scare you but I will help you if I can
By the way I disabled "google" and still the gamepad mapper is working fine so "google" has nothing to do with.
How did you guys use a computer to flash it? Sis they release the img? I would like to flash it with my computer because I still haven't received the ota.
---------- Post added at 12:14 AM ---------- Previous post was at 12:10 AM ----------
Did they release the img? How did u flash it with a computer, please help me because I didn't receive the ota and ima fan of lollipop.
All of these have been brought up on the Nvidia forums, so yes, they can be confirmed. I would like to add, that the volume changes dynamically depending on the sound being played In some games and emulators, I noticed that the sound would get quieter and louder without touching anything. I had Virtua Racing for 32x running in Retroarch and the volume dropped and raised in the same places during the demo mode every time, like it was done on purpose.
Is it just me, or does it seem like Nvidia is trying to de-Nvidia the Portable?
astuermer said:
Can anybody confirm this issues?
1. Volume way too loud
2. Volume often varies, step 1 isn't always the same level.
3. Shield Hub can't be activated with button
Click to expand...
Click to collapse
Tested on PLK-L01 from Germany.
Download the following file:
http://rootjunkysdl.com/getdownload.php?file=Huawei%20P8%20Lite/Huawei%20Product%20ID%20Generator.exe
Insert you IMEI1 and choose "HUAWEI Y300-0000" as model.
Copy the product ID.
On the following picture it is in german, but on the page it is described in english which information you have to enter.
Enter the information on following page: http://emui.huawei.com/en/plugin.php?id=unlock&mod=detail
You have to login via Facebook to get the code and it only works with facebook.
Every Facebook account can unlock two devices every six months.
You will get the unlock code marked red.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Did you tried also to flash something? (Root or xposed)
Piemo said:
Did you tried also to flash something? (Root or xposed)
Click to expand...
Click to collapse
Not until now, but if you have something reliable to flash for rooting I will try it.
There was the guide for rooting the Honor 7, but I don't know if it is only for the chinese version?
Aurevo said:
Not until now, but if you have something reliable to flash for rooting I will try it.
There was the guide for rooting the Honor 7, but I don't know if it is only for the chinese version?
Click to expand...
Click to collapse
Actually I've seen only that one, dunno if it would work. I'm like that my order is "waiting for stock" so other can try for me. XD
Worked for me
Piemo said:
Did you tried also to flash something? (Root or xposed)
Click to expand...
Click to collapse
This method worked for me, so thanks to OP.
As fastboot oem get-bootinfo shows the Bootloader as unlocked.
I flashed a Chinese TWRP from the guide I found elsewhere here. It definitely boots into TWRP and everything works inside TWRP, albeit in Chinese.
Unfortunately, I'm now in a TWRP bootloop and can't get out of it.
I don't have a stock ROM/recovery to re-flash, so I'm hosed until one appears online.
Model PLK-L01
philipcraig said:
This method worked for me, so thanks to OP.
As fastboot oem get-bootinfo shows the Bootloader as unlocked.
I flashed a Chinese TWRP from the guide I found elsewhere here. It definitely boots into TWRP and everything works inside TWRP, albeit in Chinese.
Unfortunately, I'm now in a TWRP bootloop and can't get out of it.
I don't have a stock ROM/recovery to re-flash, so I'm hosed until one appears online.
Model PLK-L01
Click to expand...
Click to collapse
Try the tutorial on gizdev!
haasgo said:
Try the tutorial on gizdev!
Click to expand...
Click to collapse
Is it useful to try it without an recovery image available? Some other user tried it and is in a bootloop now without the possibility to recover.
I also slashed beta-supersu, using the Chinese twrp. I didn't reboot in between flashing twrp and supersu. Maybe I should have.
Thanks!
Works perfect for me
What to do with the unlock code? I mean where to enter it?
Using your tip, I made this http://androidmtk.com/unlock-bootloader-of-huawei-honor-7
rahul964 said:
Using your tip, I made this http://androidxda.com/unlock-bootloader-of-huawei-honor-7
Click to expand...
Click to collapse
I get stuck on the step 10: after I fill everything out, it says "Sorry, you must use a phone account to submit this application."
I had this too. I needed to log in at the first step with a Facebook account. Basically Huawei want a record of who they've given codes to.
philipcraig said:
I had this too. I needed to log in at the first step with a Facebook account. Basically Huawei want a record of who they've given codes to.
Click to expand...
Click to collapse
Yes, it worked.
Did you figure out how to get out of the bootloop? Did you successfully root it?
pappapishu said:
Yes, it worked.
Did you figure out how to get out of the bootloop? Did you successfully root it?
Click to expand...
Click to collapse
Yes, and yes.
philipcraig said:
Yes, and yes.
Click to expand...
Click to collapse
Okay, but the "bootloop part" is necessary, isn't? Did you fix it thanks to duky_duke's post?
http://forum.xda-developers.com/showpost.php?p=62737969&postcount=17
pappapishu said:
Okay, but the "bootloop part" is necessary, isn't? Did you fix it thanks to duky_duke's post?
http://forum.xda-developers.com/showpost.php?p=62737969&postcount=17
Click to expand...
Click to collapse
Yes. Though mine seemed even more complex. I couldn't boot into the bootloader that way.
What I found is that via some combination of volume/power keys and having power plugged in or not, I finally:
* did a boot into safe-mode
* discovered I was rooted
* used to to install ROM manager
* rebooted, out of safe mode
* ran ROM manager
* rebooted to bootloader
And then did what dukey said.
strange i have tried to log using facebook button but it keeps sending me the '"Sorry, you must use a phone account to submit this application."'
any ideas?
Hi,
I got stuck when posting my numbers with the following answer:
We regret to say that the information you are searching is not found. Pleae mail to [email protected], We'll respond to you as soon as possible, thanks.
Click to expand...
Click to collapse
Has anybody else got stuck here or knows how to get around it?
I have not received an answer to the mail I sent them yesterday - I hope somebody replies at all
lippl
The .exe linked in the first post is not required to determine the product ID. It can be determined using universal code *#*#1357946#*#* (which returns an 8-digit code as expected)
Further, the .exe linked in the first post does not get a clean bill of health at VirusTotal - nothing definitive but not clean. Anyone planning to use it to generate an unlock code should use reasonable caution, sandbox the application or (better) run it on a disposable VM.