Content Count

Joined

Last visited

Community Reputation

About nontha

Yes . I had already mounted using "Mount and storage" menu in cwm recovery mode menu , and thus I could easily access all partitions ; which I had learned only later & I had mentioned this in 2nd point of previous comment .
The problem I have now is I can't use adb while I am in the OS i.e. when the phone is running android 2.3.6 . I can easily use adb when the phone is in recovery mode . Also , i think usb debugging is not enabled when the phone is in OS . The reason I say this is I connected my phone to PC and ran "android control" (or chrome's Vysor or android screencast) software on my PC . The phone is not detected by the software while its in android OS and also "adb devices" command shows no responses while the phone is in OS .

Thanks a LOT. :) I had recovered my memo data yesterday .
I am writing my Full results (as much as I remember) so that if someone needs , they could benefit from reading it.
I had recovered my data , specifically my notepad (memo) data from my phone . However , it was not by using adb pull . Before trying the adb pull command , I had backed-up my entire phone using cwm recovery's nandroid feature . In the resulting backup.ab file - i extracted it , and got all the /data and /system partitions as a ".tar" archive . I extracted the data.tar and opened the notepad-info file which was inside the com folder .
I might have recovered the data this way , because i wasnt able to adb pull anything from /data .
The reason for this was two-fold .
1.)My device was not detected as adb while i was using the OS . My device was detected as adb device only in the recovery menu . I think from what i have read , the reason for this is either usb debugging should be somehow disabled in the service menu which could be accessed by typing *#*#2846579#*#* in dialer , but since i cant use the touchscreen i cant access this service menu to enable usb debugging .
OR There are two adb drivers - one which works in recovery and one which works while phone is in OS & the adb drivers needed to be installed separately again while the phone is in the OS.However , i used device manager to update adb drivers and also installed the adb drivers already kept by Huawei in the stock rom; but still my device wasnt detected as adb while phone is in OS.
I had also used a different USB wire and connected to different USB ports to check whether the issue is broken cable or lack of voltage ; but to no avail .
I might have been able to pull /data if adb worked when phone was in OS mode .
2.) I realized only LATER (after extracting my data from nandroid backup) that /data and other partitions like /system were blocked - that is we cant view the important files for e.g. build.prop or even edit it . I could only see unimportant files using "ls" command in adb shell . Then i realised if i was in recovery mode , I needed to mount these partitions using "mounts and storage" in cwm recovery menu if I needed to access or edit the files in these partitions . After doing so , i was able to see and edit files inside these restricted partitions .
I guess this need for mounting only is there when i am in the recovery menu . I guess if i had adb in the OS , i might have been able to easily access these partitions .
Also before mounting using cwm recovery menu , I had used adb root for super-access & also used mount command in adb to access the /system parition as readable/writable memory ; but still i couldnt access the partitions fully.
3.) i might need to add .dll files to usb drivers folder or enter the signature keys of my laptop in android_usb.inf file (so as to have my phone detect my lap) -> and many other such methods I read in many forums ; so as to enable usb debugging and have adb while the phone is in the OS .
Right now , I want to be able to enable usb debugging while the phone is in the OS . I think being able to access adb is a sure sign of usb debugging being enabled , isnt it ? Since i cant use adb when phone is in OS , I must not have usb debugging . What could be the problem in my phone ?
Right now , I am attempting a last ditch effort to control my phone from my PC using android control or Chrome's vysor, but since adb is not detected and usb debugging seems to be not enabled WHILE the phone is in the OS, i cant use android control . But I can use android control when my phone is in recovery mode (cause in the recovery mode, adb is working) and i can see the recovery menu in my computer screen while using this program in my computer .
I want to control my phone using adb or android control while is in OS . I adb pulled the build.prop file and default.prop file . I made changes by adding the "persist.enable.usb" & other such commands in both these files and adb pushed it back into the phone ; so as to enable usb debugging. However , the default.prop returns to normal values when the phone is rebooted . I dont think those commands are to be edited into the build.prop either, it might have to be edited in the default.prop itself . Also even after editing the build.prop and rebooting the phone , nothing seems to have changed .
Is rooting the phone or full-level root access necessary for editing the default.prop permanently ?
What could be the problem ? - me not being able to use adb or have usb debugging when in OS .
Also , wbrambley , Thanks for everything . I cant express my gratitude enough . Yesterday , when i extracted the backup & recovered the data , I felt no euphoria at all . Maybe it was because i was more confident that I would succeed in some way, compared to a week before when i knew nothing about android and was depressed & had no hope that I would ever recover my data OR maybe because I had a greater resolve in improving myself or learning more about all this stuff rather than worrying about retrieving my data . I was hooked into tweaking android. Since your first reply in this post , I have learned a lot , and I can honestly say that the effort & enjoyment in experimenting is far greater than the result . Thanks for showing me the ropes .

I installed fastboot using android sdk . And then connected the phone during fastboot mode . The device is detected when i enter 'fastboot devices' . It shows "47782 fastboot" . Even fastboot reboot and fastboot reboot-bootloader works .
But when i type fastboot oem device-info OR fastboot oem get-bootinfo , I get no response . I only see these dots -> "..." as though it signifies waiting , and I have to stop this waiting by typing Ctrl+C if I want to get back to prompt .
However , instead of typing fastboot devices , if i type fastboot device i.e. without the letter "s" , I get "<waiting for any device>" response .
Edit : I guess this is normal since I am using stock GB bootloader , according to (1st page Tcpaulh's comment) in this : -
Shall i proceed with the flashing then ?

Even solidfiles is blocked by my ISP . So in the end , I installed a VPN and accessed both websites and downloaded the files . Now i have recovery image from mega.nz and one extracted from solidfiles zip . Both of them look the same and have the same file-size , so I assume its the same thing ?
Just curious about this one - > The zip is called B895 . Isnt that the name of a Stock rom or update of huawei g300 . So does this mean the zip file is a bundle having a stock rom + a custom recovery . So like you said , this is possible because Recovery is independent of ROM i.e. we can flash a custom Recovery alongside a stock ROM ?
Lastly , You mentioned that , that its best that the recovery be compatible with Gingerbread . Is it because the ICS roms have different partition sizes compared to the Gingerbread ROM . I read about this somewhere . So, more recent recoveries which were made to be compatible with ICS Roms, can cause a problem when flashing it alongside Gingerbread Roms because the /recovery partition and other partitions like /data have different sizes in GB and ICS ?
I am going to start doing the fastboot thing and also check the bootloader lock/unlock status !

Yes . That site is blocked by my ISP or in my region . I tried to access it via proxy sites and via my friend's network connection . But it didnt work . So, I need that name of the recovery image .
I know I am asking this again - >about whether rooting is necessary for flashing custom recovery . In that first link https://theunlockr.com/2013/06/06/how-to-flash-a-custom-recovery-on-the-huawei-ascend-g300/ , there is " You must have rooted your device before doing this procedure" line .
In the 2nd link - > page 64 of that thread i..e . its mentioned "You must have root and then install CWM"
And in this new link I found http://androidforums.com/threads/how-to-install-clockwork-mod-recovery-2-5-1-8-for-the-huawei-ascend.282068/ - > "You must be rooted. " line .
I just want to know why there are so many different opinions about this in the internet .
And also, would that Clock Work Mod Recovery 2.5.1.8 mentioned in the 3rd link work in my phone ?

I am using Stock Gingerbread in my G300 . Could anyone suggest me a Custom cwm recovery compatible with Stock Gingerbread ROM ? I haven't rooted the phone . Is rooting necessary ? I am thinking of flashing cwm recovery using fastboot commands in fastboot mode . My phone has a broken touchscreen which cannot be repaired . I am trying to recover data and looking for ways to flash a custom recovery without wiping my data . So I am looking for a custom recovery which is compatible with stock rom and will automatically enable usb debugging after flashing it .

I was reading as much as I could about fastboot , adb , rooting , custom ROM and all that stuff in the past few days . There is so much to know if we want to learn about android , that its really depressing. I have a few doubts which I want to clear before attempting all the procedure with fastboot ,adb etc : -
1.) Just out of curiosity , Is it possible to pull data using fastboot commands in fastboot itself,i.e. without having to flash recovery ? . From what I have read, it seems fastboot can only flash and control entire partitions and not edit or copy or remove single files and folders etc ; but I am just asking since long time members of android community might know if there is any such thing .
2.) You mentioned that if I inadvertently kept stock official update.app in my sd card, then when i boot into fastboot mode, the update.app might be flashed automatically . My doubt is will this happen when update.app is kept in root directory of sd card OR when it is kept in a folder which we name 'dload' which is kept inside sd card .
Also , instead of sd card , if the update.app was in the internal memory , will it still happen i..e will the phone search for an update file in the internal memory .
3.) You were right about Vol. Down + Power button will go to fastboot mode .
Does vol.up + vol. down + power button cause factory reset OR does it cause automatic flash upgrade of whatever stock upgrade file is kept in sd card or internal memory ?
Instead of stock ROM , if it was a stock recovery image , will fastboot mode automatically flash even that & if so , will I then have a re-installed stock recovery?
4.) Does flashing a custom recovery like cwm or unlocking bootloader(which I dont have to but still just asking) root the phone ? From what I have read in the internet , it doesnt root the phone . But there are too many conflicting opinions in the internet .
5.) Does fastboot mode have the ability to flash UNSIGNED zips (if i use fastboot flash or fastboot update zip command) ? And similarly, because of this reason, i kept a custom rom inside sd card instead of stock rom , will fastboot automatically flash even a custom ROM (unsigned or different sign comapred to stock ROMs) when I boot into fastboot mode ?
Does fastboot flash command only flash .img files OR does it flash zip files too ?
6.) A slight confusion I had - > If my bootloader is already unlocked , shouldnt I be able to flash Custom Roms and custom recovery using 'apply update from sd card' even in the stock recovery mode ->Or is it because i am having stock recovery mode, thats why we will get signature verification error when trying to install third-party custom Roms and recoveries .
7.) After booting into fastboot mode and the words "fastboot" appears in screen , is that the exact moment when i should plug my phone via USB cable to PC ? And just like adb commands , I must type fastboot commands in the command prompt in my laptop , right ?
8.) Is rooting a necessary prerequisite for installing or flashing custom Recovery ? This guide says its necessary : -
https://theunlockr.com/2013/06/06/how-to-flash-a-custom-recovery-on-the-huawei-ascend-g300/
& this too -
If so , I havent rooted and rooting requires USB Debugging too .
So , i am confused what this all means .
9?) You said that we must choose a recovery that is compatible with Gingerbread . I am looking at custom recoveries made by Dazzozo . If I install one of his cwm recoveries, shouldnt i have a CWM Rom in my phone instead of the stock ROM ?
OR is the only thing that matter is that the rom inside my phone be Gingerbread and NOT ICS or higher ? i.e. ROM being stock or custom doesnt matter ?
10.)Suppose I am flashing cwm recovery image named "cwm.img " & I had opened the command prompt inside platform-tools folder in android sdk folder - > while doing the command "fastboot flash recovery cwm.img" ; where should the cwm.img file be ? - should i place it in sd card or PC or should i place it inside the same platform-tools folder ?
OR could i give the full address of the file like -> fastboot flash recovery /sdcard/cwm.img
OR fastboot flash recovery C:\Desktop\cwm.img
11.) After i flash recovery.img using fasboot , which command should i enter to reboot the phone into recovery mode -> is it fastboot reboot-bootloader ? OR fastboot reboot recovery OR should i boot into recovery using fastboot boot recovery.img ?
And Thank You . Because of You , I now have working knowledge of android enough to get me out of such problems in the future .

I did buy a new digitzer and install it in my phone . It didnt work . I bought an extra digitizer and installed it just to ensure that the 1st digitzer was faulty or not . As i mentioned in my comment, It too didnt work . The problem was somewhere in the motherboard of the phone itself, and that the pinpoint location of the fault in the motherboard cant be traced or located , and that the only way to get the phone back to working condition would be to replace the entire board with a new one - > This is what the Huawei service center technician & another third party technician told me . I forgot to mention in my comment that all this problems started when water seeped into my phone 5 months ago when I was riding a bike while it was raining .
If I replace the board with a new one -> that doesnt help me at all in retrieving the data in the internal memory of my existing board(which is my foremost aim), and so in that regard, a new board is useless .
Another problem is the phone is out of stock(not available) & not supported by Huawei and also it is difficult to procure parts of it other than the digitizer & lcd , like the motherboard, camera parts, usb port board etc AND it is next to impossible to find people who have this phone but dont use it anymore and thus I cant even pluck a board from a second-hand phone even if I wanted to .
I did not approach chip-level servicing (soldering on the motherboard itself & not soldering ports or changing flex-cables) guys though to try to repair the issue in my board as I didnt want to risk my data being wiped or to have my phone back in a completely irreparable condition. Could chip-level servicing guys repair the phone (provided the issue in the board is not complex) , so that I can try this later after I am able to save my data ? - I mean can they repair the problem in the motherboard because of which the digitizer isnt working ?
On another note , I read about JTAG somewhere . Could the location of the problem in the board be found using JTAG ?
I didnt know that OTG mouse was possible with Y300 , since the Y300s and G300s phone came long before OTG and I thought they had weaker hardware which lacked the power to drive the signals for OTG . I thought OTG was possible only in newer phones from Nexus(older version Nexus) onwards which didnt have otg compliant hardware initially but could be tweaked to get otg.
I read a little about Custom Recovery , fastboot & adb yesterday . So I am going to try that today . I didnt do these steps for so long because I had thought my bootloader was locked ; and before doing fastboot, flashing etc ; bootloader unlocking had to be done and that would wipe my data . And i read about rooting procedures wihtout needing bootloader unlocking ; and after that , the phones settings could somehow be tweaked using rooting superuser access ? ; but I was too afraid of phone being bricked and all .
Thats why I settled for the procedure I mentioned in my 1st comment which I downloaded the official stock rom -> extracted the system.img from it -> opened app folder -> renamed any apk file to zip file i.e. apk-name.zip -> extracted this new zip file-> opened Meta-inf folder->copy-pasted updater-script and update-binary and build.prop to the folder which already had android.rsa(certificate), manifest.mf and cert.sf - > archived or compressed the folder to meta-inf.zip; just like I read in the article in the link I had mentioned . And i thought since this zip file was thus extracted from the downloaded stock ROM itself (which is the same version Stock Rom in my phone) , it would bypass the signature verification in my phone when i uploaded this zip using "apply update from sd card" in recovery ; but it didnt work . And I dont know why . I dont know in detail how this method works , I am just following the steps laid by someone . I would be really glad if I could understand why this method could work . This procedure would have been helpful if it worked because then I didnt need to flash any custom ROM or recovery cause I could have done all this with the Stock ROM itself , thus reducing the chances of wiping my data .
Only yesterday did I learn that my stock rom was already bootloader unlocked i.e. the phone was released by Huawei with the bootloader unlocked . I am using stock GB 2.3.6 . Only from the official ICS update to newer versions was the bootloader locked . I am going to check today whether my bootloader is unlocked using fastboot .
Also thanks for that link of dazzozo! . Thats going to be very helpful .

Could you also tell me just one thing - I am confused between recovery and rooting . For example in this article http://huaweinews.com/2013/09/root-huawei-ascend-g300/
it is told to use superrecovery program which ultimately leads to rooting the phone ? Is both recovery and rooting interconnected i.e. you can't have one without the other ?
I know that rooting is to gain superuser administrator privilege access so as to flash custom roms , but i dont know whether rooting is needed to flash recoveries ? Is Recoveries like CWM , TWRP etc used to try to repair the phone or get bricked phones back to working , just like we use Windows Recovery in computers .
I now understand there are 2 options - 1.) Fastboot -> android sdk(use android multitools?& then command prompt to fastboot) -> flash custom recovery so as to enable usb debugging and adb -> use adb to pull data
2.) fastboot - > install superrecovery.bat and get the phone rooted - > use adb to pull data

I have wondered for a long time where the memo's of the notepad app are store . I searched in my sd card . Its not there . I read in a post of the Y300 mobile of someone ( http://forum.xda-developers.com/general/help/huawei-ascend-y300-store-notes-t2810932) who was trying to access the memo app - He wrote he didnt find the memo folder in the internal memory , and some one else said the memo files OR the notepad apk data will most probably be in some SQL file or different file type which cant be decrypted . I suppose the same problem will be there in the G300 too . The problem is the Notepad app is a Stock pre-installed app & thus i also dont know whether it is in the system reserved memory (100mb) which is seperate from internal memory and external sd card - such that it cannot be accessed .
I read somewhere in fastboot mode , the screen goes pink & for some guys the data in the phone was wiped or factory reseted - > could that happen?. Is the moment when the pink screen comes the exact moment when i should connect my phone via usb to PC ?
And by recovery.img , I guess you mean recoveries like CWM , TWRP etc ?

I am going to try to use recovery.img . I am going to search for a recovery.img file , but is there a possibility that there could be any recovery.img that enables USB debugging - so that I can view my Notes using Android Screencast i.e. Memo app in my phone which cant be pulled using adb recovery ?

I am going to try to use recovery.img . Could there be any recovery.img that enables USB debugging - so that I can view my Notes using Android Screencast i.e. Memo app in my phone which cant be pulled using adb recovery ?