Related
Hi,
I have a H2000 Phone, that is stuck in a boot loop,
How it all started:
I tried to use "LCD density changer"
and I set it to change density on boot (massive mistake)
when it rebooted it shows that android animation over and over again, it locks up then vibrates then starts the animation again... CRAP!!!
so my thoughts are well like the few android phones and tablet that I have had previously I will just re-write the ROM to it somehow
well..... seems as it that is like getting blood from a stone... nobody has it???.. how can this be???
nobody at all has ever written a customs ROM for this phone??, surely not?..
I have looked high and low for a ROM for this phone, spending hours using "google Translate" to read though Chinese forums, even randomly signing up to the forums to find that I can't fins any info at all.
I do not have the IMEI problem that most people are talking about (yet)
because I cant even get that far,
i have downloaded the system.img, recovery.img etc etc. for the device, but unless I can get them onto the phone they are useless to me,
I have tried the SPmultiportflashdownloadproject.exe and installed the Mediatek MT6516 drivers and the device is recognised by windows (for about 5 second after being plugged in then the phone shows the charging indicator on the screen and the device is no longer accessable by windows)
as far as I know I have the right bits to flash the firmware or ROM to the device, but i'll be buggered to know how to do it,
I have looked all though the forums and seems as nobody so far has a solution
i can get into revocery <3e> mode by holding "+" and "Power" this gives me a green android and a explanation mark inside a triangle
if I press the "home" soft key I get
Android system recovery <3e>
Android system recovery utility
then the options of;
Reboot system now
apply sdcard:update.zip
wipe data/facory reset
wipe cache partition
So I would assume I would be after an update.zip package to progress using this method.
I can also get a "factory menu" by pressing the "Camera button" and "power button" this gives me:
"Factory Mode"
with the option of:
Full Test
Item Test
Test report
clear flash
version
reboot
I can go through the menu items using the volume "-" and "+" keys but cannot select any of the options, I have tried a few different combinations of buttons but nothing helps..
I do however have access to a working H2000, if this helps at all, I doubt it..
I ripped the build.prop off the working H2000 and will post that in a sec
would be nice if somebody could write an update.zip with the build.prop info and sign it for me???...
Please help me...
Ok I used
SP flash tool v1.1052.3
I flashed the rom I had to the device,
but i had to untick preloader for the prog to recognise my device
and it told me to insert the cable in 5,4,3,2,1
BAM it worked..
It turns on and works!!!
...but the colour is like it is inverted..??
but I do have access to the device now
should be able to access via adb connect "ip" when I get home to my wireless connection and maybe mount /system as rw and push the build.prop file
it could be that I have the wrong firmware for this hardware? as I know some were resistive (H3000 is resistive in a different casing and some are Capacitive, H2000)
I think i need to find the recomended software "SP flash tool v1.1051.5"
if anyone knows where i can find it then i will try again
Cheers,
Keg
Ok now to make things worse
The dual sim IMIE's have disappeared... (DANG!!)
I have now hit my brick wall, it looks like to do anything usefull from here on I will need the special programming cable... without it I cannot do much usefull...
if anyone knows of somebody in Canberra Australia with a cable that would save me some greif...??? Lol..
on another side note, I DID work out how to successfully change the LCD density on this phone,
I STRESS HERE I CANNOT BE HELD RESPONSIBLE WITH ANY MISLEADING OR WRONG INFORMATION THAT IS PROVIDED BELOW, I AM RE_WRITING THIS FROM MY PROVEN TO BE HORRIBLE (just ask my missus) MEMORY,
I am providing it as a rough guide, and it may not work or could brick your phone like i did to mine!!!
Ok, here we go...
it involved installing Z4Root, running the permanent root option, then using ADB from the Android SDK, I typed
"adb devices" to check that only one device was connected,
then;
"adb shell"
this gave me "$" then I typed;
"su"
and accepted the superuser request on screen
then it gave me "#"
from here I typed
"Mount" to advise of the current mountings it told me /system was from /dev/block/mtdblock8
then to access and modify the build.prop file I had to make /system Read /Write by typing in;
"mount -o remount,rw -t yaffs2 /dev/block/mtdblock8 /system"
then i typed
"chmod 777 /system"
"exit"
"exit"
From here I could then use the file explorer that comes with phone to open up /system and navigate to build.prop
then by selecting it i could scroll down the screen to almost the end where is says
LCD DENSITY=160 Or something like that
and I changed it to 140 the first time and then saved.
I reset the phone and once it booted the LCD was set to 140!!!
I tried again by doing all the above again (to get rw in system again) and set to 100 rebooted and it was set to 100 (everything is smaller and doesn't croud the screen anymore) obviously this ROM wasn't ment to be set at anything else or b easily modifiable due to the face that nothing re-sizes properly and it looks kinda crappy... (Do'H, though on a plus side the browser should be able to scale a page better now though)
So after all that I DO NOT recommend doing this procedure unless you have the programming cable and the Factory ROM just incase you bugger it up like I did....
-CHEERS
-KEG
Hi there,
I hope this helps, here is a link for the H2000 rom, try this site as its great for chinese phones, www.pandawillforum.com thanks Mark
http://www.pandawillforum.com/viewthread.php?tid=3536&extra=page%3D1
also look at this link for flashing
http://www.pandawillforum.com/viewthread.php?tid=3536&extra=page%3D1
Help! H2000 Incoming calls rejected after "clean data"
My phone is a H2000 iPhone 4 Clone with Android 2.2 Froyo. Here is the problem: I have went to Settings and then Manage Applications. I scrolled down to the Settings application and clicked it.
I selected the buttons Clear Data and Clear Cache. I was then sent to the android homescreen. Since then, whenever someone tries to call my phone, My phone will vibrate for a second, not show anything on my screen, then display on the other callers phone "User Busy". However I can still call to other people, that works atleast.
Do any of you know a solution? The phone is definetly getting the call because it vibrates when it gets the call, it just doesnt show anything on the phones screen, thus I cannot accept the call and then the other caller gets "User Busy" on their phone. Any advice? Please? Im really stumped here . Thank you in advanced!
Edit: The phone was working FINE before I did this to the Settings application.
Thanks a lot
update+working skype
Hello.Nice to meet you.Did anybody have a update for H2000? Did anybody tried to use skype on this phone? Is there a working version of skype?Thank you.
Hello friends, Please note that i tried installing ClockworkMod 3.1.0.1 but it refused to setup for some reason, even though i did everything right i.e. holding down the down vol key and power button etc but like others i only get the green android with the exclamation mark in the middle, so i do not have a backup unfortunately ;(
Anyway the story starts here:
Please be patient with me though as i am new to all this but learning fast.
Got a new Asus transformer TF101 (with keyboard) for only 5 days with
Device serial: B70KAS3?????
Build number: HMJ37.WW_epad-8.4.4.11-20110711
Android version: 3.1
Didnt know about Razorclaw ability to root B70 :-(
Anyway on going online on the TF101 for the first time, I immediately got a message saying there was a new os update available, the TF101 auto downloaded it and i then immediately updated it, thinking that the new update was best for me :-(
After the update, i then had -
Build number: HTK75.WW_epad-8.6.5.21-20111216
Android version: 3.2.1
Razorclaw doesnt work on my TF101 however i was able to use use the WW_epad-user-8.6.6.19.zip update on it and then was able to root using Razorclaw.
After that everything worked fine until i used 'Rom Manager' to create a script that was to change my hostname to my preferred one instead of the usual 'android_????????????', i then set it to do so on boot within 'Rom Manager'.
I then used 'Rom Manager' 'reboot' script to reboot the TF and now it boots then flashes locked screen for a second and shuts down and the same thing happens when i power it up again
If i am lucky and quick, i can put in the password and see the desktop just before it shuts down.
I have a feeling it the script i created and set to execute on boot is what is causing the shutdown.
Is there anyway to fix this?
It not a low battery issue, already checked that.
Was thinking along the lines of a key combination to prevent scripts running on boot time.
Dont really want to wipe the TF, as it already taken me 5 days to get it setup how i want it and now this!
It sounds like you have a stock recovery and a buggered up system.
You might be able to recover with adb, but you'll have to know what to stop/kill before it reboots. If it's enable, adb will be active well before you see the lock screen. There might also be some tools in the android sdk, perhaps ddms.
What exactly is in this rom manager script? Perhaps it is passing a reboot via one of the partitions. You would need to clear the command to stop the reboots or just kill the process that is rebooting.
That's all I gots. Good luck!
gee one said:
It sounds like you have a stock recovery and a buggered up system.
You might be able to recover with adb, but you'll have to know what to stop/kill before it reboots. If it's enable, adb will be active well before you see the lock screen. There might also be some tools in the android sdk, perhaps ddms.
What exactly is in this rom manager script? Perhaps it is passing a reboot via one of the partitions. You would need to clear the command to stop the reboots or just kill the process that is rebooting.
That's all I gots. Good luck!
Click to expand...
Click to collapse
thanx for responding mate...appreciated.
the script is just a simple script with just one line with tr3ble being the new hostname, its exactly as below:
setprop net.hostname tr3ble
I'll have a tinker with adb but what how do i search for processes to stop/kill using adb as im not that clued up with linux commands
I'm not a pro either, but I think "ps" will show you the process and "kill <pid>" will kill them. There might be a better way and I haven't tested this, so if you end up in a worse situation than then one you are in, it's all on you.
I don't think that changing the hostname will cause a reboot. I think the "reboot" command from rom manager is somehow stuck. I think it passes a reboot command via one of the partitions so that it can "find" it when it restarts. You would just have to clear the command. I think it's somewhere in the /cache directory, but that is just a guess.
gee one said:
I'm not a pro either, but I think "ps" will show you the process and "kill <pid>" will kill them. There might be a better way and I haven't tested this, so if you end up in a worse situation than then one you are in, it's all on you.
I don't think that changing the hostname will cause a reboot. I think the "reboot" command from rom manager is somehow stuck. I think it passes a reboot command via one of the partitions so that it can "find" it when it restarts. You would just have to clear the command. I think it's somewhere in the /cache directory, but that is just a guess.
Click to expand...
Click to collapse
Wow...you are definitely pointing me in the some direction though, in the begining i didnt have a clue what to do and where to look but now i have a few things to try...i'll see how things go with adb and report back.
Thank you for your time and patience mate
Update:
I tried everything i could but just didnt seem to have much time to do much using adb so i bit the bullet and did a data wipe, but to my joy, after the data wipe the TF was still rooted and my adhoc hack was still in place. If only took me bout an hour to then reinstall all my apps, which was more or less easy as i had them all in one folder on my microSD.
So all in all, the data wipe which cured the shutdown after restart wasnt sooo bad afterall.
Thank for your help mate!
....Happy New year!
b00b said:
Update:
I tried everything i could but just didnt seem to have much time to do much using adb so i bit the bullet and did a data wipe, but to my joy, after the data wipe the TF was still rooted and my adhoc hack was still in place. If only took me bout an hour to then reinstall all my apps, which was more or less easy as i had them all in one folder on my microSD.
So all in all, the data wipe which cured the shutdown after restart wasnt sooo bad afterall.
Thank for your help mate!
....Happy New year!
Click to expand...
Click to collapse
Did the same exact procedure when the same thing happened to my TF earlier this month.... Good to know that i wasn't the only one that faced this situation.
Sent from my Transformer TF101 using xda premium
Righto. Before we go any further, jsut to say I am a relatively experienced rooter of Android handsets. Not tabs, granted, but handsets. Last night I rooted my TF and flashed Megatron and recommended kernel, no problem. I've had no problem taking nandroid backups or restoring as I've done that several times today, all with expected results.
Then I opened ROM Manager and allowed the app to update, I guess updating CWM too.
I then fiddled with SetCPU overclocking the CPU. This caused the tab to stutter a bit. Then freeze. Anyway, I hard rebooted and went into recovery to try and flash the backup I took about an hour ago. Now, CWM looks different (I guess this is where ROM Manager updated). I flashed the backup which seemed to go ok, but then when the TF rebooted I got an Android message saying that encryption hadn't worked properly, and that I would need to do a full (factory) reset. I hit ok and let it do it's think. The TF rebooted, but went direct into Recovery.
I tried wiping everything using Factory Reset, and wiping Dalvik, etc, but every time I tried I got a message saying "E: Can't mount /sdcard/" and then it reverted back to the main menu structure. Even when I choose "Install zip from sdcard" > "choose zip from sdcard" I just get a message up saying "E: Can't mount /sdcard/" and that's all she wrote. I think a) ROM Manager may have caused this and b) it's royally wrecked.
I did find teh following in a TF guide regarding cold booting:
-Quote-
11. Now do a Cold Boot (aka Hard Reset). This cleans system caches, but does not delete any user data.
Unplug the power cord and shut the unit off. Press and hold the VOL DOWN and then POWER button at the same time for at least 10-12 seconds until after the start-up screen appears and is joined by some small print at the top of the screen, then let them both go. If the TF booted the way it always does, you have not accomplished the task, try again until you have seen the 2 icons in the screen.
After a few seconds you should see a couple of icons in the middle of the screen called "Wipe Data" and "Android". The right "Android" will have a green highlight fading in and out. Wait a few more seconds until the term "Cold Booting Linux" appears in the list near the top of the screens and let it reboot. If you own a keyboard dock be sure you do this with the dock connected.
This process applies to all TF models, however, if your Prime or tf300 is locked up, there is a reset available using the hole just below the microSD slot, this is NOT the same as a hard reset.
12. Finally, restore your photos, docs etc & reinstall your apps from the backups, one group at a time & cold boot between each group that you restore. (Unless you are resetting because of system instability. In which case, read the next section, first.)
-Unquote-
I tried doing this but the TF froze at the point where the unit says "Cold-booting Linux". I left it for a good 30 minutes but no joy...
The other issue I have is that even when I attach my TF to my PC the PC doesn't recignise the unit. It knows I'm trying to attach something but it doesn't know what. Therefore I don't think I can flash anything like a new CWM version or kernel if the PC doesn't know where or what to flash to...?
I'd love to hear anyone's thoughts on this one...
Thanks in advance!
"Then I opened ROM Manager and allowed the app to update, I guess updating CWM too." - Never use ROM manager on the TF, it causes extensive problems. There is a warning thread about this in General.
You'll want to try running Roach2010's fix, either via my PERI tool (in my sig) or by manually typing the commands.
Lifesaver! One problem - when I plug my TF into my PC using the USB cable it doesn't recognise it. Won't this be a problem?
Sent from my GT-I9100 using xda app-developers app
(Also, I've replied a bit more to your post on Transformer Forum - Thanks mate!)
Alright you're going to want to download this while you read -- http://xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)/STOCK+ROMS/ICS+.24
Quick guide:
1. Connect cable to computer and turn device on while holding down Volume Up. Screen will stay off, but USB will come on.
2. Find “APX” device in Device manager and update driver, then point it at usbpcdriver directory from the zip.
3. Run download.bat.
In the link below a driver package is also included, you need to either...
Code:
Open the Start Menu, type 'cmd' and hit enter, then type:
pnputil -a C:\path\to\driver folder\NvidiaUsb.inf file
exit
Then plug in the TF in APX mode and windows will find drivers automatically
Or you right click computer and hit 'Manage' and then hit 'Device Manager', find the ? entry that says APX and right click and hit 'update driver', then navigate to the folder.
Download the unbrick .zip from here: http://xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)/STOCK+ROMS/ICS+.24
(Before each file are 2 letters, (US, WW, CN, TW...) pick the one that is your Region. I'm assuming you need WW, which stands for World Wide, but if you reside in Taiwan take TW, China take CN and America take US.
Also download Wheelie NvFlash from here: http://androidroot.mobi/2012/05/31/wheelie-for-windows-beta/
Extract it, and copy the Contents of the folder into the Unbrick .zip folder's contents main folder, Overwrite any files that conflict.
Then you should be able to run Reflash_Sbkv#.bat to unbrick your TF in APX mode that is connected, try Sbkv2 first, then if you get access denied try Sbkv1.
Hope you're sorted out!
Hi guys,
I've been reading you for a while, but this is actually my first post.
Currently stuck with a "Unfortunately, Launcher has stopped" on my tablet, with no access to any menus except my Settings. The menu bar (back, home and multitasking) is now gone. I've got my keyboard to navigate, but something in the display is also quite wrong, image seems to be zoomed, or set at the wrong resolution. Tried to search on the forum, but all posts found were not about the same rom or the same issue. Sorry if I missed one.
Here's a little background story:
I've rooted my TF300T about a month ago and installed Hydro 4.1. It has been working very well since then, but in the last days, I thought that my tablet felt a little slower than usual, so I started searching if an update to 4.2 was available.
I'm not sure if this is what caused the issue or not, but I went into my "Power button" menu and went into "Recovery" mode (instead of Shutdown, reboot, etc.), which then restarted my unit into TWRP menu.
I then selected the "System" submenu and simply touched "Reboot". (terms might not be exact). At the first reboot, I got the problems that I described.
Can't do much, popup keeps appearing on my screen. I haven't tried yet to clear the cache of my Launcher, which I'm trying to avoid as I would prefer to avoid rearranging 5 pages of icons, but between that and reinstalling everything, obviously I prefer to simply lose my display preferences.
Can anyone help me about what caused my issue, and what can I do now?
Here are 2 screenshots that I took, showing that my bottom menu is missing and that the fonts aren't set right (clock and left icon). Also, my notifications menu now appears near the middle of my screen.
EDIT: I unfortunately cannot post links yet
I remember installing an app (with root access) that gave me a menu about my resolution. One thing that I'm wondering, could it be that the resolution got changed and I simply never rebooted since the change, which now caused my Launcher to crash? How can I launch an app without having access to the app menu?
Thanks in advance for your help.
irepressed said:
Hi guys,
I've been reading you for a while, but this is actually my first post.
Currently stuck with a "Unfortunately, Launcher has stopped" on my tablet, with no access to any menus except my Settings. The menu bar (back, home and multitasking) is now gone. I've got my keyboard to navigate, but something in the display is also quite wrong, image seems to be zoomed, or set at the wrong resolution. Tried to search on the forum, but all posts found were not about the same rom or the same issue. Sorry if I missed one.
Here's a little background story:
I've rooted my TF300T about a month ago and installed Hydro 4.1. It has been working very well since then, but in the last days, I thought that my tablet felt a little slower than usual, so I started searching if an update to 4.2 was available.
I'm not sure if this is what caused the issue or not, but I went into my "Power button" menu and went into "Recovery" mode (instead of Shutdown, reboot, etc.), which then restarted my unit into TWRP menu.
I then selected the "System" submenu and simply touched "Reboot". (terms might not be exact). At the first reboot, I got the problems that I described.
Can't do much, popup keeps appearing on my screen. I haven't tried yet to clear the cache of my Launcher, which I'm trying to avoid as I would prefer to avoid rearranging 5 pages of icons, but between that and reinstalling everything, obviously I prefer to simply lose my display preferences.
Can anyone help me about what caused my issue, and what can I do now?
Here are 2 screenshots that I took, showing that my bottom menu is missing and that the fonts aren't set right (clock and left icon). Also, my notifications menu now appears near the middle of my screen.
EDIT: I unfortunately cannot post links yet
I remember installing an app (with root access) that gave me a menu about my resolution. One thing that I'm wondering, could it be that the resolution got changed and I simply never rebooted since the change, which now caused my Launcher to crash? How can I launch an app without having access to the app menu?
Thanks in advance for your help.
Click to expand...
Click to collapse
What you describe is likely caused by changing the resolution. Are you still running hydro 4.1?
You can likely recover by replacing your build.prop or editing the one you now have. build.props are usualy rom specific so you need one from the rom you are using.
tobdaryl said:
What you describe is likely caused by changing the resolution. Are you still running hydro 4.1?
You can likely recover by replacing your build.prop or editing the one you now have. build.props are usualy rom specific so you need one from the rom you are using.
Click to expand...
Click to collapse
Yes, still using Hydro 4.1. I do have a build.prop editor installed on my tablet, but since I can't launch app, I don't know how to do it.
I'll try to connect the tablet to my PC and see if I can get access to my file from there.
Thanks!
irepressed said:
Yes, still using Hydro 4.1. I do have a build.prop editor installed on my tablet, but since I can't launch app, I don't know how to do it.
I'll try to connect the tablet to my PC and see if I can get access to my file from there.
Thanks!
Click to expand...
Click to collapse
I'm presently downloading 4.1 hydro to retrieve the build.prop. If you unzip it the build.prop is /system/build.prop also located there on your tab. I have another fifteen minutes to download if you wish for me to supply the file!
tobdaryl said:
I'm presently downloading 4.1 hydro to retrieve the build.prop. If you unzip it the build.prop is /system/build.prop also located there on your tab. I have another fifteen minutes to download if you wish for me to supply the file!
Click to expand...
Click to collapse
If you could, I would appreciate it!
Only thing left, how can I send the file to my TF300T without access to my apps? I'm currently trying to cheat by opening my apps using the Share feature with screenshots taken, but so far, no success.
irepressed said:
If you could, I would appreciate it!
Only thing left, how can I send the file to my TF300T without access to my apps? I'm currently trying to cheat by opening my apps using the Share feature with screenshots taken, but so far, no success.
Click to expand...
Click to collapse
We should be able to push with adb, set permissions, and reboot.
---------- Post added at 04:58 PM ---------- Previous post was at 04:36 PM ----------
http://www.mediafire.com/?tk3cifzci0vw24e
place the build.prop from the zip file into the directory with fastboot.
Open terminal or cmd in the directory with fastboot.
Boot into twrp – twrp provides adb access by default.
Use twrp mount menu and check mount system.
Then type
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
in twrp reboot system
type
adb kill-server
tobdaryl said:
We should be able to push with adb, set permissions, and reboot.
---------- Post added at 04:58 PM ---------- Previous post was at 04:36 PM ----------
place the build.prop from the zip file into the directory with fastboot.
Open terminal or cmd in the directory with fastboot.
Boot into twrp – twrp provides adb access by default.
Use twrp mount menu and check mount system.
Then type
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
in twrp reboot system
type
adb kill-server
Click to expand...
Click to collapse
Ok, my Fastboot folder is currently at the root of my C drive on my PC
I entered your command and got after the first one "adb server is out of date. killing...
* daemon started successfully *
error: device not found
FYI, before I got your last post, I used Android commander to push the build.prop that I still had on my PC when I installed the custom hydro 4.1 rom.
After my reboot, I got the Asus logo, than a black screen that does nothing.
I then rebooted in Fastboot and followed your instructions.
So now, it seems that my pc doesnt see my tablet anymore when in TWRP. is this normal? Do I need to restart it after checking "Mount system"?
irepressed said:
Ok, my Fastboot folder is currently at the root of my C drive on my PC
I entered your command and got after the first one "adb server is out of date. killing...
* daemon started successfully *
error: device not found
FYI, before I got your last post, I used Android commander to push the build.prop that I still had on my PC when I installed the custom hydro 4.1 rom.
After my reboot, I got the Asus logo, than a black screen that does nothing.
I then rebooted in Fastboot and followed your instructions.
So now, it seems that my pc doesnt see my tablet anymore when in TWRP. is this normal? Do I need to restart it after checking "Mount system"?
Click to expand...
Click to collapse
Ok, I just killed my adb.exe, tried the command again and that got rid of the out of date error.
But, still stuck with the "device not found".
irepressed said:
Ok, my Fastboot folder is currently at the root of my C drive on my PC
I entered your command and got after the first one "adb server is out of date. killing...
* daemon started successfully *
error: device not found
FYI, before I got your last post, I used Android commander to push the build.prop that I still had on my PC when I installed the custom hydro 4.1 rom.
After my reboot, I got the Asus logo, than a black screen that does nothing.
I then rebooted in Fastboot and followed your instructions.
So now, it seems that my pc doesnt see my tablet anymore when in TWRP. is this normal? Do I need to restart it after checking "Mount system"?
Click to expand...
Click to collapse
Slowdown, I'm getting behind. I'm willing to help but you are now worse off than before.
Sit tight for five minutes and I'll try to give you a twrp flashable zip for your build.prop and hope that is the extent of the damage.
If not we'll try to go from there.
http://www.mediafire.com/?ybplc1ws8uvskhf
This is a twrp flashable zip that only replaces your build.prop with the one from hydro 4.1.
tobdaryl said:
Slowdown, I'm getting behind. I'm willing to help but you are now worse off than before.
Sit tight for five minutes and I'll try to give you a twrp flashable zip for your build.prop and hope that is the extent of the damage.
If not we'll try to go from there.
This is a twrp flashable zip that only replaces your build.prop with the one from hydro 4.1.
Click to expand...
Click to collapse
Alright, I'll wait for your answer before trying anything else.
So now, I've got your latest .zip file.
Still can't see my TF300T from my PC, so, ADB is a no go for now.
In fact, I do see it in the Device Manager, but since my last reboot, it now shows an exclamation mark on it as if my drivers weren't good.
Since you mentioned the file is a flashable zip, I'm guessing that I can flash it using TWRP without going through my PC?
Can you give me precise info on that, since I do not want to mess with my system more than I already did.
Thanks
irepressed said:
Alright, I'll wait for your answer before trying anything else.
So now, I've got your latest .zip file.
Still can't see my TF300T from my PC, so, ADB is a no go for now.
In fact, I do see it in the Device Manager, but since my last reboot, it now shows an exclamation mark on it as if my drivers weren't good.
Since you mentioned the file is a flashable zip, I'm guessing that I can flash it using TWRP without going through my PC?
Can you give me precise info on that, since I do not want to mess with my system more than I already did.
Thanks
Click to expand...
Click to collapse
Look at the bottom of my previous post. You will find a new link there. Just flash with twrp and reboot. Don't worry about wiping or any of that, just flash and reboot.
tobdaryl said:
Look at the bottom of my previous post. You will find a new link there. Just flash with twrp and reboot. Don't worry about wiping or any of that, just flash and reboot.
Click to expand...
Click to collapse
Yep, that's the file I was talking about.
I now need to flash and reboot, your file is at the root of an SDcard in my TF300T, I go through the Install menu and then, can't seem to view the content of my sdcard. Tried to mount it first but can't select it either, it will simply stay on "Internal Storage".
EDIT: The RCK icon is the only one right now that boots me into something. If I try the USB icon, it just stays on that screen forever.
Trash the two zips you have downloaded. I'm providing a new one for when we get back to that point. And there will be no doubt about which zip you are using.
http://www.mediafire.com/?hagehu5qu5ky6sf
OK. First I'll explain your earlier comment about adb being old. Twrp expects a recent adb or refuses to allow adb access ( we'll not worry at the moment about that but it is something you need to address later (I hope).
If you have a cord between your tablet and pc remove it. The sdcard may be mounted as data on the pc and not allow twrp to mount it.
You have been using this sdcard prior to this exercise?
Do you have any backups or flashable zips or anything of that nature on your internal sdcard?
If so what?
tobdaryl said:
Trash the two zips you have downloaded. I'm providing a new one for when we get back to that point. And there will be no doubt about which zip you are using.
OK. First I'll explain your earlier comment about adb being old. Twrp expects a recent adb or refuses to allow adb access ( we'll not worry at the moment about that but it is something you need to address later (I hope).
If you have a cord between your tablet and pc remove it. The sdcard may be mounted as data on the pc and not allow twrp to mount it.
You have been using this sdcard prior to this exercise?
Do you have any backups or flashable zips or anything of that nature on your internal sdcard?
If so what?
Click to expand...
Click to collapse
Zips trashed, kept only the one provided in your latest answer.
No cord between PC and tablet. Still unable to click on "Using external SD" or "Mount SDCard". It simply won't let me check the box or switch the bullet.
As for using this SDcard before, yes in a PC, but no, first time in my Asus. Also tried with another one just in case and same result.
As for backups and flashable zips, I kept everything from when I did my root and rom install.
I do know that I have a backup in the Restore menu of TWRP, which seems about the time I installed it. I suppose I could simply do a restore and avoid additional headaches, but my question is, what exactly will it restore? At this point, I'm mentally prepared to go back to what I had after installing Hydro 4.1, as long as I can use the tablet ASAP.
Asap = restore your backup.
If I'm restoring a different rom I'll wipe Cache, Dalvik Cache, and Factory Reset. If the backup is from the same rom I'm flashing and I want to keep the apps I have Installed since the backup I won't Factory Reset.
Good Luck!
tobdaryl said:
Asap = restore your backup.
If I'm restoring a different rom I'll wipe Cache, Dalvik Cache, and Factory Reset. If the backup is from the same rom I'm flashing and I want to keep the apps I have Installed since the backup I won't Factory Reset.
Good Luck!
Click to expand...
Click to collapse
So, I did the restore, and I'm up and running, but, no more Hydro 4.1. I guess my backup was probably what got done right before the installed it.
The good thing is, my tablet is working again and my root is still active. The bad part is that I'm gonna have to dig my head again in all the tutorials and try to find the best one.
Hey, I wanted to say a huge thank you for all your help, if it wasn't for guys like you, newbies like me would be stuck with useless thin computers.
irepressed said:
So, I did the restore, and I'm up and running, but, no more Hydro 4.1. I guess my backup was probably what got done right before the installed it.
The good thing is, my tablet is working again and my root is still active. The bad part is that I'm gonna have to dig my head again in all the tutorials and try to find the best one.
Hey, I wanted to say a huge thank you for all your help, if it wasn't for guys like you, newbies like me would be stuck with useless thin computers.
Click to expand...
Click to collapse
Great I'm glad you are happy. I had hoped for the outcome you expressed but this works also.
You're welcome!
Hallo,
being new to this forum and also new to Android devices, please feel free to move my post into the correct section of the forum if I used the wrong one. The use of the search function is also not unknown to me, however I may not know all terms to be used (rookie) and english still is a foreign language for me.
Anyway, I have a serious problem with my brandnew Jiayu G4T phone and at least I need some help in sorting my thoughts and ideas after several days of browsing through the community.
What I know for sure:
Phone starts booting but stops on the third screen (1st: Jiayul ogo white, 2nd: Jiayu logo green falling in place, 3rd: Jiayu logo white fading).
I am able to boot into stock recovery and into factory mode (mostly chinese characters).
I have access to my phone by adb shell and can look into the directories.
The event occured after an overnight update with weird behavior of the phone (what happened is posted in the assumption section, it was still pretty early and I was clearly not fully awake.
I had the Xposed framework and XPrivacy installed and running. All other apps were pretty common.
In ADB my phone is listed as 0123456789ABCDEF (weird number)
What I do not know / Assumptions:
In /data I see plenty of files telling me that the data wipe from recovery was not successfull, the data belong to previously installed apps.
It seems that I was able to flash a new ROM, in system/app I do not see any of my previously installed apps. Superuser.apk is still present.
I also can access data however only after using su in shell.
I cannot delete the data using rm or wipe data being in [email protected] #, I have no idea why. Read only....
SP Flash tool told me that the flash of the new ROM was successful (red, pink, yellow progress bar followed by green circle). I think that is a good sign.
I also was able to apply ADB sideload for installing a new ROM and the phone told me I was successful. Not sure if this is true considering that my phone still is not booting.
After finding my phone in the morning mobile connections were both down, I think that an Android update was not successful and it might have happened that I restricted this very app with XPrivacy inadvertently.
The phone identifier seems to tell me that XPRivacy might still be active somewhere....
What I think about the next steps:
I think that getting rid of the old data might be the key for success, but I have no idea HOW....
Any thoughts from your side re highly appreciated,
Thomas
Tomcat117 said:
Hallo,
being new to this forum and also new to Android devices, please feel free to move my post into the correct section of the forum if I used the wrong one. The use of the search function is also not unknown to me, however I may not know all terms to be used (rookie) and english still is a foreign language for me.
Anyway, I have a serious problem with my brandnew Jiayu G4T phone and at least I need some help in sorting my thoughts and ideas after several days of browsing through the community.
What I know for sure:
Phone starts booting but stops on the third screen (1st: Jiayul ogo white, 2nd: Jiayu logo green falling in place, 3rd: Jiayu logo white fading).
I am able to boot into stock recovery and into factory mode (mostly chinese characters).
I have access to my phone by adb shell and can look into the directories.
The event occured after an overnight update with weird behavior of the phone (what happened is posted in the assumption section, it was still pretty early and I was clearly not fully awake.
I had the Xposed framework and XPrivacy installed and running. All other apps were pretty common.
In ADB my phone is listed as 0123456789ABCDEF (weird number)
What I do not know / Assumptions:
In /data I see plenty of files telling me that the data wipe from recovery was not successfull, the data belong to previously installed apps.
It seems that I was able to flash a new ROM, in system/app I do not see any of my previously installed apps. Superuser.apk is still present.
I also can access data however only after using su in shell.
I cannot delete the data using rm or wipe data being in [email protected] #, I have no idea why. Read only....
SP Flash tool told me that the flash of the new ROM was successful (red, pink, yellow progress bar followed by green circle). I think that is a good sign.
I also was able to apply ADB sideload for installing a new ROM and the phone told me I was successful. Not sure if this is true considering that my phone still is not booting.
After finding my phone in the morning mobile connections were both down, I think that an Android update was not successful and it might have happened that I restricted this very app with XPrivacy inadvertently.
The phone identifier seems to tell me that XPRivacy might still be active somewhere....
What I think about the next steps:
I think that getting rid of the old data might be the key for success, but I have no idea HOW....
Any thoughts from your side re highly appreciated,
Thomas
Click to expand...
Click to collapse
This is your solution right here (hopefully)
1) If you have not installed the drivers, download, unpack and install drivers http://uloz.to/xwWU1vKw/mtk6589-driver-zip.
2) Download and unpack Stock ROM http://www.ejiayu.com/en/News2-1-100.html.
3) Download and unpack FlashTools http://uloz.to/x6U5ZDKs/spflash3-1316-0-150-zip, and Click on Flash_tool.exe.
4) Click button "Scatter-loading" and select a the MT6589_Android_scatter_emmc.txt in ROM.
5) Turn off your phone and remove the battery!
6) Press F9 (or hit Download button) and connect your phone into the computer via USB data cable.
7) The process will start and a red progress bar will appear after color purple, yellow. And green circles display. Finish. You can now safely disconnect your phone and turn it on.
Egbert
jimmys01 said:
This is your solution right here (hopefully)
Click to expand...
Click to collapse
This actually is a thread I found very early and unfortunately it was not working.
Honestly I assume that Isomehow lost root: How does this sound in the view of my observations and assumptions?
Thomas